RP 125-14 v1.1 problems booting up a new image

[alyapin9]

Hi All!
I'm trying to resurrect a bunch of RPs we have in our lab that appear to be v1.1 125-14 boards with the 7010 chip to use them as scopes and perhaps general fpga fun later. They previously ran a v0.94 copy of the ecosystem which still boots but no apps are available as it must be too old and thing have changed since. I am therefore trying to boot them with any of the latest images, and none of them seem to be able to access EEPROM. I'm attaching the bit of the log with the error message for STEMlab_125-xx_OS_1.04-18_stable. Since this does not happen with 0.94 but does with 1.04 on 2 boards, presumably not a hardware problem. Anything I can try?
Thanks!

Code: Select all

[  OK  ] Started Network Service.
[  OK  ] Reached target Network.
         Starting Network Name Resolution...
[  OK  ] Started Jupyter notebook server.
[  OK  ] Started Service for startup script Red Pitaya.
         Starting Customized Nginx web server for Red Pitaya applications...
         Starting OpenBSD Secure Shell server...
[  OK  ] Started Network Name Resolution.
         Starting Avahi mDNS/DNS-SD Stack...
[  OK  ] Reached target Network is Online.
         Starting /etc/rc.local Compatibility...
         Starting LSB: Advanced IEEE 802.11 management daemon...
[  OK  ] Started /etc/rc.local Compatibility.
[  OK  ] Started LSB: Advanced IEEE 802.11 management daemon.
[  OK  ] Started Avahi mDNS/DNS-SD Stack.
[  OK  ] Started Getty on tty1.
[  OK  ] Reached target Login Prompts.
[  OK  ] Started OpenBSD Secure Shell server.
[  OK  ] Started Customized Nginx web server for Red Pitaya applications.
[  OK  ] Reached target Multi-User System.
[  OK  ] Reached target Graphical Interface.
         Starting Update UTMP about System Runlevel Changes...
[  OK  ] Started Update UTMP about System Runlevel Changes.

Ubuntu 16.04.7 LTS rp-f03c18 ttyPS0

rp-f03c18 login: root (automatic login)

cdns-i2c e0004000.i2c: timeout waiting on completion


U-Boot 2016.07 (Apr 28 2022 - 04:31:17 +0000), Build: jenkins-redpitaya-master-125-14-18

Model: Red Pitaya Board
Board: Xilinx Zynq
I2C:   ready
DRAM:  ECC disabled 480 MiB
I2C:EEPROM selection failed
MMC:   sdhci@e0100000: 0
In:    serial@e0000000
Out:   serial@e0000000
Err:   serial@e0000000
Model: Red Pitaya Board
Board: Xilinx Zynq
Net:   ZYNQ GEM: e000b000, phyaddr 1, interface rgmii-id
eth0: ethernet@e000b000
Hit any key to stop autoboot:  0
Zynq> 

[redpitaya]

Hello alyapin9,

Thank you for posting this on the forum.

If possible, please try using a different SD card and the recommended application Balena Ethcer to flash the OS. We include 32 GB SD cards with the new Red Pitayas, so it is possible that the SD cards have insufficient size.

Do the Red Pitaya's boot? Please compare the boot-up status LED sequence to this one:
https://www.youtube.com/watch?v=9xZCAkXAkw8

I will let you know if there is anything else you can try.

[alyapin9]

I am in fact using a 32GB SD etched with Balena. Unfortunately the only large capacity SD I have around. The boards boot and then timeout and re-boot in an infinite sequence. This does not happen with the v0.94 of the ecosystem on a 4GB SD I had originally with the board.

[redpitaya]

here is how to fix it: https://github.com/RedPitaya/RedPitaya/issues/250
Please check the instructions by the user b-swat

[alyapin9]

Thank you for the suggestion!
It does not seem to have worked though. I changed the hv_rev, but the boot sequence still goes into a loop after seemingly loading the OS. Please, let me know if there's more to try.

Sometimes I get this error message before the bootloader kicks in again:

Code: Select all

cdns-i2c e0004000.i2c: timeout waiting on completion

The hardware settings now look like this:

Code: Select all

bootcmd=run $modeboot
bootdelay=3
baudrate=115200
ipaddr=10.10.70.102
serverip=10.10.70.101
prod_date=12/22/13
kernel_image=uImage
ramdisk_image=uramdisk.image.gz
devicetree_image=devicetree.dtb
bitstream_image=system.bit.bin
loadbit_addr=0x100000
kernel_size=0x500000
devicetree_size=0x20000
ramdisk_size=0x5E0000
fdt_high=0x20000000
initrd_high=0x20000000
sdboot=echo Copying Linux from SD to RAM... && mmcinfo && fatload mmc 0 0x3000000 ${kernel_image} && fatload mmc 0 0x2A00000 ${devicetree_image} && fatload mmc 0 0x2000000 ${ramdisk_image} && bootm 0x3000000 0x2000000 0x2A00000
ethaddr=00:26:32:F0:3C:18
nav_code=4662
serial=1624ARVPUV
hw_rev=STEM_125-14_v1.1

