Re: [U-Boot] booting os 'Unknown OS' (1) is not supported
methinks that the problem in kernel. I can boot "original" android kernel from any place: emmc, SD, fat partition, USB-device, etc. 2014/1/20 Detlev Zundel > Hi Alexander, > > > link to my u-boot https://github.com/fedya/u-boot-yse5250 > > > >>Please change the boot command and include the commands > > > > Changed to this > > bootcmd=md 4080 10;imi 4080;bootm 4080 > > > > [YSE5250@omv]# boot > > 4080: 56190527 ba6b0d61 9850d952 08484800'..Va.k.R.P..HH. > > 40800010: 00800040 00800040 8a221c4c 00020205@...@...L.". > > 40800020: 756e694c 2e332d78 302e3331 3863722dLinux-3.13.0-rc8 > > 40800030: > > > > ## Checking Image at 4080 ... > >Legacy image found > >Image Name: Linux-3.13.0-rc8 > >Image Type: ARM Linux Kernel Image (uncompressed) > >Data Size:4737032 Bytes = 4626 KiB > >Load Address: 40008000 > >Entry Point: 40008000 > >Verifying Checksum ... OK > > ## Current stack ends at 0xc3cfbcc8 * kernel: cmdline image address = > > 0x4080 > > ## Booting kernel from Legacy Image at 4080 ... > >Image Name: Linux-3.13.0-rc8 > >Image Type: ARM Linux Kernel Image (uncompressed) > >Data Size:4737032 Bytes = 4626 KiB > >Load Address: 40008000 > >Entry Point: 40008000 > >Verifying Checksum ... OK > >kernel data at 0x40800040, len = 0x00484808 (4737032) > > ## No init Ramdisk > >ramdisk start = 0x, ramdisk end = 0x > >Loading Kernel Image ... OK > > OK > >kernel loaded at 0x40008000, end = 0x4048c808 > > ERROR: booting os 'Unknown OS' (1) is not supported > > This is really weird and I am pretty sure that this is not supposed to > happen with the code that we have in mainline. I think you have two > options here: > > 1. Get mainline U-Boot running on your board that works with the uImage >that os created from mainline Linux > > 2. Debug your U-Boot version why it does not handle the uImage like it >is supposed to. > > Option 1 will be the more rewarding alternative of course. > > Best wishes > Detlev > > -- > insults: If set, sudo will insult users when they enter an incorrect > password. This flag is off by default. >-- man sudoers > -- > DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel > HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany > Phone: (+49)-8142-66989-40 Fax: (+49)-8142-66989-80 Email: d...@denx.de > ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] booting os 'Unknown OS' (1) is not supported
link to my u-boot https://github.com/fedya/u-boot-yse5250 >Please change the boot command and include the commands Changed to this bootcmd=md 4080 10;imi 4080;bootm 4080 [YSE5250@omv]# boot 4080: 56190527 ba6b0d61 9850d952 08484800'..Va.k.R.P..HH. 40800010: 00800040 00800040 8a221c4c 00020205@...@...L.". 40800020: 756e694c 2e332d78 302e3331 3863722dLinux-3.13.0-rc8 40800030: ## Checking Image at 4080 ... Legacy image found Image Name: Linux-3.13.0-rc8 Image Type: ARM Linux Kernel Image (uncompressed) Data Size:4737032 Bytes = 4626 KiB Load Address: 40008000 Entry Point: 40008000 Verifying Checksum ... OK ## Current stack ends at 0xc3cfbcc8 * kernel: cmdline image address = 0x4080 ## Booting kernel from Legacy Image at 4080 ... Image Name: Linux-3.13.0-rc8 Image Type: ARM Linux Kernel Image (uncompressed) Data Size:4737032 Bytes = 4626 KiB Load Address: 40008000 Entry Point: 40008000 Verifying Checksum ... OK kernel data at 0x40800040, len = 0x00484808 (4737032) ## No init Ramdisk ramdisk start = 0x, ramdisk end = 0x Loading Kernel Image ... OK OK kernel loaded at 0x40008000, end = 0x4048c808 ERROR: booting os 'Unknown OS' (1) is not supported >movi string from help movi- movi - sd/mmc r/w sub system for SMDK board and same command for o-droid http://lists.denx.de/pipermail/u-boot/2013-February/146047.html 2014/1/20 Wolfgang Denk > Dear Alexander Khryukin, > > In message < > cabtoafz3e-ee3v73th6u4bjsqixu6sy3h1tdng2fx-phdf0...@mail.gmail.com> you > wrote: > > > > As you said i changed my bootcmd to > > *bootcmd=movi read kernel 0 4080;bootm 408* > > I really wonder which sort of U-Boot you are running. "movi" is not a > command present in mainline, not in any vendor port I am aware of. > What exactly is this command supposed to do? > > Please change the boot command and include the commands > > md 408 10;imi 408 > > before the "bootm" part. > > > > Best regards, > > Wolfgang Denk > > -- > DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel > HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany > Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: w...@denx.de > Hacking's just another word for nothing left to kludge. > ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] booting os 'Unknown OS' (1) is not supported
Good day! I'm here again with short report. As you said i changed my bootcmd to *bootcmd=movi read kernel 0 4080;bootm 408* with default bootargs options bootargs=console=ttySAC1,115200n8 vmalloc=512M androidboot.console=ttySAC And i see same result [YSE5250@omv]# boot reading kernel..device 0 Start 1063, Count 16384 MMC read: dev # 0, block # 1063, count 16384 ... 16384 blocks read: OK completed ## Current stack ends at 0xc3cfbcc8 * kernel: cmdline image address = 0x4080 ## Booting kernel from Legacy Image at 4080 ... Image Name: Linux-3.13.0-rc8 Image Type: ARM Linux Kernel Image (uncompressed) Data Size:4737032 Bytes = 4626 KiB Load Address: 40008000 Entry Point: 40008000 Verifying Checksum ... OK kernel data at 0x40800040, len = 0x00484808 (4737032) ## No init Ramdisk ramdisk start = 0x, ramdisk end = 0x Loading Kernel Image ... OK OK kernel loaded at 0x40008000, end = 0x4048c808 ERROR: booting os 'Unknown OS' (1) is not supported 2014/1/17 Detlev Zundel > Hi Alexander, > > > You have any suggestion how i can fix or hack it? > > I really have no clue what's wrong and why it's working with android > kernel > > and not with mainline. > > Well, potentially, there can be worlds of differences between such > kernels. I don't know your platform at all, but is it expected to work > with a mainline kernel? > > The only thing that I can think of to get more information is to edit > your bootcmd to only boot the kernel without any ramdisk and see if the > loading of the latter is the problem, i.e. something like that: > > bootcmd=movi read kernel 0 4080;bootm 4080 > > Even though this cannot fully work, it may give us new input. > > Cheers > Detlev > > -- > ;; Self-replicator in ELisp > ((lambda (l) (prin1-to-string (list l (list (quote quote) l > (quote (lambda (l) (prin1-to-string (list l (list (quote quote) l)) > -- > DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel > HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany > Phone: (+49)-8142-66989-40 Fax: (+49)-8142-66989-80 Email: d...@denx.de > ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] booting os 'Unknown OS' (1) is not supported
You have any suggestion how i can fix or hack it? I really have no clue what's wrong and why it's working with android kernel and not with mainline. 2014/1/17 Detlev Zundel > Hi Alexander, > > > Might i need a special arguments for mkimage > > to set up OS in headers of uImage? > > One needs parameters for that, but the information looks ok: > > [...] > > >> [fedya@discordy linux-linaro-tracking]$ mkimage -l arch/arm/boot/uImage > >> Image Name: Linux-3.13.0-rc8 > >> Created: Fri Jan 17 15:47:36 2014 > >> > >> Image Type: ARM Linux Kernel Image (uncompressed) > ^ > > If you check common/image.c:261 (image_print_type), you'll see that this > is correctly decoded from the image, so the image seems perfectly fine. > It just makes no sense that U-Boot then complains about an unknown OS. > This means that between the time the header is printed and between the > time the code wants to boot it, the memory does not contain what it > should anymore. > > Cheers > Detlev > > -- > ike|abel - Eine Partnerschaft erweist sich als ikeabel, wenn ein > samstäglicher > Besuch bei Ikea weder zur sofortigen Trennung noch zu tagelangen > Diskussionen > führt. In einigen urbanen Subkulturen hat der gemeinsame Ikea-Besuch die > Ver- > lobung vollständig ersetzt.-- "Wortschatz" v. Sascha Lobo > -- > DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel > HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany > Phone: (+49)-8142-66989-40 Fax: (+49)-8142-66989-80 Email: d...@denx.de > ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] booting os 'Unknown OS' (1) is not supported
> Do you have a kernel and ramdisk and kernel > command line that works on your board? Yes, i have a working 3.0. kernel and ramdisk.img it is an android image. Linux version 3.0.15 (root@yicsystem) (gcc version 4.4.3 (GCC) ) #1 SMP PREEMPT Thu Apr 25 14:28:59 KST 2013 > kernel command line # cat /proc/cmdline console=ttySAC1,115200n8 vmalloc=512M androidboot.console=ttySAC1 i built a kernel with same string. > Also is U-Boot and the kernel > mainline? u-boot based on U-Boot 2012.12-0-g462762b-dirty with yse5250 platform changes And i tried a mainline u-boot and it's does not working. Just an empty screen on terminal window. 2014/1/17 Detlev Zundel > Hi Alexander, > > > Also if flashed 3.12_zImage (same kernel, same sources, just zImage) > > Ok, zImage doesn't have the uImage header, so we will not see any > information nor will U-Boot be able to verify a checksum there. > > > reading kernel..device 0 Start 1063, Count 16384 > > MMC read: dev # 0, block # 1063, count 16384 ... 16384 blocks read: OK > > completed > > reading RFS..device 0 Count 17447, Start 2048 > > MMC read: dev # 0, block # 17447, count 2048 ... 2048 blocks read: OK > > completed > > Boot with zImage > > Wrong Ramdisk Image Format > > Note that you also have a problem with your ramdisk, even if the kernel > starts, it will likely not do much if it needs the ramdisk. > > > Starting kernel ... > > > > > > And it's stucked at "Starting kernel ..." > > Let's say "we don't see anything after Starting kernel ". This is > also a common case when the kernel cannot open an initial console. It > may well be that the kernel runs but without a console you will see > nothing. To diagnose this you'd need to be sure that "bootargs" is > setup properly before booting the kernel. > > Let's step back a bit. Do you have a kernel and ramdisk and kernel > command line that works on your board? I.e. do we have a "working case" > that we can retreat to for further tests? Also is U-Boot and the kernel > mainline? > > Cheers > Detlev > > -- > The management question ... is not _whether_ to build a pilot system > and throw it away. You _will_ do that. The only question is whether to > plan in advance to build a throwaway, or to promise to deliver the > throwaway to customers. - Fred Brooks, "The Mythical Man Month" > -- > DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel > HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany > Phone: (+49)-8142-66989-40 Fax: (+49)-8142-66989-80 Email: d...@denx.de > ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] booting os 'Unknown OS' (1) is not supported
Might i need a special arguments for mkimage to set up OS in headers of uImage? 2014/1/17 Alexander Khryukin > >Can you do an 'mkimage -l > > > [fedya@discordy linux-linaro-tracking]$ mkimage -l arch/arm/boot/uImage > Image Name: Linux-3.13.0-rc8 > Created: Fri Jan 17 15:47:36 2014 > > Image Type: ARM Linux Kernel Image (uncompressed) > Data Size:4737032 Bytes = 4626.01 kB = 4.52 MB > > Load Address: 40008000 > Entry Point: 40008000 > > source code: https://github.com/fedya/u-boot-yse5250 > > > > 2014/1/17 Detlev Zundel > >> Hi Alexander, >> >> [...] >> >> > *ERROR: booting os 'Unknown OS' (1) is not supported* >> >> Hm, very strange. Looking up the code, the '1' is the image type >> contained in the uImage header. It is defined to be OpenBSD in >> include/image.h and if your U-Boot doesn't have support for that, you >> will get that message. This however doesn't make sense to have an >> uImage with this type. >> >> Can you do an 'mkimage -l ' on your development host to check the >> contents of the header? If this looks good, then somehow the image >> seems to be overwritten before trying to boot, but I don't see where. >> >> Cheers >> Detlev >> >> -- >> I object to doing things that computers can do. -- Olin Shivers >> -- >> DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel >> HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany >> Phone: (+49)-8142-66989-40 Fax: (+49)-8142-66989-80 Email: d...@denx.de >> > > ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] booting os 'Unknown OS' (1) is not supported
>Can you do an 'mkimage -l [fedya@discordy linux-linaro-tracking]$ mkimage -l arch/arm/boot/uImage Image Name: Linux-3.13.0-rc8 Created: Fri Jan 17 15:47:36 2014 Image Type: ARM Linux Kernel Image (uncompressed) Data Size:4737032 Bytes = 4626.01 kB = 4.52 MB Load Address: 40008000 Entry Point: 40008000 source code: https://github.com/fedya/u-boot-yse5250 2014/1/17 Detlev Zundel > Hi Alexander, > > [...] > > > *ERROR: booting os 'Unknown OS' (1) is not supported* > > Hm, very strange. Looking up the code, the '1' is the image type > contained in the uImage header. It is defined to be OpenBSD in > include/image.h and if your U-Boot doesn't have support for that, you > will get that message. This however doesn't make sense to have an > uImage with this type. > > Can you do an 'mkimage -l ' on your development host to check the > contents of the header? If this looks good, then somehow the image > seems to be overwritten before trying to boot, but I don't see where. > > Cheers > Detlev > > -- > I object to doing things that computers can do. -- Olin Shivers > -- > DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel > HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany > Phone: (+49)-8142-66989-40 Fax: (+49)-8142-66989-80 Email: d...@denx.de > ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] booting os 'Unknown OS' (1) is not supported
Thanks. I changed env to baudrate=115200 *bootcmd=movi read kernel 0 4080;movi read rootfs 0 4100 10;bootm 4080 4100* bootdelay=3 emmcbootrecovery=mmc erase boot 1 0 0;emmc open 1;movi read fwbl1 0 4000;movi write zero fwbl1 1 4000;movi read bl2 0 40004000;movi write zero bl2 1 40004000;movi read u-boot 0 4200;movi write zero u-boot 1 4200;movi read tzsw 0 4210;movi write zero tzsw 1 4210;emmc close 1 ethact=smc911x-0 ethaddr=00:40:5c:26:0a:5b gatewayip=192.168.0.1 ipaddr=192.168.0.28 netmask=255.255.255.0 rootfslen= 10 serverip=192.168.0.13 And now trying to boot U-Boot 2012.12-0-g503cd8d-dirty (Jan 15 2014 - 12:58:49) for YICSYSTEM YSE5250-scp CPU: S5PC520 Rev1.0 [Samsung SOC on SMP Platform Base on ARM CortexA15] APLL = 800MHz, MPLL = 800MHz Board: YSE5250-scp DRAM: 2047 MiB TrustZone Enabled BSP BL1 version: 20130404 PMIC: S5M8767 Checking Boot Mode ... SDMMC REVISION: 1.0 REVISION: 1.0 MMC Device 0: 3839 MB NAME: S5P_MSHC0 MMC Device 1: 7348 MB MMC Device 2 not found Net: smc911x-0 Hit any key to stop autoboot: 0 reading kernel..device 0 Start 1063, Count 16384 MMC read: dev # 0, block # 1063, count 16384 ... 16384 blocks read: OK completed reading RFS..device 0 Count 17447, Start 2048 MMC read: dev # 0, block # 17447, count 2048 ... 2048 blocks read: OK completed ## Booting kernel from Legacy Image at 4080 ... Image Name: Linux-3.13.0-rc8 Image Type: ARM Linux Kernel Image (uncompressed) Data Size:4754992 Bytes = 4643 KiB Load Address: 40008000 Entry Point: 40008000 Verifying Checksum ... OK Wrong Ramdisk Image Format Loading Kernel Image ... OK OK *ERROR: booting os 'Unknown OS' (1) is not supported* No changes. But XIP is gone. 2014/1/17 Detlev Zundel > Hello Alexander, > > > Thanks for your answer! > > > >>So again, try loading the image somewhere else in RAM and let U-Boot do > >>the copying to the correct place. > > > > It's not obvious for me how to do it. > > Might you have any guide or faq? > > [...] > > >> > ### main_loop: bootcmd="movi read kernel 0 40008000;movi read rootfs 0 > ^^^ > >> > 4100 10;bootm 40008000 4100" > ^^ > > Your bootmcd reads the kernel to 40008000 and then calls bootm to that > address. Simple change those two places to, say, 4080 by editing > bootcmd. (Not knowing your system, I presume RAM starts at 4000, > and 4080, then would be 8MiB after the beginning. U-Boot will copy > the kernel to 4008000 so the kernel should not be bigger than 7.5MiB but > the other snippets from your log say the kernel is ~3.2MiB, so this > should be fine. > > Cheers > Detlev > > -- > The only thing that interferes with my learning is my education. > -- Albert Einstein > -- > DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel > HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany > Phone: (+49)-8142-66989-40 Fax: (+49)-8142-66989-80 Email: d...@denx.de > ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] booting os 'Unknown OS' (1) is not supported
Also if flashed 3.12_zImage (same kernel, same sources, just zImage) i see this reading kernel..device 0 Start 1063, Count 16384 MMC read: dev # 0, block # 1063, count 16384 ... 16384 blocks read: OK completed reading RFS..device 0 Count 17447, Start 2048 MMC read: dev # 0, block # 17447, count 2048 ... 2048 blocks read: OK completed Boot with zImage Wrong Ramdisk Image Format Starting kernel ... And it's stucked at "Starting kernel ..." 2014/1/17 Alexander Khryukin > Thanks. > I changed env to > > baudrate=115200 > *bootcmd=movi read kernel 0 4080;movi read rootfs 0 4100 > 10;bootm 4080 4100* > bootdelay=3 > emmcbootrecovery=mmc erase boot 1 0 0;emmc open 1;movi read fwbl1 0 > 4000;movi write zero fwbl1 1 4000;movi read bl2 0 40004000;movi > write zero bl2 1 40004000;movi read u-boot 0 4200;movi write zero > u-boot 1 4200;movi read tzsw 0 4210;movi write zero tzsw 1 > 4210;emmc close 1 > ethact=smc911x-0 > ethaddr=00:40:5c:26:0a:5b > gatewayip=192.168.0.1 > ipaddr=192.168.0.28 > netmask=255.255.255.0 > rootfslen= 10 > serverip=192.168.0.13 > > > > And now trying to boot > U-Boot 2012.12-0-g503cd8d-dirty (Jan 15 2014 - 12:58:49) for YICSYSTEM > YSE5250-scp > > > CPU: S5PC520 Rev1.0 [Samsung SOC on SMP Platform Base on ARM CortexA15] > APLL = 800MHz, MPLL = 800MHz > Board: YSE5250-scp > DRAM: 2047 MiB > > TrustZone Enabled BSP > BL1 version: 20130404 > PMIC: S5M8767 > > > Checking Boot Mode ... SDMMC > REVISION: 1.0 > REVISION: 1.0 > MMC Device 0: 3839 MB > NAME: S5P_MSHC0 > MMC Device 1: 7348 MB > MMC Device 2 not found > Net: smc911x-0 > > Hit any key to stop autoboot: 0 > reading kernel..device 0 Start 1063, Count 16384 > MMC read: dev # 0, block # 1063, count 16384 ... 16384 blocks read: OK > completed > reading RFS..device 0 Count 17447, Start 2048 > MMC read: dev # 0, block # 17447, count 2048 ... 2048 blocks read: OK > completed > ## Booting kernel from Legacy Image at 4080 ... >Image Name: Linux-3.13.0-rc8 > >Image Type: ARM Linux Kernel Image (uncompressed) >Data Size:4754992 Bytes = 4643 KiB > >Load Address: 40008000 >Entry Point: 40008000 >Verifying Checksum ... OK > Wrong Ramdisk Image Format >Loading Kernel Image ... OK > OK > > *ERROR: booting os 'Unknown OS' (1) is not supported* > > > No changes. > But XIP is gone. > > > > 2014/1/17 Detlev Zundel > >> Hello Alexander, >> >> > Thanks for your answer! >> > >> >>So again, try loading the image somewhere else in RAM and let U-Boot do >> >>the copying to the correct place. >> > >> > It's not obvious for me how to do it. >> > Might you have any guide or faq? >> >> [...] >> >> >> > ### main_loop: bootcmd="movi read kernel 0 40008000;movi read rootfs >> 0 >> ^^^ >> >> > 4100 10;bootm 40008000 4100" >> ^^ >> >> Your bootmcd reads the kernel to 40008000 and then calls bootm to that >> address. Simple change those two places to, say, 4080 by editing >> bootcmd. (Not knowing your system, I presume RAM starts at 4000, >> and 4080, then would be 8MiB after the beginning. U-Boot will copy >> the kernel to 4008000 so the kernel should not be bigger than 7.5MiB but >> the other snippets from your log say the kernel is ~3.2MiB, so this >> should be fine. >> >> Cheers >> Detlev >> >> -- >> The only thing that interferes with my learning is my education. >> -- Albert Einstein >> -- >> DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel >> HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany >> Phone: (+49)-8142-66989-40 Fax: (+49)-8142-66989-80 Email: d...@denx.de >> > > ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] booting os 'Unknown OS' (1) is not supported
Thanks for your answer! >So again, try loading the image somewhere else in RAM and let U-Boot do >the copying to the correct place. It's not obvious for me how to do it. Might you have any guide or faq? 2014/1/17 Detlev Zundel > Hi Alexander, > > > I faced with a strange behaviour of u-boot. > > Expected behaviour for some people may seem strange to others ;) > > > Few months ago i bought an ARM development board from yicsystem > > it's based on exynos 5250 and very similar to arndale > > http://www.yicsystem.com/products/low-cost-board/yse5250/ > > > > And i can boot Android ICS > > but when i try to boot any linux > > i always see > > > > > > Checking Boot Mode ... SDMMC > > Now running in RAM - U-Boot at: c3e0 > > REVISION: 1.0 > > REVISION: 1.0 > > MMC Device 0: 3839 MB > > NAME: S5P_MSHC0 > > MMC Device 1: 7348 MB > > MMC Device 2 not found > > Destroy Hash Table: c3f80f78 table = (null) > > Create Hash Table: N=512 > > INSERT: table c3f80f78, filled 1/521 rv c3d047a0 ==> name="baudrate" > > value="115200" > > INSERT: table c3f80f78, filled 2/521 rv c3d0582c ==> name="bootargs" > > value="root=/dev/mmcblk0p1" > > INSERT: table c3f80f78, filled 3/521 rv c3d04a1c ==> name="bootcmd" > > value="movi read kernel 0 40008000;movi read rootfs 0 4100 > 10;bootm > > 40008000 4100" > > INSERT: table c3f80f78, filled 4/521 rv c3d04f20 ==> name="bootdelay" > > value="3" > > INSERT: table c3f80f78, filled 5/521 rv c3d04bfc ==> name="bootfile" > > value="/tftpboot/revoboot/bin/revoboot.pxe" > > INSERT: table c3f80f78, filled 6/521 rv c3d040a4 ==> > > name="emmcbootrecovery" value="mmc erase boot 1 0 0;emmc open 1;movi read > > fwbl1 0 4000;movi write zero fwbl1 1 4000;movi read bl2 0 > > 40004000;movi write zero bl2 1 40004000;movi read u-boot 0 4200;movi > > write zero u-boot 1 4200;movi read tzsw 0 4210;movi write zero > tzsw > > 1 4210;emmc close 1" > > INSERT: table c3f80f78, filled 7/521 rv c3d04998 ==> name="ethact" > > value="smc911x-0" > > INSERT: table c3f80f78, filled 8/521 rv c3d0462c ==> name="ethaddr" > > value="00:40:5c:26:0a:5b" > > INSERT: table c3f80f78, filled 9/521 rv c3d057a8 ==> name="gatewayip" > > value="192.168.0.1" > > INSERT: table c3f80f78, filled 10/521 rv c3d05874 ==> name="ipaddr" > > value="192.168.0.28" > > INSERT: table c3f80f78, filled 11/521 rv c3d048c0 ==> name="netmask" > > value="255.255.255.0" > > INSERT: table c3f80f78, filled 12/521 rv c3d05214 ==> name="rootfslen" > > value=" 10" > > INSERT: table c3f80f78, filled 13/521 rv c3d048e4 ==> name="serverip" > > value="192.168.0.13" > > INSERT: free(data = c3d00010) > > INSERT: done > > Net: smc911x-0 > > ### main_loop entered: bootdelay=3 > > > > ### main_loop: bootcmd="movi read kernel 0 40008000;movi read rootfs 0 > > 4100 10;bootm 40008000 4100" > > Hit any key to stop autoboot: 0 > > reading kernel..device 0 Start 1063, Count 16384 > > MMC read: dev # 0, block # 1063, count 16384 ... 16384 blocks read: OK > > completed > > reading RFS..device 0 Count 17447, Start 2048 > > MMC read: dev # 0, block # 17447, count 2048 ... 2048 blocks read: OK > > completed > > ## Current stack ends at 0xc3cfbd98 * kernel: cmdline image address = > > 0x40008000 > > ## Booting kernel from Legacy Image at 40008000 ... > >Image Name: Linux-3.12.0-rc1-armv7-x0.6-0012 > >Image Type: ARM Linux Kernel Image (uncompressed) > >Data Size:3243400 Bytes = 3167 KiB > >Load Address: 40008000 > >Entry Point: 40008000 > >Verifying Checksum ... OK > >kernel data at 0x40008040, len = 0x00317d88 (3243400) > > * ramdisk: cmdline image address = 0x4100 > > Wrong Ramdisk Image Format > >ramdisk start = 0x4100, ramdisk end = 0x4100 > >XIP Kernel Image ... OK > > This "XIP" points to a problem. In essence I think you should try to > load your image to any address in RAM but _not_ to the load address > specified in the uImage. The intention of this field is to tell U-Boot > where the uImage file - that could reside on nor flash for exmple - > should be loaded to in RAM before it is executed. You have specified > 4008000 at image creation time but already load uImage that has a > 64-byte header prepended to that location. U-Boot in term finds that > the image is alreday where it should be, does nothing and switches to > XIP mode and then gets pretty confused. > > So again, try loading the image somewhere else in RAM and let U-Boot do > the copying to the correct place. > > And even better, we consider uImages to be legacy for quite a while, so > please plan to switch to using FIT images sometime soon. > > Cheers > Detlev > > -- > This is not the first time my views on some topic have inspired in > someone the desire to psychoanalyze me. Previous experience leads me > to ask about your couch. Is it comfortable? Are its springs in good > shape? -- Jonh McCarthy > -- > DENX Software Engineering GmbH,
[U-Boot] booting os 'Unknown OS' (1) is not supported
Hello guys! I faced with a strange behaviour of u-boot. Few months ago i bought an ARM development board from yicsystem it's based on exynos 5250 and very similar to arndale http://www.yicsystem.com/products/low-cost-board/yse5250/ And i can boot Android ICS but when i try to boot any linux i always see Checking Boot Mode ... SDMMC Now running in RAM - U-Boot at: c3e0 REVISION: 1.0 REVISION: 1.0 MMC Device 0: 3839 MB NAME: S5P_MSHC0 MMC Device 1: 7348 MB MMC Device 2 not found Destroy Hash Table: c3f80f78 table = (null) Create Hash Table: N=512 INSERT: table c3f80f78, filled 1/521 rv c3d047a0 ==> name="baudrate" value="115200" INSERT: table c3f80f78, filled 2/521 rv c3d0582c ==> name="bootargs" value="root=/dev/mmcblk0p1" INSERT: table c3f80f78, filled 3/521 rv c3d04a1c ==> name="bootcmd" value="movi read kernel 0 40008000;movi read rootfs 0 4100 10;bootm 40008000 4100" INSERT: table c3f80f78, filled 4/521 rv c3d04f20 ==> name="bootdelay" value="3" INSERT: table c3f80f78, filled 5/521 rv c3d04bfc ==> name="bootfile" value="/tftpboot/revoboot/bin/revoboot.pxe" INSERT: table c3f80f78, filled 6/521 rv c3d040a4 ==> name="emmcbootrecovery" value="mmc erase boot 1 0 0;emmc open 1;movi read fwbl1 0 4000;movi write zero fwbl1 1 4000;movi read bl2 0 40004000;movi write zero bl2 1 40004000;movi read u-boot 0 4200;movi write zero u-boot 1 4200;movi read tzsw 0 4210;movi write zero tzsw 1 4210;emmc close 1" INSERT: table c3f80f78, filled 7/521 rv c3d04998 ==> name="ethact" value="smc911x-0" INSERT: table c3f80f78, filled 8/521 rv c3d0462c ==> name="ethaddr" value="00:40:5c:26:0a:5b" INSERT: table c3f80f78, filled 9/521 rv c3d057a8 ==> name="gatewayip" value="192.168.0.1" INSERT: table c3f80f78, filled 10/521 rv c3d05874 ==> name="ipaddr" value="192.168.0.28" INSERT: table c3f80f78, filled 11/521 rv c3d048c0 ==> name="netmask" value="255.255.255.0" INSERT: table c3f80f78, filled 12/521 rv c3d05214 ==> name="rootfslen" value=" 10" INSERT: table c3f80f78, filled 13/521 rv c3d048e4 ==> name="serverip" value="192.168.0.13" INSERT: free(data = c3d00010) INSERT: done Net: smc911x-0 ### main_loop entered: bootdelay=3 ### main_loop: bootcmd="movi read kernel 0 40008000;movi read rootfs 0 4100 10;bootm 40008000 4100" Hit any key to stop autoboot: 0 reading kernel..device 0 Start 1063, Count 16384 MMC read: dev # 0, block # 1063, count 16384 ... 16384 blocks read: OK completed reading RFS..device 0 Count 17447, Start 2048 MMC read: dev # 0, block # 17447, count 2048 ... 2048 blocks read: OK completed ## Current stack ends at 0xc3cfbd98 * kernel: cmdline image address = 0x40008000 ## Booting kernel from Legacy Image at 40008000 ... Image Name: Linux-3.12.0-rc1-armv7-x0.6-0012 Image Type: ARM Linux Kernel Image (uncompressed) Data Size:3243400 Bytes = 3167 KiB Load Address: 40008000 Entry Point: 40008000 Verifying Checksum ... OK kernel data at 0x40008040, len = 0x00317d88 (3243400) * ramdisk: cmdline image address = 0x4100 Wrong Ramdisk Image Format ramdisk start = 0x4100, ramdisk end = 0x4100 XIP Kernel Image ... OK OK kernel loaded at 0x40008000, end = 0x4031fd88 images.os.start = 0x40008000, images.os.end = 0x4031fdc8 images.os.load = 0x40008000, load_end = 0x4031fd88 *ERROR: booting os 'Unknown OS' (1) is not supported* Unknown OS. But i do not understand what i should change to proceed. Any suggestions? ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
