Hi thanks for the reply,I am Archie working with Aditya on this . We use your reprository and then followed the steps given in https://github.com/genodelabs/genode/commit/ce58a63fb661df42e6bf283891589b11... ,https://github.com/genodelabs/genode/commit/ce58a63fb661df42e6bf283891589b11a1f411f2#commitcomment-2891606for creating uImage .
And then booted using tftp with this.
# either 'dhcp' or 'setenv ipaddr xxx.xxx.xxx.xxx' # 'setenv serverip xxx.xxx.xxx.xxx' as long it isn't set via DHCP # 'tftp 0x70800000 [path_to_uimage]/uImage' # 'bootm 0x70800000'
Now the error we are getting in this is
Using FEC device TFTP from server 10.6.1.123; our IP address is 10.6.1.122 Filename 'uImage'. Load address: 0x10800000 Loading: ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################# done Bytes transferred = 1829585 (1bead1 hex) U-Boot > bootm ## Booting kernel from Legacy Image at 10800000 ... Image Name: Image Type: ARM Linux Kernel Image (gzip compressed) Data Size: 1829521 Bytes = 1.7 MiB Load Address: 70140000 Entry Point: 7018b33c Verifying Checksum ... OK Uncompressing Kernel Image ...
Any Ideas where we might be going wrong?
On Wed, Jul 10, 2013 at 3:52 PM, Nikolay Golikov <nik@...104...> wrote:
[image: Boxbe] https://www.boxbe.com/overview This message is eligible for Automatic Cleanup! (nik@...104...) Add cleanup rulehttps://www.boxbe.com/popup?url=https%3A%2F%2Fwww.boxbe.com%2Fcleanup%3Ftoken%3D6QhiTkGDnWSDBCZCgRWml5MYJzAKEf3VsPTwYq8npCZP6PPBx1DnsDKAW5iMdK9cwsjbKEkZouxkn1hRE4gx1%252BmS8I%252F9bxMRT7vWUdOIcTr1CtWJzvHUkXnlXuxfSRKwkxY50ei5QlQ%253D%26key%3DIiPAnPO2CAsKw%252BlwcPl5Uzo145bFWBvCFheyxad7Z4M%253D&tc_serial=14582365019&tc_rand=1545586721&utm_source=stf&utm_medium=email&utm_campaign=ANNO_CLEANUP_ADD&utm_content=001| More infohttp://blog.boxbe.com/general/boxbe-automatic-cleanup?tc_serial=14582365019&tc_rand=1545586721&utm_source=stf&utm_medium=email&utm_campaign=ANNO_CLEANUP_ADD&utm_content=001
среда, 10 июля 2013 г. пользователь Aditya Kousik писал:
Hello
Firstly, thank you for patiently replying to our queries and debugging issues so far.
We're trying to port Genode onto an i.MX6, which we've realised is no easy task. Our initial approach to this was to tweak existing i.Mx53 files and make corresponding changes (arm cortex a9, created imx6 related folders in include). As pointed out to us by Stefan, this was completely off track as the memory layout may be mixed up (or many more issues).
Here's a brief reboot of our attempt:
- edit create_builddir to add a rule for imx6 board and added
build.conf.hw_imx6 in builddir folder. 2. modify board_base.h in base/include/platform/imx6/drivers and fill with addresses by referring to the imx6 reference manual. (We also added CORTEX_A9_CLOCK and private memory base) 3. read through the Makefile and added spec-hw_imx6 and spec-platform_imx6 respectively. 4. created imx6 folder with files in os/include/platform/imx6 as well. (All with imx53 as reference)
Make: Since the drivers for imx6 would take a long time to code, we are NOT running demo.run. We tried to build hello.run (without building drivers/timer) according the instructions given in your site.
We're getting the following error: Program core/imx6/core COMPILE _main.o ASSEMBLE boot_modules.o COMPILE console.o COMPILE context_area.o COMPILE cpu_session_component.o COMPILE cpu_session_support.o ASSEMBLE crt0.o COMPILE dataspace_component.o COMPILE dump_alloc.o COMPILE io_mem_session_component.o COMPILE io_mem_session_support.o COMPILE irq_session_component.o COMPILE kernel.o COMPILE kernel_support.o COMPILE main.o make[3]: *** No rule to make target `mode_transition.o', needed by `core'. Stop. make[2]: *** [core.prg] Error 2 make[1]: *** [gen_deps_and_build_targets] Error 2 make[1]: Leaving directory `/media/work/assorted/genode/imx' Error: Genode build failed make: *** [run/hello] Error 255
Thanks and regards Aditya
Hello, four months ago I added basic support for i.MX6 to genode. Results of this work you can see at https://github.com/decaprox/genode/tree/i.mx6.
See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clk...
Genode-main mailing list Genode-main@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/genode-main
Archie Nidhi schrieb:
Hi thanks for the reply,I am Archie working with Aditya on this . We use your reprository and then followed the steps given in https://github.com/genodelabs/genode/commit/ce58a63fb661df42e6bf283891589b11... , for creating uImage . And then booted using tftp with this. # either 'dhcp' or 'setenv ipaddr xxx.xxx.xxx.xxx' # 'setenv serverip xxx.xxx.xxx.xxx' as long it isn't set via DHCP # 'tftp 0x70800000 [path_to_uimage]/uImage' # 'bootm 0x70800000' Now the error we are getting in this is Using FEC device TFTP from server 10.6.1.123; our IP address is 10.6.1.122 Filename 'uImage'. Load address: 0x10800000 Loading: ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################# done Bytes transferred = 1829585 (1bead1 hex) U-Boot > bootm ## Booting kernel from Legacy Image at 10800000 ... Image Name: Image Type: ARM Linux Kernel Image (gzip compressed) Data Size: 1829521 Bytes = 1.7 MiB Load Address: 70140000 Entry Point: 7018b33c Verifying Checksum ... OK Uncompressing Kernel Image ... Any Ideas where we might be going wrong?
Hello, Archie
Which type of i.MX6 board are you using? The load address 0x70140000 of your boot image assumes that your board supports 2 GB of RAM (physical address range 0x10000000 to 0x8FFFFFFF). AFAIK not all i.MX6 boards have that much memory, others come with 1 GB instead (physical address range 0x10000000 to 0x4FFFFFFF). In that case you have to modify the build scripts so that the löad address is set to 0x40140000 and the entry point to 0x4018b33c (or other values which fit into the 1 GB range).
Frank