Thanks Robert!!! The information/education we're getting from this site is really helpful!!
Changed board.c::board_fit_config_name_match(..) to always return '0', but the MLO/SPL appears to be stuck at the same place... Since the MLO/SPL, is printing out its startup string on console, tomorrow I will try to print out the MLO/SPL's board ID to the console or some other debug interface, and then update this thread if successful. Also, I may be dd'ing the MLO and u-boot image to the SD card incorrectly, as I get >>> Created a new DOS disklabel with disk identifier 0xad1707b9. Start sector 8192 out of range. Failed to add partition: Numerical result out of range After the sudo sfdisk step.. Regards, jeff On Sunday, June 11, 2017 at 12:08:16 PM UTC-5, RobertCNelson wrote: > > On Sun, Jun 11, 2017 at 11:54 AM, Jeff Andich <jeff....@gmail.com > <javascript:>> wrote: > > in the 2017.01 u-boot, I attempted to change the default device tree > that > > u-boot is using to see if that would allow u-boot to boot on the 5718 > IDK, > > but the console output still stops just after the SPL prints its output > > (please see below). I get the same result regardless of whether I use > the > > 2017.01 vs TI SDK's board/ti/am57xx/ IO pad configuration in > mux_data.h. I > > believe that for all of the builds I have tried, 2017.01 u-boot seems to > > boot on the 572x EVM. > > > > To attempt to change the device tree which u-boot uses: > > > > In configs/am57xx_evm_defconfig: > > > > changed CONFIG_DEFAULT_DEVICE_TREE="am572x-idk" to > > > > CONFIG_DEFAULT_DEVICE_TREE="am57xx-beagle-x15" /* I did this because > TI > > SDK's u-boot assigns the am57xx-beagle-x15 device tree name */ > > (just noticed before hitting reply) Oh fudge, did they fubar the eeprom? > > > > > Then re-built the 2017.01 u-boot. > > > > Note: When I re-built 2017.01 u-boot, I re-used the am57xx-beagle-x15 > dts > > file within the 2017.01 u-boot file tree. I did not copy > > the am57xx-beagle-x15.dts or #included dtsi files from the TI SDK file > tree. > > The dts files with the same name are different in the two trees. > > > > 1) Am I barking up the right tree? > > i'd expect it to just work with ti's tree... > > > > > 2) Robert, when you ran the BeagleBoard-X15 image on the 571x IDK, what > > u-boot defconfig, u-boot device tree, and pad mux did you use? > > It was a am571x "based" board, not the IDK (i don't have the idk).. > It boots the exact same X15 image.. > > > > > 3) Does this console output mean that SPL has jumped to u-boot, but > u-boot > > has not started up correctly? > > > > > > > > Thanks a lot in advance!!!! > > > > > > Console Output: > > ************************** > > > > U-Boot SPL 2017.01-00319-g9fb6b936b8 (May 16 2017 - 10:31:53) > > DRA722-GP ES2.0 > > Trying to boot from MMC1 > > > > ** Unable to use mmc 0:1 for loading the env ** > > Using defau environment > > > > > > This means you only got into the MLO file (u-boot spl), it never made > the jump to u-boot.img > > i think your stuck here: > > > http://git.ti.com/gitweb/?p=ti-u-boot/ti-u-boot.git;a=blob;f=board/ti/am57xx/board.c;h=b8798d6f2a24c58a24ace604939182fa49d2f883;hb=refs/heads/ti-u-boot-2017.01#l1050 > > > change the -1 to a 0, it should catch the > > 1046 } else if (board_is_am571x_idk() && !strcmp(name, > "am571x-idk")) { > 1047 return 0; > 1048 } > > but it's not.. > > 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 beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/ee1d97e8-8878-4cd2-afbc-e60b8ecaa91a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
