Hi Robert, Here's what I'm seeing so far, what I've tried, and what's coming to mind to try to get the debian 8.8 image going on the 571x IDK:
*When our 5718 IDK, is booting the bbx15-debian-8.8-lxqt-4gb-armhf-2017-06-04-4gb.img image from SD Card, the console output dies shortly after the SPL startup string (see below). *The debian 8.8 LXQT image boots fine on out 572x EVM (console output of 2017.01 u-boot shown below). *The latest TI SDK image, am57xx-evm-03.03.00.04 boots ok on both the 5718 IDK and 5728 EVM (boot console printed below). * After thinking the problem could be related to pinmux issues, I built the 2017.01 u-boot , but substituted the TI SDK's pad config. file, mux_data.h for the mux_data.h in 2017.01 u-boot. I then "dd-ed" just the MLO and u-boot.img to an SD Card ( per https://eewiki.net/display/linuxonarm/BeagleBoard-X15#BeagleBoard-X15-SetupmicroSDcard), and booted the 5718 IDK, but I apparently get the same result (console dies after SPL). *Am not sure what to try next, but am wondering if getting u-boot to load the am571x-idk.dtb instead of am57xx-evm-reva3.dtb would help. I can't see whether the TI SDK image is loading a different dtb for the 571x vs the 572x as it doesn't appear to advertise this during bootup. * Also wondering if it has anything to do with the different DDR3 configuration on the 572x EVM (4 DDR3 chips on 2 EMIFs) vs. 571X IDK (2 DDR3 chips on 1 EMIF). Please let me know what to try next... Thanks a lot in advance!! jeff Following are the different boot console outputs of interest: ***************************************************************************************************************** * Console Output 2017.01 u-boot image substituting TI SDK's mux_data.h file --------- 571x IDK. * ***************************************************************************************************************** (Note: I get the same output (except for the dirty qualifier if I boot the 571x with the stock debian 8.8 lxqt image). (Note: Just dd'ed the MLO and u-boot.img files to the SD Card - omitted the kernel and FS.) U-Boot SPL 2017.01-00318-g9fd6070-dirty (Jun 09 2017 - 09:06:) DRA722-GP ES2.0 Trying to boot from MMC1 ** Unable to use mmc 0:1 for loading the env ** Using default environment ***************************************************************************************************************** * Console Output 2017.01 u-boot image substituting TI SDK's mux_data.h file --------- 572x EVM. * ***************************************************************************************************************** (Note: Just dd'ed the MLO and u-boot.img files to the SD Card - omitted the kernel and FS.) U-Boot SPL 2017.01-00318-g9fd6070-dirty (Jun 09 2017 - 09:06:15) 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-00318-g9fd6070-dirty (Jun 09 2017 - 09:06:15 -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 setup_board_eeprom_env: am57xx_evm_reva3 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 Press SPACE to abort autoboot in 2 seconds usb_boot is currently disabled scsi_boot is currently disabled switch to partitions #0, OK mmc0 is current device Scanning mmc device 0 Checking for: /uEnv.txt ... Failed to mount ext2 filesystem... ** Unrecognized filesystem type ** Checking for: /boot/uEnv.txt ... Failed to mount ext2 filesystem... ** Unrecognized filesystem type ** ** Invalid partition 2 ** ** Invalid partition 3 ** ** Invalid partition 4 ** ** Invalid partition 5 ** ** Invalid partition 6 ** ** Invalid partition 7 ** switch to partitions #0, OK mmc1(part 0) is current device Scanning mmc device 1 Checking for: /uEnv.txt ... Checking for: /boot/uEnv.txt ... ** Invalid partition 4 ** ** Invalid partition 5 ** ** Invalid partition 6 ** ** Invalid partition 7 ** => ***************************************************************************************************************** * Console Output TI SDK 03.03.00.04 image on 5718 IDK - written to SD Card using their shell script. ***************************************************************************************************************** U-Boot SPL 2016.05-g4db46a6bbd (Mar 29 2017 - 23:25:16) DRA722-GP ES2.0 Trying to boot from MMC1 reading args spl_load_image_fat_os: error reading image args,rr - -1 reading u-boot.img reading u-boot.img reading u-boot.img reading u-boot.img U-Boot 2016.05-g4db46a6bbd (Mar 29 2017 - 23:25:16 -0400) CPU : DRA722-GP ES2.0 Model: AM5718 IDK Board: AM571x IDK REV 1.3B DRAM: 1 GiB MMC: no pinctrl for sdr104 no pinctrl for ddr50 no pinctrl for sdr50 no pinctrl fordr25 no pinctrl for sdr12 OMAP SD/MMC: 0, OMAP SD/MMC: 1 reading uboot.env ** Unable to read "uboot.env" from mmc0:1 ** Using default environment am57x_idkcd_detect: Touch screen detect failed: 1 SCSI: SATA link 0 timeout. AHCI 0001.0300 32 slots 1 ports 3 Gbps 0 impl SATA mode flags: 64bit ncq stag pm led clo only pmp pio slum part ccc ap scanning bus for devices... Found 0 device(s). Net: Warning: ethernet@48484000 using MAC address from ROM eth0:thernet@48484000 Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0 is current device SD/MMC found on device 0 reading boot.scr ** Unable to read file boot.scr ** reading uEnv.txt 574 byt read in 5 ms (111.3 KiB/s) Loaded env from uEnv.txt Importing environment from mmc0 ... switch to partitions #0, OK mmc0 is current device SD/MMC found on device 0 3602144 bytes read in 204 ms (16.8 MiB/s) 99658 bytes read in 50 ms (1.9 MiB/s) Kernel image @ 0x820000 [ 0x000000 - 0x36f6e0 ] ## Flattened Device Tree blob at 88000000 Boing using the fdt blob at 0x88000000 Loading Device Tree t8ffe4000, end 8ffff549 ... OK Starting kernel ... [ 0.000000] Booting Linux on physical CPU 0x0 . . . Arago 2016.12 a7xx-evm ttyS2 ***************************************************************************************************************** * Console Output TI SDK 03.03.00.04 image on 5728 EVM - written to SD Card using their shell script. ***************************************************************************************************************** U-Boot SPL 2016.05-g4db46a6bbd (Mar 29 2017 - 23:25:16) DRA752-GP ES2.0 Trying to boot from MMC1 reading args spl_load_image_fat_os: error reading image args, err - -1 reading u-boot.img reading u-boot.img reading u-boot.img reading u-boot.img U-Boot 2016.05-g4db46a6bbd (Mar 29 2017 - 23:25:16 -0400) CPU : DRA752-GP ES2.0 Model: TI AM5728 BeagleBoard-X15 Board: AM572x EVM REV A.3A DRAM: 2 GiB MMC: no pinctrl for sdr104 no pinctrl for ddr50 no pinctrl for sdr50 no pinctrl for sdr25 no pinctrl for sdr12 OMAP SD/MMC: 0, OMAP SD/MMC: 1 reading uboot.env ** Unable to read "uboot.env" from mmc0:1 ** 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: Warning: ethernet@48484000 using MAC address from ROM eth0: ethernet@48484000 Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0 is current device SD/MMC found on device 0 reading boot.scr ** Unable to read file boot.scr ** reading uEnv.txt 574 bytes read in 5 ms (111.3 KiB/s) Loaded env from uEnv.txt Importing environment from mmc0 ... switch to partitions #0, OK mmc0 is current device SD/MMC found on device 0 3602144 bytes read in 199 ms (17.3 MiB/s) 103020 bytes read in 55 ms (1.8 MiB/s) Kernel image @ 0x82000000 [ 0x000000 - 0x36f6e0 ] ## Flattened Device Tree blob at 88000000 Booting using the fdt blob at 0x880 00000 Loading Device Tree to 8ffe3000, end 8ffff26b ... OK Starting kernel ... [ 0.000000] Booting Linux on physical CPU 0x0 . . . Arago 2016.12 am57xx-evm ttyS2 On Tuesday, June 6, 2017 at 2:43:04 PM UTC-5, Jeff Andich wrote: > > > Thanks a lot Robert!! > > Will update what happens here... Regards, Jeff > > > On Tuesday, June 6, 2017 at 2:15:27 PM UTC-5, Jeff Andich wrote: >> >> Hi, >> >> Does the BeagleBoard-X15 image run, out of the box on the 5718 Industrial >> Development Kit (IDK) in addition to the 572x EVM or are configuration >> changes needed to the image to make it compatible with the 5718 IDK? >> >> Has anyone tried this specific configuration with the BB-X15 image? >> We're running with the BeagleBoard-X15 image on the 572x EVM, literally >> out of the box. Debian on the BB-X15 image facilitates testing by our >> software team. >> >> We're at a crucial decision point on whether to design-in the am5718 vs >> the am5728 chip on a board. >> >> Any information is greatly appreciated!! >> >> Thanks! >> >> >> >> -- 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/35ce5d1d-73cf-4464-b38d-be9762504f90%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
