Hi Neal, Thanks for that.
I have no idea about the magic signing value, I have 3 questions and comments: 1> If I just use the original nandb.img which was dd out of the nand itself, will that still be needed? 2> if I do create a magic signing value again, how would I do that? 3> would this why my previous lichee-dev u-boot.bin doesn't play well with boot0/boot1? did I miss any magic value there? Thanks, -Hunter On Sunday, March 9, 2014 1:25:42 PM UTC-5, npeacock wrote: > > Hello, > > Seems like the structure was > > /dev/nandb < u-boot.env with magic signing value > /dev/nandc < the linux kernel, just dd copied on, make sure to clear with > zero in case yours its smaller > /dev/nandX < the root partition, which was defined in the u-boot.env, so > you could make it whatever you want, as long as it matches your env file. > If nandj is 5Gb then that is what I would use in my hacky approach. > > So is that more clear? You'll need to put your linux kernel in nandc, > your adjusted uboot.env in nandb and your rootfs on a new partition on nandj > > I'll try to find the actual script and old images tonight. I was having a > lot of trouble uploading large files and hadn't tried in awhile. > > Thanks. > > On 3/9/2014 11:07 AM, hunter hu wrote: > > Hi Neal, > > The link seems broken while I was trying to get the image: wget > http://pengpod.com/dl/images/pengpod1000-linaro-flashcard-2013.03.29.img.tar.gz > > However, I can set things up by following the same logic, but I need to > confirm one change, for nandb, what changes need to be made? I plan to edit > binary image out from my board, there are actually 2 entries for the > environment, > > one setup root=/dev/nandc > the other setup root=/dev/nandd > > according to your notes, we will dd uImage into nandc, so say, if I will > use nandj (which is 5G in size) as the rootfs, should I change the both > nandc and nandd to nandj or just nandd to nandj? > > Thanks, > -Hunter > > On Saturday, March 8, 2014 10:54:28 PM UTC-6, npeacock wrote: >> >> Here is a link for what I did on the PengPod where we used the original >> u-boot from Android. >> http://pengpod.com/pengwiki/index.php?title=Install_Linaro_to_the_internal_flash >> >> >> The only trick not listed was the u-boot environment had to be signed, I >> can't remember the name of the tool but its in the u-boot repo. >> >> I think the first logo was displayed by boot1, before u-boot runs. >> >> >> >> >> Hi Timo, >> >> Thanks for the detailed answer to my questions, really appreciate that. >> >> I have done the same thing, still I am stuck at the logo screen, feels >> like there is something else is missing in my case. >> >> 1> I don't see any serial output from NAND boot, did you see anything >> on the serial console if you were using serial output? >> 2> anyone knows if the logo has been displayed, does it imply that >> u-boot.bin got loaded at all? >> >> I think in my case, the question is why u-boot.bin built from >> sun5i_a13 with the CONFIG_BOOTCOMMAND modification doesn't print any output >> at all? in the common/main.c: >> 205 static inline int abortboot(int bootdelay) >> >> >> 206 { >> 207 int abort = 0; >> 208 >> 209 #ifdef CONFIG_MENUPROMPT >> 210 printf(CONFIG_MENUPROMPT); >> 211 #else >> 212 printf("Hit any key to stop autoboot: %2d ", bootdelay); >> 213 #endif >> >> would always print "Hit any key to stop autoboot:", even if something >> went wrong later? but I saw nothing from console, (UART1 that is I am using >> and good with SD boot). >> >> Still baffled, :-( >> >> Regards, >> -Hunter >> >> >> >> On Saturday, March 8, 2014 1:07:44 PM UTC-6, Timo Schmiade wrote: >>> >>> Hi Patrick, >>> >>> > Looks to me like this is loading script.bin and uImage from nanda. >>> >>> thanks for pointing this out, you're of course right! nandb contains >>> my root filesystem, nanda is the boot partition. >>> >>> On Sat, Mar 8, 2014 at 3:24 PM, Patrick Wood <patric...@gmail.com> >>> wrote: >>> > >>> > Looks to me like this is loading script.bin and uImage from nanda. >>> > >>> > -- >>> > You received this message because you are subscribed to a topic in the >>> Google Groups "linux-sunxi" group. >>> > To unsubscribe from this topic, visit >>> https://groups.google.com/d/topic/linux-sunxi/omgs3skJYDI/unsubscribe. >>> > To unsubscribe from this group and all of its topics, send an email to >>> linux-sunxi...@googlegroups.com. >>> > For more options, visit https://groups.google.com/d/optout. >>> >> -- >> You received this message because you are subscribed to the Google Groups >> "linux-sunxi" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to linux-sunxi...@googlegroups.com. >> For more options, visit https://groups.google.com/d/optout. >> >> >> -- > You received this message because you are subscribed to the Google Groups > "linux-sunxi" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to linux-sunxi...@googlegroups.com <javascript:>. > For more options, visit https://groups.google.com/d/optout. > > > -- You received this message because you are subscribed to the Google Groups "linux-sunxi" group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
