Ok, I did a quick tree diff on the patched 2017.01 u-boot from last-Thursday vs. the patched 2017.01 u-boot from today. Looks like there were some additional board variants that were potentially being supported in last-Thursday's patch, but I don't see that in today's patched 2017.01 u-boot. If it's worthwhile to analyze what the differences are, let me know... If not, I'm just happy to move on..
Thanks! jeff. On Monday, July 24, 2017 at 10:34:24 AM UTC-5, Jeff Andich wrote: > > Ok, > > ???I must have done something wrong before or something really weird > happened??? As TODAY when I git pull the TI patches from TI and apply the > beagleX15 patch file, it works on my 572XEVM_ES2.X (with the > touchscreen/LCD removed). For some reason, when I tried this last-Thursday > (late afternoon CST), nothing would print to the console. > I'm still using the same linaro > toolchain, gcc-linaro-5.4.1-2017.01-x86_64_ ... > > > Thanks and FYI! > > jeff > > ************************************ > > U-Boot SPL 2017.01-00355-g6f3f23b (Jul 24 2017 - 10:17:22) > DRA752-GP ES2.0 > Trying to boot from MMC1 > > ** Unable to use mmc 0:1 for loading the env ** > Using default environment > > > > U-Boot 2017.01-00355-g6f3f23b (Jul 24 2017 - 10:17:22 -0500) > > CPU : DRA752-GP ES2.0 > Model: TI AM572x EVM Rev A3 > Board: AM572x EVM REV A.3A > DRAM: 2 GiB > MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1 > > ** Unable to use mmc 0:1 for loading the env ** > Using default environment > > SCSI: SATA link 0 timeout. > AHCI 0001.0300 32 slots 1 ports 3 Gbps 0x1 impl SATA mode > flags: 64bit ncq stag pm led clo only pmp pio slum part ccc apst > scanning bus for devices... > Found 0 device(s). > Net: <ethaddr> not set. Validating first E-fuse MAC > cpsw > Hit any key to stop autoboot: 0 > switch to partitions #0, OK > mmc0 is current device > SD/MMC found on device 0 > Failed to mount ext2 filesystem... > ** Unrecognized filesystem type ** > ** Unrecognized filesystem type ** > switch to partitions #0, OK > mmc0 is current device > SD/MMC found on device 0 > ** Invalid partition 2 ** > switch to partitions #0, OK > mmc1(part 0) is current device > SD/MMC found on device 1 > reading /boot/zImage > ** Unable to read file /boot/zImage ** > => > > > When I build it with the older toolchain (gcc-linaro-5.4.1-2017.01), it > works today! > > On Friday, July 21, 2017 at 9:11:01 PM UTC-5, Jeff Andich wrote: >> >> Thanks Robert!! >> >> Sorry to eat into your weekend again... >> >> My toolchain (5.4.1-2017.01) is a little older than the one on eewiki. >> Will upgrade it and retry. >> >> Rgds, jeff >> >> >> On Friday, July 21, 2017 at 8:40:53 PM UTC-5, RobertCNelson wrote: >>> >>> On Fri, Jul 21, 2017 at 10:56 AM, Jeff Andich <[email protected]> >>> wrote: >>> > Don't know if this is a useful or erroneous datapoint, but I tested >>> the >>> > above steps (2017.01 branch of u-boot with latest TI git tree merged >>> in but >>> > patching with the older version of the 0001 .... bootz-n-fixes patch >>> file), >>> > and my 572xEVM appears dead... >>> >>> Okay this is what i get with teh 572x evm >>> >>> U-Boot SPL 2017.01-00349-g756f5e76a1 (Jul 06 2017 - 16:42:25) >>> DRA752-GP ES2.0 >>> Trying to boot from MMC1 >>> >>> ** Unable to use mmc 0:1 for loading the env ** >>> Using default environment >>> >>> <repeats> >>> >>> Regards, >>> >>> -- >>> Robert Nelson >>> https://rcn-ee.com/ >>> >> -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/e8d6bce0-34ae-4f7b-8625-61360d5b3498%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
