Last hours for Arrow's 20% off sale and X15's in stock at Digi-Key

[Jason Kridner]

BeagleBone Blue's at under $64 plus tax and free shipping. Unfortunately, limited to the US. Ends at 11:59PM US Central time.

Also, I see Digi-Key has BeagleBoard-X15's in stock.

[Jeff Andich]

Best news I've heard all week....

Just out of curiosity is the BB-X15 that we can order now from DigiKey still SR2 or was there another revision done on the board/silicon?  

I have an am572xEvm which reports to be ES2.0/(?SR2.0?) when SPL/u-boot boots.  Will the rev_a3 device tree for the the ti 572x still run on the latest BB-X15?

Reason I ask. A couple of weeks ago, following the instructions on retrieving and patching u-boot for the BB-X15 from eewiki, I retrieved a mysterious version of the TI patch set for u-boot which compiled, but wouldn't boot.  It had references to device trees with 'RevC.'  I posted up here, and then re-retrieved/applied the u-boot patch set and those references to RevC went away, and u-boot ran again on my ES2.0 am572xEvm..

Thanks and regards! jeff

[Robert Nelson]

On Fri, Aug 11, 2017 at 12:40 PM, Jeff Andich <jeff....@gmail.com> wrote:
>
> Best news I've heard all week....
>
> Just out of curiosity is the BB-X15 that we can order now from DigiKey still
> SR2 or was there another revision done on the board/silicon?

It's labeled as Rev C, it's essentially a Rev B with SR2.0 silicon...
(SR2.0 fixes the 1GB 2nd phy, on the Rev B (SR1.x) the 2nd phy was
limited to 100MB)

> I have an am572xEvm which reports to be ES2.0/(?SR2.0?) when SPL/u-boot
> boots. Will the rev_a3 device tree for the the ti 572x still run on the
> latest BB-X15?
>
> Reason I ask. A couple of weeks ago, following the instructions on
> retrieving and patching u-boot for the BB-X15 from eewiki, I retrieved a
> mysterious version of the TI patch set for u-boot which compiled, but
> wouldn't boot. It had references to device trees with 'RevC.' I posted up
> here, and then re-retrieved/applied the u-boot patch set and those
> references to RevC went away, and u-boot ran again on my ES2.0 am572xEvm..

Yeah i still need to fixup our support for the rev_a3 572x evm board.

Regards,

--
Robert Nelson
https://rcn-ee.com/

[Robert Nelson]

okay, hacked around the spl lookup on line 982:

https://github.com/RobertCNelson/Bootloader-Builder/commit/c6e15b3c8c49edc78921a74798eeded2ee790643

it "should" have been returning 0, but for some reason it just locks
up.. might be a stack/oom/etc issue, as it's in SPL at that point...

*******************************
U-Boot SPL 2017.01-00359-g590c7d7fe1-dirty (Aug 11 2017 - 15:40:27)
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-00359-g590c7d7fe1-dirty (Aug 11 2017 - 15:40:27 -0500)

CPU : DRA752-GP ES2.0
Model: TI AM5728 BeagleBoard-X15
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 ...
Checking for: /boot/uEnv.txt ...
446 bytes read in 20 ms (21.5 KiB/s)
Loaded environment from /boot/uEnv.txt
Checking if uname_r is set in /boot/uEnv.txt ...
debug: [uname_r=4.4.80-ti-r116] ...
loading /boot/vmlinuz-4.4.80-ti-r116 ...
8664192 bytes read in 395 ms (20.9 MiB/s)
loading /boot/dtbs/4.4.80-ti-r116/am57xx-evm-reva3.dtb ...
149379 bytes read in 51 ms (2.8 MiB/s)
loading /boot/initrd.img-4.4.80-ti-r116 ...
5487379 bytes read in 255 ms (20.5 MiB/s)
debug: [console=ttyO2,115200n8 root=/dev/mmcblk0p1 ro rootfstype=ext4
rootwait coherent_pool=1M net.ifnames=0 quiet] ...
debug: [bootz 0x82000000 0x88080000:53bb13 0x88000000] ...
## Flattened Device Tree blob at 88000000
Booting using the fdt blob at 0x88000000
Loading Ramdisk to 8fac4000, end 8ffffb13 ... OK
Loading Device Tree to 8fa9c000, end 8fac3782 ... OK

Starting kernel ...

*******************************

[Robert Nelson]

Jeff, give this image a quick test:

https://rcn-ee.net/rootfs/2017-08-11/microsd/bbx15-debian-9.1-console-armhf-2017-08-11-2gb.img.xz

[Jeff Andich]

Hi Robert,

So far, so good.  It boots and gives the "arm" prompt.  Will collect some cursory logs and post them back up here..

Thanks and regards!

Jeff

[Jeff Andich]

Here's the bootup log without the verbose mode flag enabled in uEnv.txt:

**********************************************************************************

U-Boot SPL 2017.01-00360-gc604741cb3 (Aug 11 2017 - 15:47:09)

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-00360-gc604741cb3 (Aug 11 2017 - 15:47:09 -0500), Build: jenkins-github_Bootloader-Builder-592