And if I interrupt the boot sequence (using the latest beta of the ecosystem, but it's similar with the latest stable):

Code: Select all

U-Boot 2022.01 (Mar 06 2023 - 16:24:17 +0000), Build: jenkins-redpitaya-master-unify-15

CPU:   Zynq 7z010
Silicon: v3.1
DRAM:  ECC disabled 512 MiB
Flash: 0 Bytes
NAND:  0 MiB
MMC:   mmc@e0100000: 0
Loading Environment from nowhere... OK
In:    serial@e0000000
Out:   serial@e0000000
Err:   serial@e0000000
Net:   
ZYNQ GEM: e000b000, mdio bus e000b000, phyaddr 1, interface rgmii-id
eth0: ethernet@e000b000
Hit any key to stop autoboot:  0 

[alyapin9]

Hi again, just noticed a potential problem with the beta build.

When running 1.04_18_stable I get to login prompts and then the board reboots:

Code: Select all

[  OK  ] Created slice system-getty.slice.
[  OK  ] Started Set hostname to redpitaya-[MAC].
[  OK  ] Started Set console scheme.
[  OK  ] Started Service for startup wifi.
[  OK  ] Started Hostname Service.
         Starting Network Service...
[  OK  ] Started Network Service.
[  OK  ] Reached target Network.
         Starting Network Name Resolution...
[  OK  ] Started Service for startup script Red Pitaya.
         Starting Customized Nginx web server for Red Pitaya applications...
[  OK  ] Started Jupyter notebook server.
         Starting OpenBSD Secure Shell server...
[  OK  ] Started Network Name Resolution.
[  OK  ] Reached target Network is Online.
         Starting LSB: Advanced IEEE 802.11 management daemon...
         Starting /etc/rc.local Compatibility...
         Starting Avahi mDNS/DNS-SD Stack...
[  OK  ] Started LSB: Advanced IEEE 802.11 management daemon.
[  OK  ] Started /etc/rc.local Compatibility.
[  OK  ] Started Getty on tty1.
[  OK  ] Reached target Login Prompts.
[  OK  ] Started Avahi mDNS/DNS-SD Stack.


U-Boot 2016.07 (Apr 28 2022 - 04:31:17 +0000), Build: jenkins-redpitaya-master-125-14-18

Model: Red Pitaya Board
Board: Xilinx Zynq
I2C:   ready
DRAM:  ECC disabled 480 MiB
I2C:EEPROM selection failed
MMC:   sdhci@e0100000: 0
In:    serial@e0000000
Out:   serial@e0000000
Err:   serial@e0000000
Model: Red Pitaya Board
Board: Xilinx Zynq
Net:   ZYNQ GEM: e000b000, phyaddr 1, interface rgmii-id
eth0: ethernet@e000b000
Hit any key to stop autoboot:  0 
Zynq> 

v2 beta build 131 gives a slightly different result that seems to have a problem with starting the ssh server before still going to a reboot:

Code: Select all

[  OK  ] Started Jupyter notebook server.
         Starting Network Time Service...
[  OK  ] Started Service for startup script Red Pitaya.
         Starting Customized Nginx …for Red Pitaya applications...
         Starting LSB: Shell In A Box Daemon...
         Starting OpenBSD Secure Shell server...
         Starting Permit User Sessions...
[  OK  ] Started Avahi mDNS/DNS-SD Stack.
[  OK  ] Finished Permit User Sessions.
[  OK  ] Started Serial Getty on ttyPS0.
         Starting Set console scheme...
[  OK  ] Started Network Time Service.
[  OK  ] Finished Set console scheme.
[FAILED] Failed to start OpenBSD Secure Shell server.
See 'systemctl status ssh.service' for details.
[  OK  ] Created slice Slice /system/getty.
[  OK  ] Started Getty on tty1.
[  OK  ] Reached target Login Prompts.
[  OK  ] Stopped OpenBSD Secure Shell server.
         Starting OpenBSD Secure Shell server...
[FAILED] Failed to start OpenBSD Secure Shell server.
See 'systemctl status ssh.service' for details.
[  OK  ] Started Customized Nginx w…r for Red Pitaya applications.
[  OK  ] Started LSB: Shell In A Box Daemon.
[  OK  ] Stopped OpenBSD Secure Shell server.
         Starting OpenBSD Secure Shell server...
[FAILED] Failed to start OpenBSD Secure Shell server.


U-Boot 2022.01 (Jul 10 2023 - 06:30:56 +0000), Build: jenkins-RED_PITAYA_UNIFY-Kernel-62

CPU:   Zynq 7z010
Silicon: v3.1
DRAM:  ECC disabled 512 MiB
Flash: 0 Bytes
NAND:  0 MiB
MMC:   mmc@e0100000: 0
Loading Environment from nowhere... OK
In:    serial@e0000000
Out:   serial@e0000000
Err:   serial@e0000000
Net:   
ZYNQ GEM: e000b000, mdio bus e000b000, phyaddr 1, interface rgmii-id
eth0: ethernet@e000b000
Hit any key to stop autoboot:  0 
Zynq> 

[redpitaya]

And have you tried the latest beta OS version 2.0 ? At this point, I am also wondering if the SD card was written properly or if maybe you have a standard board or an external clock input version.

[alyapin9]

As you can see above, I tried both the stable version recommended for my board and the beta v2. I tried 2 different SD cards. I have a standard board v1.1.

[redpitaya]

ok, thank you for the info, let's take this up with our support. Please write to support at redpitaya dot com and please mention this thread.

[alyapin9]

Thank you for the referral!