start kernel problem

Started by hamze60, July 10, 2021, 09:33:38 pm

Previous topic - Next topic


We have designed a PCB, with A20. Our schematic is very similar, but not completely, to reference A20-OLinuXino-Lime2 board (our USB ports are different,...). We have a SD-card with Armbian OS on it which works on our A20-OLinuXino-Lime2. After first try, it did not pass start kernel. Please see below log. What can be the problem? I guess CPU-power manager I2C bus is first problem source candidate, but not sure.
U-Boot SPL 2020.10-armbian (Dec 11 2020 - 22:55:37 +0100)
DRAM: 1024 MiB
Failed to set core voltage! Can't set CPU frequency
Trying to boot from MMC1

U-Boot 2020.10-armbian (Dec 11 2020 - 22:55:37 +0100) Allwinner Technology

CPU:   Allwinner A20 (SUN7I)
Model: Olimex A20-OLinuXino-LIME2-eMMC
I2C:   ready
DRAM:  1 GiB
MMC:   mmc@1c0f000: 0, mmc@1c11000: 1
Loading Environment from FAT... Unable to use mmc 1:0... DDC: timeout reading EDID
DDC: timeout reading EDID
DDC: timeout reading EDID
In:    serial
Out:   serial
Err:   serial
Allwinner mUSB OTG (Peripheral)
Net:   Could not get PHY for ethernet@1c50000: addr 1
eth1: usb_ether
230454 bytes read in 21 ms (10.5 MiB/s)
Error: 24 bits/pixel bitmap incompatible with current video mode
starting USB...
Bus usb@1c14000: USB EHCI 1.00
Bus usb@1c14400: USB OHCI 1.0
Bus usb@1c1c000: USB EHCI 1.00
Bus usb@1c1c400: USB OHCI 1.0
scanning bus usb@1c14000 for devices... 1 USB Device(s) found
scanning bus usb@1c14400 for devices... ERROR:  USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did
not provide a handshake (OUT) (5)
ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did
not provide a handshake (OUT) (5)
unable to get device descriptor (error=-1)
1 USB Device(s) found
scanning bus usb@1c1c000 for devices... 1 USB Device(s) found
scanning bus usb@1c1c400 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
Autoboot in 1 seconds, press <Space> to stop
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot/boot.scr
3967 bytes read in 6 ms (645.5 KiB/s)
## Executing script at 43100000
U-boot loaded from SD
Boot script loaded from mmc
203 bytes read in 5 ms (39.1 KiB/s)
11434469 bytes read in 758 ms (14.4 MiB/s)
7808464 bytes read in 512 ms (14.5 MiB/s)
Found mainline kernel configuration
43687 bytes read in 13 ms (3.2 MiB/s)
5532 bytes read in 17 ms (317.4 KiB/s)
Applying kernel provided DT fixup script (sun7i-a20-fixup.scr)
## Executing script at 45000000
## Loading init Ramdisk from Legacy Image at 43300000 ...
   Image Name:   uInitrd
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    11434405 Bytes = 10.9 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 43000000
   Booting using the fdt blob at 0x43000000
EHCI failed to shut down host controller.
   Loading Ramdisk to 49518000, end 49fff9a5 ... OK
   Loading Device Tree to 494a4000, end 49517fff ... OK

Starting kernel ...


It seems like a problem with the USB hardware. You probably have a short cut between the data lines.

Double-check your USB circuitry.

After that ensure the power supply for the whole unit is good enough.
Technical support and documentation manager at Olimex


Our board has different USB configuration,then I expected to see some errors about USB. The first problem we need to solve is about power manager. It generates power-good, accept 3-sec shutdown push-button and then power-up again, generates all voltages,... It seems it is totally fine. Our power supply is also 5V-3A and it also should be fine (I tested another supply too to be sure too). But, when I investigated the bellow error on line 3 of boot:
"Failed to set core voltage! Can't set CPU frequency", I guessed about a problem in I2C line. I probed that, and compared it with Lime2 evaluation kit. I noticed that power manager does not respond to CPU in my board, while in Lime2 they keep talking.
I have 3 boards mounted, and all have same behavior on I2C line.
Have you ever seen such problem?
Thank you


I have the same issue. Any tips for solution?