Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FS#1355 - U-Boot fails to start kernel #6400

Closed
openwrt-bot opened this issue Feb 13, 2018 · 3 comments
Closed

FS#1355 - U-Boot fails to start kernel #6400

openwrt-bot opened this issue Feb 13, 2018 · 3 comments
Labels

Comments

@openwrt-bot
Copy link

@openwrt-bot openwrt-bot commented Feb 13, 2018

matteosilex:

  • Device problem occurs on
    Olimex A13-SOM-256
  • Software versions of OpenWrt/LEDE release, packages, etc.
    Occurs 100% on builds from any of the lede-17.01.x tags
  • Steps to reproduce
    Occurs 100% of the time either by flashing an SD card from the official release builds or by doing a clean build with the A13-SOM profile. Occurs with root as ext4 and squashfs.

U-Boot seems to run correctly, but then the device stops UART1 output at kernel start. The UART1 console configuration in the kernel seems correct, so I doubt it's just UART1 that's not working.
Consumption seems to indicate no activity (constant 170mA on a 5V supply)

log from UART1 console for the official build of release 17.01.4:

=======================================================================================================
U-Boot SPL 2016.03 (Oct 16 2017 - 11:22:18)
DRAM: 256 MiB
CPU: 1008000000Hz, AXI/AHB/APB: 3/2/2
Trying to boot from MMC1

U-Boot 2016.03 (Oct 16 2017 - 11:22:18 +0000) Allwinner Technology

CPU: Allwinner A13 (SUN5I)
Model: Olimex A13-Olinuxino
I2C: ready
DRAM: 256 MiB
MMC: SUNXI SD/MMC: 0
*** Warning - bad CRC, using default environment

In: serial
Out: serial
Err: serial
Net: No ethernet found.
starting USB...
USB0: USB EHCI 1.00
USB1: USB OHCI 1.0
scanning bus 0 for devices... 2 USB Device(s) found
Hit any key to stop autoboot: 0
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot.scr
reading /boot.scr
377 bytes read in 16 ms (22.5 KiB/s)

Executing script at 43100000

reading uImage
2160632 bytes read in 165 ms (12.5 MiB/s)
reading dtb
18096 bytes read in 29 ms (609.4 KiB/s)

Booting kernel from Legacy Image at 42000000 ...

Image Name: ARM LEDE Linux-4.4.92
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2160568 Bytes = 2.1 MiB
Load Address: 40008000
Entry Point: 40008000
Verifying Checksum ... OK

Flattened Device Tree blob at 43000000

Booting using the fdt blob at 0x43000000
Loading Kernel Image ... OK
Using Device Tree in place at 43000000, end 430076af

Starting kernel ...
[HANGS HERE]

@openwrt-bot
Copy link
Author

@openwrt-bot openwrt-bot commented Feb 13, 2018

matteosilex:

Found the cause of the issue. On the lede-17.01 branch, the kernel config for A13-SOM has LPAE enabled, while the A13 does not support LPAE.

@openwrt-bot
Copy link
Author

@openwrt-bot openwrt-bot commented Feb 21, 2018

mkresin:

Please send a patch following https://openwrt.org/submitting-patches to get it fixed. You might want to have a look at master as well, to ensure that the next release doesn't have the same issue.

@openwrt-bot
Copy link
Author

@openwrt-bot openwrt-bot commented Feb 23, 2018

matteosilex:

Submitted PR at #756

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant