u - boot > printenvīootcmd = boardinit > setenv bootcmd nandboot Showing the environment variables and the faulty bootcmd. It will fail as it can't find the recovery image. The AP hangs at the u-boot and doesn't proceed. It might have accidentally unplugged while was booting up. Image signing verification success, continue to run. Validating first E-fuse MAC cpsw, usbether Hit any key to stop autoboot: 0 switch to partitions 0, OK mmc0 is. UBIFS: mounted UBI device 0, volume 0, name "part1" U-Boot SPL 2014.10-rc1 (19:20:25) reading u-boot.img reading u-boot.img U-Boot 2014.10-rc1 (19:20:25) I2C: ready DRAM: 512 MiB MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1 Using default environment Net: not set.
PCI-e 2 (IF 1 - bus 1) Root Complex Interface, Detected Link X1, GEN 2.0 This causes the pytest framework to fail as it looks like a reset.
U BOOT CONSOLE SERIAL
With driver model this function does not work correctly and when CONFIGDISPLAYBOARDINFOLATE is enabled we end up announcing U-Boot twice on the serial port. PCI-e 1 (IF 0 - bus 0) Root Complex Interface, Detected Link X1, GEN 2.0 U-Boot PATCH 0/3 console: Tidy up consoledevisserial() Simon Glass Thu, 08:32:47 -0700. SF: Detected N25Q32A with page size 64 KiB, total 4 MiB PCIe, Idx 2: Link upgraded to Gen2 based on client cpabilitiesĭDR4 Training Sequence - Ver TIP-0.23.(Sublib 0.8)0ĭDR4 Training Sequence - Switching XBAR Window to FastPath WindowĭDR4 Training Sequence - Ended SuccessfullyīootROM: Image checksum verification PASSEDīootROM: Boot image signature verification PASSED PCIe, Idx 1: Link upgraded to Gen2 based on client cpabilities
:** Link is Gen1, check the EP capability Connected Console into the AP and rebootedīootROM: RSA Public key verification PASSEDīootROM: CSK block signature verification PASSEDīootROM: Boot header signature verification PASSEDīoardId = 0x23board SerDes lanes topology details: