Post Go back to editing

AD-JUPITER-EBZ fails to properly boot when turning on

Thread Summary

The user encountered issues booting the AD-JUPITER-EBZ development module after a power-off, receiving a 'No Valid Environment Area found' error via UART. The solution involved ensuring the correct binaries from the Jupiter folder are placed in the root of the SD card after flashing the Kuiper image. The user confirmed this resolved the issue.
AI Generated Content
Category: Software
Product Number: ADRV9002

I am getting started using the AD-JUPITER-EBZ development module and I was having some issues with getting the Jupiter module turned on. There is a related question from   titled "boot partition for ad jupiter ebz" that did not provide a sufficient answer for me to address the issue I am experiencing. I was able to initially startup the module using the provided microSD card image and was able to get the module booted in standalone mode with a DisplayPort monitor and keyboard and mouse.

After initially using the system for some time I powered the system off using the on-module power button and then a couple hours later went to turn on the system and was getting no output on my monitor. Using the UART debug port I identified the issue as possibly being an issue with the SD card image as I was receiving the following message on the UART Serial stream:

Loading Environment from FAT... *** Error - No Valid Environment Area found
*** Warning - bad env area, using default environment

Full UART message shown below

Release 2023.1   Nov  9 2023  -  13:40:16
NOTICE:  BL31: Non secure code at 0x8000000
NOTICE:  BL31: v2.8(release):4683880e5
NOTICE:  BL31: Built : 06:39:41, Jun 27 2023

U-Boot 2022.01-40843-ga16a6a9cb3 (Jun 26 2023 - 15:37:16 +0300)

CPU:   ZynqMP
Silicon: v3
Model: Analog Devices, Inc. Jupiter SDR
Board: Xilinx ZynqMP
DRAM:  2 GiB
PMUFW:  v1.1
PMUFW:  No permission to change config object
EL Level:       EL2
Chip ID:        zu3eg
NAND:  0 MiB
MMC:   mmc@ff170000: 0
Loading Environment from FAT... *** Error - No Valid Environment Area found
*** Warning - bad env area, using default environment

In:    serial
Out:   serial
Err:   serial
Bootmode: LVL_SHFT_SD_MODE1
Reset reason:   EXTERNAL
Net:   FEC: can't find phy-handle

ZYNQ GEM: ff0e0000, mdio bus ff0e0000, phyaddr 15, interface rgmii-id

Error: ethernet@ff0e0000 address not set.
No ethernet found.

scanning bus for devices...
SATA link 0 timeout.
SATA link 1 timeout.
AHCI 0001.0301 32 slots 2 ports 6 Gbps 0x3 impl SATA mode
flags: 64bit ncq pm clo only pmp fbss pio slum part ccc apst
starting USB...
No working controllers found
Hit any key to stop autoboot:  0
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
libfdt fdt_check_header(): FDT_ERR_BADMAGIC
Scanning disk mmc@ff170000.blk...
Found 4 disks
No EFI system partition
Unable to find TPMv2 device
DFU alt info setting: done
FEC: can't find phy-handle

ZYNQ GEM: ff0e0000, mdio bus ff0e0000, phyaddr 15, interface rgmii-id

Error: ethernet@ff0e0000 address not set.
FEC: can't find phy-handle

ZYNQ GEM: ff0e0000, mdio bus ff0e0000, phyaddr 15, interface rgmii-id

Error: ethernet@ff0e0000 address not set.
BootOrder not defined
EFI boot manager: Cannot load any image
JTAG: Trying to boot script at 20000000
## Executing script at 20000000
Wrong image format for "source" command
JTAG: SCRIPT FAILED: continuing...
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
libfdt fdt_check_header(): FDT_ERR_BADMAGIC
BootOrder not defined
EFI boot manager: Cannot load any image
MMC Device 1 not found
no mmc device at slot 1
jedec_spi_nor spi_flash@0:0: unrecognized JEDEC id bytes: ff, ff, ff
Failed to initialize SPI flash at 0:0 (error -2)
QSPI: SCRIPT FAILED: continuing...

no devices available
NAND: SCRIPT FAILED: continuing...
starting USB...
No working controllers found
USB is stopped. Please issue 'usb start' first.
starting USB...
No working controllers found
USB is stopped. Please issue 'usb start' first.

Device 0: unknown device
starting USB...
No working controllers found
FEC: can't find phy-handle

ZYNQ GEM: ff0e0000, mdio bus ff0e0000, phyaddr 15, interface rgmii-id

Error: ethernet@ff0e0000 address not set.
FEC: can't find phy-handle

ZYNQ GEM: ff0e0000, mdio bus ff0e0000, phyaddr 15, interface rgmii-id

Error: ethernet@ff0e0000 address not set.
FEC: can't find phy-handle

ZYNQ GEM: ff0e0000, mdio bus ff0e0000, phyaddr 15, interface rgmii-id

Error: ethernet@ff0e0000 address not set.
FEC: can't find phy-handle

ZYNQ GEM: ff0e0000, mdio bus ff0e0000, phyaddr 15, interface rgmii-id

Error: ethernet@ff0e0000 address not set.
FEC: can't find phy-handle

ZYNQ GEM: ff0e0000, mdio bus ff0e0000, phyaddr 15, interface rgmii-id

Error: ethernet@ff0e0000 address not set.
FEC: can't find phy-handle

ZYNQ GEM: ff0e0000, mdio bus ff0e0000, phyaddr 15, interface rgmii-id

Error: ethernet@ff0e0000 address not set.
FEC: can't find phy-handle

ZYNQ GEM: ff0e0000, mdio bus ff0e0000, phyaddr 15, interface rgmii-id

Error: ethernet@ff0e0000 address not set.
FEC: can't find phy-handle

ZYNQ GEM: ff0e0000, mdio bus ff0e0000, phyaddr 15, interface rgmii-id

Error: ethernet@ff0e0000 address not set.
No ethernet found.
Insufficient RAM for page table: 0x15000 > 0x14000. Please increase the size in get_page_table_size()
### ERROR ### Please RESET the board ###


I then went to reflash the SD card using a default Kuiper image which I was able to successfully do. The next day I noticed some strange behavior from the jupiter module. Upon pressing the module's power button, the LED remained in the red state, and I was unable to observe any UART messages. I suspect this may not be an issue with the SD card and possibly a hardware issue altogether as the SD card seemed to be successfully flashing the kuiper image.

Please advise on any way to resolve this issue and successfully boot up the module. Thanks

Before You Switch


Switching languages will make ADI Explorer unavailable. Resume your session by switching back to English and reopening ADI Explorer.