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).
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. So, if someone has any further info on this, I'd be very grateful for sharing. On Saturday, July 19, 2014 5:19:29 PM UTC+2, Ivan Kozic wrote: > > Hi all, > > I'm having trouble finding some infos regarding Boot0/Boot1 bootloaders - > I need some GPIO control during boot and I also want to try to change the > part of it which has magic number checking for NAND implemented. > So far I have found only some general things about it on linux-sunxi.org > and I'm currently going through the code to figure it out more (I've cloned > hno/allwinner-boot), but some pointers or reading would be nice. > > My current GPIO Boot1 problem: > > I am booting off NAND with Olinuxino-A20 and I've changed the lcd_bl_en > pin from PH07 to PB04 in my fex file, recompiled binary script.bin and > copied it to /dev/nanda. I've also changed the actual physical connection > on the pcb. After the kernel boots, it's the same as before - backlight > working normally. However, during power-up, until the kernel LCD driver > kicks in, the LCD is blank and I can no longer see the Boot1 logo (haven't > changed it - still says Allwinner A20 Dual Core or something) - I just see > the glimpse of it when kernel fires up the backlight. So for Boot1 (which > inits the LCD also during LiPo charging), nothing's changed - BL_EN is > still at PH07. This is why I've decided to change it in the source. > > However, the Boot1 source is quite messy for my taste and I also see > references to script_parsers in the source like for regular linux kernel > drivers, so it seems to also parse the script, but maybe not script.bin. > > So, if someone's got any info on this it'd be quite nice to share. > Thanks in advance! > -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
