Intel Edison Round #2

Oyake, Amalaye (398F) amalaye.oyake at
Wed Dec 10 22:26:01 UTC 2014

Wait wait wait …

A whole lotta stuff happened in-between this email and your previous email :D

How did you get the boot loader to work? Also could you post a few pictures as well.

* Amalaye Oyake                                       *
* Instrument Product Software Development Group  */\  *
* Jet Propulsion Laboratory, Pasadena            *||  *
* CA 91109 818.393.7168 work   626.399.1707 cell /||\ *

From: Joel Sherrill <joel.sherrill at<mailto:joel.sherrill at>>
Date: Wednesday, December 10, 2014 at 2:23 PM
To: "users at<mailto:users at>" <users at<mailto:users at>>, Jeff Mayes <Jeff.Mayes at<mailto:Jeff.Mayes at>>
Subject: Intel Edison Round #2


Jeff and I have hacked on the Edison and have it starting to
boot with printk() and bsp_reset() working. I added a bunch of
printk's to trace the progress. It is the end of the day and we are
stuck at the create of the first Classic API task in hello world failing
to allocate the FP area.

I am assuming some memory layout issue but I just don't
see it. This board has 1GB RAM per Intel and U-Boot.
It loads our normal pc386 ELF at the right address and runs.

I am throwing this out to the community to see if anyone
has an idea on what to poke at tomorrow. We are tired at
the end of the day.

boot > bootelf 0x1000000
## Starting application at 0x0010000c ...
0234rtemsWorkAreaStart=130F40 MemSize=0x08x/0

work_area_start = 0x130F40
work_area_size = 1072492736 0x3FECF0C0
end = 0x40000000
current stack pointer = 0x130F18
heap_start = 0x134D0A
heap_size = 1072476918
allocated thread fp area 133CB8
initialize device drivers
Checking on /dev/main
Register /dev/main
Register /dev/main as console
Console initialize complete
run post driver extensions
Invoke api extension 10F540
Init tasks => 12C3E8 1
allocated thread 13255C
allocated thread fp area 0
Thread Initialize failed
task create returned 13

EXECUTIVE SHUTDOWN! Any key to reboot...

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the users mailing list