Good to hear that it is working for you... It's detecting PRUs for me now
when booting off the SD card - I just need to get them to start my code and
setup /de/rpmsg_31 properly... another hurdle but I'm sure I will overcome.
On Sunday, 26 May 2019 23:33:37 UTC+1, jonre...@gmail.com wrote:
>
>
Okay I managed to get everything working too. I had to do the following
steps:
1. reset eMMC
sudo /opt/scripts/tools/developers/update_bootloader.sh
2. flash new image provided above
3. After that the model from /opt/scripts/tools/version.sh was wrong for
me. I'm using a BBBW but model field
Robert, is it ok to use this image in production or should I use the
current stretch IOT image and flash the eMMC to overwrite this old
bootloader?
On Saturday, 25 May 2019 20:55:58 UTC+1, RobertCNelson wrote:
>
> > This is what I think is relevant from my uBoot console:
> >
> > U-Boot SPL
Damn... accidentally overwritten uBoot on the eMMC... I thought the flasher
wouldn't touch that. Apologies Robert.
However, it was obviously a uBoot on eMMC problem as with a freshly flashed
eMMC the overlay loads properly. I'll try booting from SD card now and see
if that works too,. In our
I will get that sorted and put it on my dropbox. I've got to flash eMMC
with the sd card contents then reboot with another sd card in the USB-A
port - I'm working from home and don't have any cables other than a 232r on
the debug header and a 5v power brick.
Give me half an hour...
On
> This is what I think is relevant from my uBoot console:
>
> U-Boot SPL 2017.03-2-gd12b1519b4 (Mar 14 2017 - 10:28:26)
> Trying to boot from MMC2
> U-Boot 2017.03-2-gd12b1519b4 (Mar 14 2017 - 10:28:26 -0500), Build:
> jenkins-
> github_Bootloader-Builder-532
There you go!! Would you
Flashing your test image to a fresh SD card leaves me with the same
behaviour as before Robert. My uEnv.txt follows:
debian@beaglebone:~$ cat /boot/uEnv.txt
#Docs: http://elinux.org/Beagleboard:U-boot_partitioning_layout_2.0
