Does the Latest BeagleBoard-X15 Image Run Out of the Box on The Sitara am571x IDK?
489 views
Skip to first unread message
Jeff Andich
Jun 6, 2017, 3:15:27 PM6/6/17
to BeagleBoard
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!
Robert Nelson
Jun 6, 2017, 3:20:26 PM6/6/17
to Beagle Board, Jeff Andich
Hi Jeff,
Give the 2017-06-04 snapshot a shot:
https://rcn-ee.net/rootfs/bb.org/testing/2017-06-04/
There's one am571x based device off the x15 that i know it personally
boots just fine on..
the 5718 idk 'should' work, but please test it and give us a serial
boot log if there is is issues.
Regards,
--
Robert Nelson
https://rcn-ee.com/
https://rcn-ee.net/rootfs/bb.org/testing/2017-06-04/
There's one am571x based device off the x15 that i know it personally
boots just fine on..
the 5718 idk 'should' work, but please test it and give us a serial
boot log if there is is issues.
Regards,
--
Robert Nelson
https://rcn-ee.com/
Jeff Andich
Jun 6, 2017, 3:43:04 PM6/6/17
to BeagleBoard
Thanks a lot Robert!!
Will update what happens here... Regards, Jeff
Jeff Andich
Jun 9, 2017, 4:25:49 PM6/9/17
to BeagleBoard
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
Jeff Andich
Jun 11, 2017, 12:54:21 PM6/11/17
to BeagleBoard
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 */
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?
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?
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
..Additional Console Outputs Below..
Robert Nelson
Jun 11, 2017, 1:08:16 PM6/11/17
to Beagle Board, Jeff Andich
On Sun, Jun 11, 2017 at 11:54 AM, Jeff Andich <jeff....@gmail.com> 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?
> 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 */
>
> 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?
>
> 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 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
>
>
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..
Jeff Andich
Jun 11, 2017, 2:03:32 PM6/11/17
to BeagleBoard, jeff....@gmail.com
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
Jeff Andich
Jun 12, 2017, 4:45:10 PM6/12/17
to BeagleBoard, jeff....@gmail.com
Hi Robert,
Yesterday, I built u-boot wrong after making your recommended change to board/ti/am57xx/board.c. The build date on my u-boot from yesterday was showing May 16, 2017.
When I made your recommended change in another 2017.01 u-boot tree on another VM, the change allowed my 571x/5718 IDK to get to u-boot (see below).
I'm sorry, I should have noticed the build date issue yesterday!!
My console output thus far follows. Please note that this build of u-boot pulls in the default device tree for 2017.01 u-boot CONFIG_DEFAULT_DEVICE_TREE="am572x-idk" and the TI SDK's mux_data.h file
!!!!! Thanks a lot for your help yesterday !!!!!!!
I think our board engineer is designing in the 5728 at this point, but I'll relay these results to the manager and team.
**** Console Output after making change.
U-Boot SPL 2017.01-00318-g9fd6070-dirty (Jun 12 2017 - 15:31:55)
DRA722-GP ES2.0
Trying to boot from MMC1
** First descriptor is NOT a primary desc on 0:1 **
** No partion table - mmc 0 **
Using default environment
U-Boot 2017.01-00318-g9fd6070-dirty (Jun 12 2017 - 15:31:5-0500)
CPU : DRA722-GP ES2.0
Model: TI AM5728 BeagleBoard15
Board: AM571x IDK REV 1.3B
DRAM: 1 GiB
MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1
CACHE: Misaligned operation at range [bffbb290, bffbba90]
** rst descriptor is NOT a primary desc on 0:1 **
** No partition table - mmc 0 **
Usindefault environment
setup_board_eeprom_env: am571x_idk
am5_idk_lcd_detect: Touch screen detect failed: 1!
SCSI: SATA link 0 timeout.
AHCI 0001.0300 32 slots 1 ports 3 Gbps 0x1 impl SATA mode
fgs: 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 SCE to abort autoboot in 2 seconds
usb_boot is currently disabled
scsi_boot is currently disabled
CACHE: Misaligned operation at range [bffbb290, bffbba90]
** rst descriptor is NOT a primary desc on 0:1 **
switch to partions #0, OK
mmc0 is current device
CACHE: Misaligned operation at range [bffbb290, bffbba90]
** First descriptor is NOT a priry desc on 0:1 **
Scanning mmc device 0
Checking for: /uEnv.t ...
** No partition table - mmc 0 **
Checking for: /boot/uEnv.txt ...
** No partition table - mmc 0 **
** partition table - mmc 0 **
* No partition table - mmc 0 ***
** No partition table - mmc 0 **
** No partition table - mmc 0 **
** No partition tle - mmc 0 **
CACHE: Misaligned operation at range [bffbb290, bffbba90]
** First descriptor is NOT a primary desc on 1:1 **
switch toartitions #0, OK
mmc1(part 0) is current device
CACHE: Misaligned operation at range [bffbb290, bffbba90]
** First descriptor is NOT a pmary desc on 1:1 **
Scanning mmc device 1
Checking for: /uEntxt ...
** No partition table - mmc 1 **
Checking for: /boot/uEnv.txt ...
** No partition table - mmc 1 **
** No ptition table - mmc 1 **
** No partition table - mmc 1 **
** partition table - mmc 1 **
** No partition table - mmc 1 **
** No partition table - mmc 1 **
** No partition tabl- mmc 1 **
U-Boot SPL 2017.01-00318-g9fd6070-dirty (Jun 12 2017 - 15:31:55)
DRA722-GP ES2.0
Trying to boot from MMC1
** First descriptor is NOT a primary desc on 0:1 **
** No partion table - mmc 0 **
Using default environment
U-Boot 2017.01-00318-g9fd6070-dirty (Jun 12 2017 - 15:31:5-0500)
CPU : DRA722-GP ES2.0
Model: TI AM5728 BeagleBoard15
Board: AM571x IDK REV 1.3B
DRAM: 1 GiB
MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1
CACHE: Misaligned operation at range [bffbb290, bffbba90]
** rst descriptor is NOT a primary desc on 0:1 **
** No partition table - mmc 0 **
Usindefault environment
setup_board_eeprom_env: am571x_idk
am5_idk_lcd_detect: Touch screen detect failed: 1!
SCSI: SATA link 0 timeout.
AHCI 0001.0300 32 slots 1 ports 3 Gbps 0x1 impl SATA mode
fgs: 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 SCE to abort autoboot in 2 seconds
usb_boot is currently disabled
scsi_boot is currently disabled
CACHE: Misaligned operation at range [bffbb290, bffbba90]
** rst descriptor is NOT a primary desc on 0:1 **
switch to partions #0, OK
mmc0 is current device
CACHE: Misaligned operation at range [bffbb290, bffbba90]
** First descriptor is NOT a priry desc on 0:1 **
Scanning mmc device 0
Checking for: /uEnv.t ...
** No partition table - mmc 0 **
Checking for: /boot/uEnv.txt ...
** No partition table - mmc 0 **
** partition table - mmc 0 **
* No partition table - mmc 0 ***
** No partition table - mmc 0 **
** No partition table - mmc 0 **
** No partition tle - mmc 0 **
CACHE: Misaligned operation at range [bffbb290, bffbba90]
** First descriptor is NOT a primary desc on 1:1 **
switch toartitions #0, OK
mmc1(part 0) is current device
CACHE: Misaligned operation at range [bffbb290, bffbba90]
** First descriptor is NOT a pmary desc on 1:1 **
Scanning mmc device 1
Checking for: /uEntxt ...
** No partition table - mmc 1 **
Checking for: /boot/uEnv.txt ...
** No partition table - mmc 1 **
** No ptition table - mmc 1 **
** No partition table - mmc 1 **
** partition table - mmc 1 **
** No partition table - mmc 1 **
** No partition table - mmc 1 **
** No partition tabl- mmc 1 **
Jeff Andich
Jun 13, 2017, 6:25:14 PM6/13/17
to BeagleBoard, jeff....@gmail.com
Well right now we're moving forward with the BeagleBoard-X15 image on the 5728 part, but I'm still taking a look at booting the BB-X15 image on the 571x IDK - at least through today...
Today I re-imaged a 16 GB SD Card with the entire BB-X15 image file and then dd'ed just the re-built MLO and u-boot (with RCN's recommended fix for board.c) to the SD Card.
On the 571x IDK, the kernel boots, but when it mounts the FS, but it ends up in initramfs. The same SD card, when inserted in the am572x EVM boots and comes up with the debian login prompt.
I also tried a mixture of device trees (am57x-idk.dtb) am57xx-beagle-x15.dtb from the BeagleBoard-X15 image and TI SDK image, but each time, I'm still ending up in initramfs.
Here are excerpts from the boot console log on the 571x IDK. At the end of the console printout, there are some questions.
Let me know what else you would like to see.
Regards, jeff
**********************************************************************
U-Boot 2017.01-00318-g9fd6070-dirty (Jun 12 2017 - 17:07:01 -0500)
U : DRA722-GP ES2.0
Model: TI AM5728 BeagleBoard-X15
Board:M571x IDK REV 1.3B
DRAM: 1 GiB
MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1
** Unable to use mmc 0:1 for loading the env **
Using defau environment
setup_board_eeprom_env: am571x_idk
am57x_idk_lcd_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 piolum part ccc apst
scanning bus for devices...
Found 0 device(s).
Net: <ethaddr> not set. Validating first E-fu 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 ...
Checking for: /boot/uEnv.txt ...
582 bytes read in 47 ms (11.7 KiB/s)
Loaded environment from /boot/uE.txt
Checking if uname_r is set in /boot/uEnv.txt ...
debug:uname_r=4.4.68-ti-r107] ...
loading /boot/vmlinuz-4.4.68-ti-r107 ...
8806080 bytes read in 430 ms (19.5 MiB/s)
loading /boot/dtbs/4.4.68-ti-r107/am571x-idk.dtb ...
97660 bytes read in 114 ms (835.9 KiB/s)
loading /boot/initrd.img-4.4.68-ti-r107 ...
5336554 bytes read in 277 ms (18.4 MiB/s)
debug: [console=tty,115200n8 root=/dev/mmcblk0p1 ro rootfstype=ext4 rootwait coherent_pool=1M netfnames=0] ...
debug: [bootz 0x82000000 0x88080000:516dea 0x880000] ...
## Flattened Device Tree blob at 88000000
Booting using the fdt blob at 0x88000000
Loading Ramdisko 8fae9000, end 8ffffdea ... OK
Loading Device Tree to 8face000, end 8fae8d7b ... OK
Starting kernel ...
[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Initialing cgroup subsys cpuset
[ 0.000000] Initializing cgroup suys cpu
[ 0.000000] Initializing cgroup subsys cpuacct
[ 0.000000] Linux version 4.4.68-ti-r107 (root@a1-imq-wandboard-2gb) (gcc version 4.9.2 (Debian 4.9.2-10) ) #1 SMPr7
[ 0.000000] CPU: ARMv7 Processor [412fc0f2] revision 2 (ARMv7), cr=10c5387d
[ 0.0000] CPU: PIPT / VIPT nonaliasing data cache, PIPT instructionache
[ 0.000000] Machine model: TI AM5728 BeagleBoard-X15
[ 0.000000] Reserved memory: created CMA memory pooat 0x95800000, size 56 MiB
[ 0.000000] Reserved memory: inialized node ipu2_cma@95800000, compatible id shared-dma-pool
[ 0.000000] Reserved memory: created CMA memory po at 0x99000000, size 64 MiB
[ 0.000000] Reserved memory: itialized node dsp1_cma@99000000, compatible id shared-dma-pool
[ 0.000000] Reserved memory: created CMA memory pl at 0x9d000000, size 32 MiB
[ 0.000000] Reserved memory: itialized node ipu1_cma@9d000000, compatible id shared-dma-pool
[ 0.000000] Reserved memory: created CMA memory pl at 0x9f000000, size 8 MiB
[ 0.000000] Reserved memory: itialized node dsp2_cma@9f000000, compatible id shared-dma-pool
[ 0.000000] cma: Reserved 48 MiB at 0xbc800000
[ 0.000000] Memory policy: Data cache writealloc
[ 0.000000OMAP4: Map 0xbfe00000 to fe600000 for dram barrier
[ 0.000000] DRA722 ES2.0
[ 0.000000] PERCPU: Embedded 13 pes/cpu @ef63a000 s24320 r8192 d20736 u53248
[ 0.000000] But 1 zonelists in Zone order, mobility grouping on. Total pages: 210752
[ 0.000000] Kernel command line: console=yO2,115200n8 root=/dev/mmcblk0p1 ro rootfstype=ext4 rootwait cerent_pool=10
[ 0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
[ 0.000000] Dent cache hash table entries: 131072 (order: 7, 524288 bytes)
[ 0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[ 0.000000] Memory: 604496K/849920K avlable (11546K kernel code, 938K rwdata, 3884K rodata, 752K ini 909K bss, 3243)
[ 0.000000] Virtual kernel memory layout:
[ .000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB)
[ 0.000000] fixmap : 0xffc00000 - 0xfff00000 (3072 kB)
[ 0.000000] vmalloc : 0xf0800000 - 0xff800000 240 MB)
[ 0.000000] lowmem : 0xc0000000 - 0xf0000000 ( 768 MB)
[ 0.000000] pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
[ 0.000000] modules : 0xbf000000 0xbfe00000 ( 14 MB)
[ 0.000000] .text : 0xc000800- 0xc0f19e28 (15432 kB)
[ 0.000000] .init : 0xc0f1a000 - 0xc0fd6000 ( 752 kB)
[ 0.000000] .dat: 0xc0fd6000 - 0xc10c08b0 ( 939 kB)
[ 0.000000] .s : 0xc10c3000 - 0xc11a64a8 ( 910 kB)
[ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
.
.
.
[ 77.359804] remoteproc0: releasing 4b2b8000.pru1
[ 77.364642] p-rproc: probe of 4b2b8000.pru1 failed with error -2
Begin: Loading essential drivers ... done.
Begin: Running /scpts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
gin: Running /scripts/local-premount ... done.
Begin: Waiting for root file system ... Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
.
.
.
Gave up waiting for root device. Common problems:
- Boot args (cat /pc/cmdline)
- Check rootdelay= (did the system wait long engh?)
- Check root= (did the system wait for the right devi?)
- Missing modules (cat /proc/modules; ls /dev)
ALERT! /dev/mmcblk0p1 does not exist. Dropping to a shell!
morobe: module i8042 not found in modules.dep
modprobe: module ci-orion not found in modules.dep
modprobe: module uhci-hcd not found in modules.dep
modprobe: module ohci-hcd not und in modules.dep
BusyBox v1.22.1 (Debian 1:1.22.0-9+deb1) built-in shell (ash)
Enter 'help' for a list of built-in commands.
/bin/sh: can't access tty; job control turn off
(initramfs)
*******************************************************************
**Questions:
1) Sunday, you spotted that the EEPROM data on the 571x IDK is corrupt (to some extent). Since my board is now able to boot all the way through the kernel to initramfs, should I worry about the SPL having incorrectly setup the IO PAD configuration stuff due to the wrong board ID, or would that not matter since the kernel has booted?
2) Should I worry more about the kernel loading the correct device tree?
3) I probably created the SD Card in a potentially dangerous way - just overwriting the existing MLO and u-boot on the BeagleBoard-X15 image without following all of the steps here ( https://eewiki.net/display/linuxonarm/BeagleBoard-X15#BeagleBoard-X15-SetupmicroSDcard ). I just called
dd if=./u-boot/MLO of=${DISK} count=1 seek=1 bs=128k, and dd if=./u-boot/u-boot.img of=${DISK} count=2 seek=1 bs=384k. Is this a problem? If so, how come the same SD card boots on the 572x EVM?
Thanks!!
Jeff Andich
Jun 14, 2017, 6:29:27 PM6/14/17
to BeagleBoard, jeff....@gmail.com
Update on BeagleBoard Debian on the 571x IDK:
I just tried imaging a smaller SD Card than what I was attempting before. This time I used a 4 GB SD card, whereas previously used a 32 GB card.
***Am able to boot into Debian (BeagleBoard.org Debian Image 2017-06-04) and am able to login! ***
Getting a few of these error messages after the FS is mounted (for different sectors):
[ 29.628082] mmcblk0: error -110 transferring data, sector 4154243 (et. al). nr 165, cmd response 0x900card status 0x0
Previously, when running with an image on a 32 GB SD card, I kept getting the following when ?? booting the kernel??
[ 5.802193] omap_hsmmc 4809c000.mmc: card busy
[ 5.849414] mmc0: error -110 whilst initialising SD card
* I've seen other posts on TI E2E related to card busy and error -110. One TI employee suggested trying another SD Card.
* I'm not sure why the 4 GB SD Card would make things better?? Not sure if it's a timing issue, or because I'm improperly formatting the card (??leaving a bunch of junk after the ext4 partition??).
* I didn't experience this problem on the 572x EVM - just on the 571x IDK..
* Found this patch ( https://py3.patchwork.dja.id.au/series/1807/mbox), ?? for omap_hsmmc "Add-ADMA-support and ..." but not sure if it has anything to do with this issue...
Again, please let me know if you want me to fetch anything else from this test configuration and thanks again for your help on Sunday Robert!!
rgds, jeff
Reply all
Reply to author
Forward
0 new messages