From: Claudio L. <cl...@hp...> - 2013-11-29 02:45:02
|
Thank you, Stefan Yes, there's absolutely no documentation about the 5410, so I'm relying on the Linux sources, which are not exactly friendly to extract information. Right now I've become quite busy but I'll make slow progress. I'll check out your sources, it's probably a much cleaner approach. I followed the topic where it seems that base-hw is the future of genode, so perhaps it's better to drop Fiasco and just write drivers and improve base-hw rather than trying to port Fiasco.OC. Thanks again for the help. Claudio On 11/26/2013 09:14, Stefan Kalkowski wrote: > Hi Claudio, > > coincidentally, an ODROID XU board ended up on by desktop. I've enabled > rudimentary support for it using Genode's hw kernel (not Fiasco.OC). > Maybe, you'll profit from it when doing further research on top of > Fiasco.OC. You can find an intermediate state in this topic branch: > > https://github.com/skalk/genode/tree/odroid > > Sadly, I couldn't find any resources about Exynos-5410's memory map, > irqs, or clock tree beside the Linux kernel tree from "hardkernel" > itself :-(. > > Best regards > Stefan > > On 11/13/2013 02:31 AM, Claudio L. wrote: >> Update: >> The crash happens while mapping memory, during the early stages of the >> bootstrap process, most likely due to differences in the chipset. >> I've already created all the makefiles and directories needed for a >> separate "odroidxu" target, for now just a copy of the arndale ones, and >> I'm ready to start coding. >> I created one spec called "exynos5octa", which will complement the >> existing "exynos5", on the few items where there are architectural >> differences in the SOC. >> >> Claudio >> >> >> On 11/06/2013 07:54, Claudio L. wrote: >>> Hello, >>> I'm creating this thread where I'll report the status of my port of >>> genode to the Odroid-XU board. >>> >>> Initial bootstrap went well. Board executed the bootstrap and hung right >>> after showing "Hello from startup::stage2", which is where most of the >>> hardware initialization takes place. Here's where the real porting job >>> begins. >>> >>> For others with the XU board, here's what I did to test it: >>> >>> * After having checked out genode repository, and installed the >>> additional packages per the genode instructions to build Fiasco.OC, >>> install one more package: >>> >>> > apt-get install u-boot-tools >>> >>> This will give us the mkimage command we need. >>> >>> then, from the main genode directory: >>> >>> > cd base_foc >>> > make prepare >>> > cd .. >>> > ./tool/create_builddir foc_arndale BUILD_DIR=build.exynos >>> > cd build.exynos >>> > make >>> >>> This make is just to see if you have anything missing. You should be >>> able to get to the end without any errors. If not, something went wrong. >>> >>> Now we need a small change to generate the uboot image: >>> >>> > cd build.exynos/etc >>> >>> edit the file build.conf and add the line >>> >>> RUN_OPT = --target uboot >>> >>> then build the printf demo with: >>> >>> > make clean [[make sure you are in the build.exynos directory] >>> > make run/printf >>> >>> If everything goes well, compile will end with an error saying it can't >>> run automatically on this target. This is normal, since we never removed >>> the lines in the run script that try to use qemu to run the test. >>> The important thing is that in build.exynos/var/run/printf, there's a >>> 'uImage' file. >>> >>> Put the file on a microSD card, insert the card into the Odroid-XU. >>> Connect to the serial console (I use the excellent Putty), configured as >>> 115200, 8N1. The name of the serial port might vary, depending on which >>> USB port the board was plugged in. To access the serial port, Putty >>> might need to be run as root. >>> >>> Boot the board and press space quickly to stop the boot process at >>> u-boot (green light on the board should be on). >>> Now issue the following commands: >>> >>> > mmc dev 1 >>> > fatload mmc 1 0x60000000 uImage >>> >>> It should say it's OK and that it read about 600k from the sd card. >>> >>> finally, boot the image: >>> >>> > bootm 0x60000000 >>> >>> If everything goes well, you should see a lot of text in the console, >>> ending with "Hello from startup::stage2". >>> >>> That's as far as I got today. More to come... >>> Claudio >>> >>> ------------------------------------------------------------------------------ >>> November Webinars for C, C++, Fortran Developers >>> Accelerate application performance with scalable programming models. Explore >>> techniques for threading, error checking, porting, and tuning. Get the most >>> from the latest Intel processors and coprocessors. See abstracts and register >>> http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk >>> _______________________________________________ >>> Genode-main mailing list >>> Gen...@li... >>> https://lists.sourceforge.net/lists/listinfo/genode-main >>> >>> >> >> ------------------------------------------------------------------------------ >> DreamFactory - Open Source REST & JSON Services for HTML5 & Native Apps >> OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access >> Free app hosting. Or install the open source package on any LAMP server. >> Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native! >> http://pubads.g.doubleclick.net/gampad/clk?id=63469471&iu=/4140/ostg.clktrk >> _______________________________________________ >> Genode-main mailing list >> Gen...@li... >> https://lists.sourceforge.net/lists/listinfo/genode-main >> |