On 08/25/2013 01:56 PM, Alexander Tarasikov wrote:
On Sun, Aug 25, 2013 at 8:18 PM, Bob Stewart <robjsstewart@...196... mailto:robjsstewart@...196...> wrote:
I'm try to get a basic Genode setup working on a Beaglebone Black (TI AM335x processor). I'm using a version of u-boot specifically built for the Beaglebone Black from Robert Nelson's eewiki pages. The only modification I made was to allow for elf file commands.I would suggest taking a look at github.com/ksys-labs http://github.com/ksys-labs, we should have a tree that supports Omap3
Carefully following how the PandaBoard and the imx53 platforms were build I successfully built from base-hw an elf image for run/nested_init and loaded that onto an SDCard which contained the two stages of u-boot. (Previously, I had succesfuly built a helloworld test version of Fiasco.OC and successfully manually booted it from an SDCard with the same MLO and u-boot.img files. So the basic process of booting an elf image file works.) The elf image is built to load and 0x81000000 with u-boot using the space from start of SDRAM at 0x80000000. The elf file header has an entry point address of 0x81004DC0. Booting the Beagleboard into u-boot from the SDCard, manually loading the elf image file to the load address above, and giving it a"go" command to the entry point address, I get an "application terminated" message as shown below in the console output through minicom: .I would suppose you are expected to do a "bootelf 0x81000000" to let u-boot properly align the ELF sections. Otherwise, it should be possible to add the "u-boot" to build.conf flags to build an uImage. Either way, what I did was to take the image.bin.gz, ungzip it and substract 0x8000 bytes from the address. So, I loaded it to the address "0x80ff8000". Then, you can either "go" or "bootz" (if your u-boot supports it). Take a look around here for details http://allsoftwaresucks.blogspot.ru/2013/05/porting-genode-to-commercial-har...
. . *U-Boot# load mmc 0 0x81000000 image.elf** **reading image.elf** **604700 bytes read in 73 ms (7.9 MiB/s)** **U-Boot# go 0x81004dc0** **## Starting application at 0x81004DC0 ...** **## Application terminated, rc = 0x8108C004** **U-Boot# * At termination, the output above shows rc to be pointed at 4 bytes beyond the start of the bss section of the image. I would have expected to see at least some Genode core debugging messages, at least. Is core not being executed at the entry point? I believe I have the Board_base stucture and cores cpu, pic, platform_support, timer and tlb files correctly set up for the AM335x. Thank you for any help you can provide. Bob Stewart ------------------------------------------------------------------------------ Introducing Performance Central, a new site from SourceForge and AppDynamics. Performance Central is your source for news, insights, analysis and resources for efficient Application Performance Management. Visit us today! http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk _______________________________________________ Genode-main mailing list Genode-main@lists.sourceforge.net <mailto:Genode-main@lists.sourceforge.net> https://lists.sourceforge.net/lists/listinfo/genode-main-- Regards, Alexander
Introducing Performance Central, a new site from SourceForge and AppDynamics. Performance Central is your source for news, insights, analysis and resources for efficient Application Performance Management. Visit us today! http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clk...
Thanks for the reply Alexander. I'll build it with the u-boot in spec.conf and try loading the uImage. "bootelf" on the loadaddr resulted in a data abort crash.
Bob
Genode-main mailing list Genode-main@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/genode-main