Hi Henrik, Thanks for replying - I have made an error (too much programming I guess), it's a bit different actually - the start address for script is BOOT1_BASE+BOOT1_HEAD_LENGTH - this is then memcpy-ed to SCRIPT_BASE. Either way, it's using the script embedded in its header, as you've said.
However, I thought that I should build Boot1 with disabled SCRIPT_INSTALL_EARLY and then it'd fetch the actual script.bin. Your solution is also good, but can you tell me which pack tool can I use to repack Boot1? I'm going to use NAND boot for finished product (SD or NFS for development) - somehow the idea of Boot1 is not bad, as it's relatively easy to change boot logo images and battery charging images. My only problem with it is that I can't build it so I could customize the script file (ok, it's also behaving a bit erratically as sometimes it boots when you plug in OTG, sometimes it goes to standby, but this could also easily be because of bad HW design). Also, up to now I've been fixing kernel and doing some userland apps, but never had much contact with uboot sources (I'm almost always using some precompiled binary for it), but honestly the code looks much more complex (somewhat similar to kernel code) - I'm not really sure that Battery charging / Logos could be controlled so easily as with Boot1. Although, as I said - I'm really not familiar with uboot sources... Still I'd be quite interested in trying out this WiP NAND uboot - do you know from which repo can I fetch the source/binaries? Maybe it's time that I get familiar with uboot... Regards, Ivan On Tuesday, July 22, 2014 10:56:25 PM UTC+2, Henrik Nordström wrote: > > mån 2014-07-21 klockan 09:08 -0700 skrev Ivan Kozic: > > Ok, I have some updates - it seems that my Boot1 was compiled with > > SCRIPT_INSTALL_EARLY, so it doesn't fetch script.bin, but instead > > looks at SCRIPT_BASE. Not really sure what's happening there, but I > > recompiled drv_de.drv and using some printfs (__inf), I can verify > > that Boot1 gets the old PH07 instead of new PB04 (PB04 is set in > > script.bin). > > So it's using the script.bin embedded in it's header? > > If that is the case then you need to reinstall boot1 to update > script.bin. I.e. repack the firmware and install it with livesuit. > > > > However, there are a lot of errors when I attempt to recompile the > > complete Boot1 package, and I don't even know where the result goes, > > or how is 'make' used here - Boot1 is split across multiple folders, > > so even Makefiles are hard to track. > > I am not aware of anyone outside Allwinner that have succeeded in > building boot0 & boot1. Have only used the sources as reference. > > It is known it is a bit picky on which toolchain is being used to build > it. > > Our focus is still to replace boot0/boot1 entirely, using u-boot all the > way both on SD/MMC (stable for years) and NAND (work in progress). > > Regards > Henrik > > > -- 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.