CPU  : DRA752-GP ES2.0

Model: TI AM5728 BeagleBoard-X15

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 ...

Checking for: /boot/uEnv.txt ...

446 bytes read in 49 ms (8.8 KiB/s)

Loaded environment from /boot/uEnv.txt

Checking if uname_r is set in /boot/uEnv.txt ...

debug: [uname_r=4.4.80-ti-r116] ...

loading /boot/vmlinuz-4.4.80-ti-r116 ...

5487379 bytes read in 283 ms (18.5 MiB/s)

debug: [console=ttyO2,115200n8 root=/dev/mmcblk0p1 ro rootfstype=ext4 rootwait coherent_pool=1M net.ifnames=0 quiet] ...

debug: [bootz 0x82000000 0x88080000:53bb13 0x88000000] ...

## Flattened Device Tree blob at 88000000

   Booting using the fdt blob at 0x88000000

   Loading Ramdisk to 8fac4000, end 8ffffb13 ... OK

   Loading Device Tree to 8fa9c000, end 8fac3782 ... OK

Starting kernel ...

[    0.063779] /cpus/cpu@0 missing clock-frequency property

[    0.063800] /cpus/cpu@1 missing clock-frequency property

[    2.194996] dra7-pcie 51000000.pcie_rc: link is not up

[    2.540811] omap_hsmmc 480b4000.mmc: no pinctrl state for sdr25 mode

[    2.547225] omap_hsmmc 480b4000.mmc: no pinctrl state for sdr12 mode

[    2.639312] omap_voltage_late_init: Voltage driver support not added

[    3.537309]  remoteproc0: failed to load am57xx-pru1_0-fw

[    3.542894]  remoteproc0: request_firmware failed: -2

[    3.547988] pru-rproc 4b234000.pru0: rproc_boot failed

[    3.555830]  remoteproc0: failed to load am57xx-pru1_1-fw

[    3.562347]  remoteproc0: request_firmware failed: -2

[    3.567442] pru-rproc 4b238000.pru1: rproc_boot failed

[    3.581573]  remoteproc0: failed to load am57xx-pru2_0-fw

[    3.588946]  remoteproc0: request_firmware failed: -2

[    3.594048] pru-rproc 4b2b4000.pru0: rproc_boot failed

[    3.603674]  remoteproc0: failed to load am57xx-pru2_1-fw

[    3.610193]  remoteproc0: request_firmware failed: -2

[    3.615285] pru-rproc 4b2b8000.pru1: rproc_boot failed

[    5.899545]  remoteproc0: failed to load dra7-ipu1-fw.xem4

[    5.923242]  remoteproc2: failed to load dra7-dsp1-fw.xe66

[    5.932697]  remoteproc3: failed to load dra7-dsp2-fw.xe66

[    6.517022] pixcir_ts 4-005c: pixcir_set_power_mode: can't read reg 0x33 : -121

[    6.517027] pixcir_ts 4-005c: Failed to set IDLE mode

Debian GNU/Linux 9 arm ttyS2

rcn-ee.net console Debian Image 2017-08-11

Support/FAQ: http://elinux.org/BeagleBoardDebian

default username:password is [debian:temppwd]

[Jeff Andich]

Attached a text file containing log of output of the dmesg command.

*** Note: The dmesg command was captured from an earlier bootup session than from the session with the abridged kernel log pasted above ***

Thanks!  jeff

[Jeff Andich]

Last-night I received my BB-X15 at home.  From the description on DigiKey's website, I wasn't sure what comes in the box.

As it turns out, just a populated PCBA in an electrostatic bag, no power supply headers/standoffs, FTDI, default SD Card with the BBB-X15 image.

****Could the vendors please put a note on what comes in the box?****

Now I've got to order all of the obligatory accessories just to fire it up (and maybe pay more shipping charges).... argh!

Thanks!

Jeff

[Gerald Coley]

It boots off the eMMC on the board. It does not require a SD card to boot.

 

Gerald

--
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...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/c5942984-80cb-4749-9db6-5430308ccf04%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Jeff Andich]

Oops, I'm sorry.

If I only would have read this:

https://github.com/beagleboard/beagleboard-x15/blob/master/BeagleBoard-X15_Quick-Start-Guide.pdf

page 3, 

I would have known to order the other accessories.  

IMO, it would still be great if the distributors could specify what comes in the box.

Anyhow, it's booting a very late image of the kernel from eMMC...

[Robert Nelson]

On Aug 18, 2017 6:40 PM, "Jeff Andich" <jeff....@gmail.com> wrote:

Oops, I'm sorry.

If I only would have read this:

https://github.com/beagleboard/beagleboard-x15/blob/master/BeagleBoard-X15_Quick-Start-Guide.pdf

page 3, 

I would have known to order the other accessories.  

IMO, it would still be great if the distributors could specify what comes in the box.

Anyhow, it's booting a very late image of the kernel from eMMC...

It's v4.9.x-ti, with remotepruc_pruss, dsp support (OpenCL working out of the box).

I submitted mainline support this week, it'll hit v4.14.0-rc0.

Regards,