Jump to content

Lime2 doesn't start after Armbian 5.35 update


Noero

Recommended Posts

Hi everybody,

 

At first I would like to thank you all cause of all your comments in previous posts that helped to make my Lime2 working great.

But since the 5.35 upgrade it doesn't want to start anymore.

 

I was on a A20-OLinuXino-LIME2 without eMMC and the Armbian_5.31_Lime2_Ubuntu_xenial_default_3.4.113_desktop image which I upgraded to the 5.35.

On the 5.31 I modified before the update the /boot/bin/lime2.bin file into a lime2lcd10.bin file in order to make the lime2 work with the LCD-OLinuXino-10TS of Olimex. After the update, I needed to make the link again with the /boot/script.bin file. But even with a new Armbian image freshly downloaded, it doesn't start also.

 

When I plug the HDMI I see :

U-Boot 2017.09-armbian (nov 22 2017 -15:21:35 +0100) Allwinner Technology

CPU: Allwinner A20 (SUN7I)
Model: Olimex A20-OlinuXino-Lime2-eMMC
I2C: ready
DRAM: 1GiB
MMC: SUNXI SD/MMC: 0, SUNXI SD/MMC: 1
*** Warning - bad CRC, using default environnment

HDMI connected: Setting up a 1920x1000 hdmi console(overscan 0x0)
Error: no valid bmp image at 66000000
In: serial
Out: vga
Err: vga
SCSI: SATA link 0 timeout.
AHCI 0001.0100 32 slots 1 ports 3 Gbps 0x1 impl SATA mode
flags: ncq stag pm led clo only pmp pio slun part ccc apst
Net: eth0: ethernet@01c50000
38518 bytes read in 146 ms (256.0 KiB/s)
starting USB...
USB0:	USB EHCI 1.00
USB1:	USB OHCI 1.0
USB2:	USB EHCI 1.00
USB3:	USB OHCI 1.0
scanning bus 0 for devices... 1 USB Device(s) found
scanning bus 2 for devices... 1 USB Device(s) found
		scanning bus 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.src
3565 bytes read in 194 ms (176 KiB/s)
## Executing script at 43100000
U-boot loaded from SD
Boot script loaded from mmc
192 bytes read in 156 ms (1000 Bytes/s)
5076840 bytes read in 559 ms (8.7 MiB/s)
5594800 bytes read in 549 ms (9.7 MiB/s)
Found legacy kernel configuration
53532 bytes read in 576 ms (89.8 KiB/s)
## Loading init Ramdisk from Legacy Image at 43300000 ...
  Image Name:	uInitrd
  Image Type:	ARM Minux RAMDisk Image (gzip compressed)
  Data Size:	5076776 Bytes = 4.8 MiB
  Load Addresses: 	00000000
  Entry Point:	00000000
  Verifying Checksum ... OK
EHCI failed to shut down host controller.
  Loading Ramdisk to 49b28000, end 49fff728 ... OK
  
Starting kernel ...
  

And then nothing...

For the Warning at the beginning I stopped the Autoboot and wrote the code :

 

saveenv
reset

No more warning but still doesn't start.

Any idea how to fix it?

 

Thanks

Edited by Noero
Some misspellings in the code
Link to comment
Share on other sites

Found a solution after following Roman Antoshchenkov's post : 

It seems the new version of u-boot toggels also LDO3 that causes crash/shutdown of the AXP209.

Thanks Roman for your post.

 

Best, 

Noemie & Romain

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines