avafinger / nanopi-a64-firmware

Nano Pi A64 firmware ( u-boot, kernel 3.10.104 / kernel 3.10.105 )
10 stars 5 forks source link

boot failure build v2 #8

Closed eventus17 closed 6 years ago

eventus17 commented 6 years ago

Hi Avafinger! I appreciate Your work on this alternative firmware for our nanopi-a64! Unfortunately I have problem to boot the system. I burned v2 build according read-me. Whole microSD card was zeroed before burning (dd if=/dev/zero/) an prepared on host PC with Ubuntu 16.04. Script ./burn_sdcard_v2.sh always ends without errors. The same microSD card works like a charm with firmware from FriendlyARM images. Below UART debug log on start up:

HELLO! BOOT0 is starting!
boot0 commit : 045061a8bb2580cb3fa02e301f52a015040c158f

boot0 version : 4.0.0
set pll start
set pll end
rtc[0] value = 0x00000000
rtc[1] value = 0x00000000
rtc[2] value = 0x00000000
rtc[3] value = 0x00000000
rtc[4] value = 0x00000000
rtc[5] value = 0x00000000
DRAM driver version: V1.1
rsb_send_initseq: rsb clk 400Khz -> 3Mhz
PMU: AXP81X
ddr voltage = 1500 mv
DRAM Type = 3 (2:DDR2,3:DDR3,6:LPDDR2,7:LPDDR3)
DRAM clk = 672 MHz
DRAM zq value: 003b3bbb
DRAM single rank full DQ OK
DRAM size = 1024 MB
DRAM init ok
dram size =1024
card boot number = 0, boot0 copy = 0
card no is 0
sdcard 0 line count 4
[mmc]: mmc driver ver 2015-05-08 20:06
[mmc]: sdc0 spd mode error, 2
[mmc]: Wrong media type 0x00000000
[mmc]: ***Try SD card 0***
[mmc]: HSSDR52/SDR25 4 bit
[mmc]: 50000000 Hz
[mmc]: 14991 MB
[mmc]: ***SD/MMC 0 init OK!!!***
sdcard 0 init ok
The size of uboot is 000e4000.
sum=e4887dd4
src_sum=e4887dd4
Succeed in loading uboot from sdmmc flash.
boot0: start load other image
boot0: Loading BL3-1
Loading file 0 at address 0x40000000,size 0x0000a200 success
boot0: Loading scp
Loading file 2 at address 0x00040000,size 0x00019a00 success
set arisc reset to de-assert state
Ready to disable icache.
�  Configuring SPC Controller
NOTICE:  BL3-1: v1.0(debug):3cdc5c3
NOTICE:  BL3-1: Built : 15:26:02, Oct 24 2017
INFO:    BL3-1: Initializing runtime services
INFO:    BL3-1: Preparing for EL3 exit to normal world
INFO:    BL3-1: Next image address = 0x4a000000
INFO:    BL3-1: Next image spsr = 0x1d3

U-Boot 2014.07-A64-00004-g6f37e5c-dirty (Oct 24 2017 - 15:25:20) Allwinner Technology

uboot commit : 6f37e5cf6a65b0b10455d12dbd631effabe765ec

rsb: secure monitor exist
[      0.362]pmbus:   ready
[      0.364][ARISC] :arisc initialize
[      0.697][ARISC] :arisc_dvfs_cfg_vf_table: support only one vf_table
[SCP] :sunxi-arisc driver begin startup 2
[SCP] :arisc_para size:1a8
[SCP] :arisc version: [v0.1.76]
[SCP] :sunxi-arisc driver v1.10 is starting
[      0.826][ARISC] :sunxi-arisc driver startup succeeded
[      0.859]PMU: AXP81X
[      0.861]PMU: AXP81X found
bat_vol=1, ratio=100
[      0.868]PMU: dcdc2 1100
[      0.871]PMU: cpux 1008 Mhz,AXI=336 Mhz
PLL6=600 Mhz,AHB1=200 Mhz, APB1=100Mhz AHB2=300Mhz MBus=400Mhz
device_type = 3253, onoff=1
dcdc1_vol = 3100, onoff=1
dcdc2_vol = 1100, onoff=1
dcdc6_vol = 1100, onoff=1
aldo1_vol = 2800, onoff=0
aldo2_vol = 1800, onoff=1
aldo3_vol = 3000, onoff=1
dldo1_vol = 3300, onoff=0
dldo2_vol = 3300, onoff=0
dldo3_vol = 2800, onoff=0
dldo4_vol = 3300, onoff=1
eldo1_vol = 1800, onoff=1
eldo2_vol = 1800, onoff=0
eldo3_vol = 1800, onoff=0
fldo2_vol = 1100, onoff=1
gpio0_vol = 3100, onoff=0
vbus not exist
normal dc exist, limit to dc
run key detect
no key found
no uart input
DRAM:  1008 MiB
fdt addr: 0x76ec23a0
Relocation Offset is: 35f14000
In:    serial
Out:   serial
Err:   serial
gic: sec monitor mode
[      1.678]start
drv_disp_init
init_clocks: finish init_clocks.
enable power vcc-hdmi-33, ret=0
drv_disp_init finish
boot_disp.output_disp=0
boot_disp.output_type=3
boot_disp.output_mode=5
fetch script data boot_disp.auto_hpd fail
disp0 device type(4) enable
attched ok, mgr0<-->device1, type=4, mode=5
[      2.086]end
workmode = 0,storage type = 1
[      2.090]MMC:        0
[mmc]: @lex mmc driver ver 2015-06-03 13:50:00
sdc_no: 0
[mmc]: get card2_boot_para:sdc_ex_dly_used 0
[mmc]: delete mmc-hs400-1_8v from dtb
[mmc]: delete mmc-hs200-1_8v from dtb
[mmc]: delete mmc-ddr-1_8v from dtb
[mmc]: delete max-frequency from dtb
SUNXI@lex SD/MMC: 0
[mmc]: start mmc_calibrate_delay_unit, don't access device...
[mmc]: delay chain cal done, sample: 192(ps)
[mmc]: BPI: 0 CARD_TYPE_SD
[mmc]: media type 0x8000001
[mmc]: ************Try SD card 0************
[mmc]: host caps: 0x27
[mmc]: MID 1b PSN 75aee44f
[mmc]: PNM 00000 -- 0x30-30-30-30-30
[mmc]: PRV 1.0
[mmc]: MDT m-3 y-2013
[mmc]: speed mode     : HSSDR52/SDR25
[mmc]: clock          : 50000000 Hz
[mmc]: bus_width      : 4 bit
[mmc]: user capacity  : 14991 MB
[mmc]: ************SD/MMC 0 init OK!!!************
[mmc]: BPI: sunxi_switch_to_best_bus - host->mmc_no: 0
[mmc]: erase_grp_size      : 0x1WrBlk*0x200=0x200 Byte
[mmc]: secure_feature      : 0x0
[mmc]: secure_removal_type : 0x0
[      2.426]sunxi flash init ok

** Unable to use mmc 0:1 for loading the env **
Using default environment

--------fastboot partitions--------
mbr not exist
base bootcmd=run mmcbootcmd
* storage_type=STORAGE_SD
bootcmd set setargs_mmc
key 0
recovery key high 12, low 10
fastboot key high 6, low 4
no misc partition is found
to be run cmd=run mmcbootcmd
update dtb dram start
update dtb dram  end
serial is: 1410503442183c26030e
Detect: A64 model by DRAM size:
A64 model: 2GB
PowerBus = 2(0: not exist 1:vBus 2:acBus 3:vBus&acBus)
Battery Voltage=0, Ratio=0
power trigger
sunxi_bmp_logo_display
Failed to mount ext2 filesystem...
** Unrecognized filesystem type **
sunxi bmp info error : unable to open logo file bootlogo.bmp
[      2.726]inter uboot shell
Hit any key to stop autoboot:  0
Failed to mount ext2 filesystem...
** Unrecognized filesystem type **
Failed to mount ext2 filesystem...
** Unrecognized filesystem type **
Booting with defaults ...
fdt ...
Failed to mount ext2 filesystem...
** Unrecognized filesystem type **
libfdt fdt_check_header(): FDT_ERR_BADMAGIC
Failed to mount ext2 filesystem...
** Unrecognized filesystem type **

I assume that this has nothing with the build itself, rather some issue with file system on flash card during preparation process executed over burn-script. Any idea how to deal with this? Thank You in advance for any help.

avafinger commented 6 years ago

Yes, you have a bad SD CARD. Please get Sandisk Ultra 16GB that is less prone to error. Make sure you have a good USB sd card reader/writer, check in your PC host for errors or resets during writing: dmesg

Edited: Sorry for the wrong link.

avafinger commented 6 years ago

@eventus,

Please, check dmesg|tail on your HOST PC and check if your SD CARD is unmounted at the end, it should be unmounted.

eventus17 commented 6 years ago

[SOLVED] There was no errors/resets during flashing in dmesg also the card was properly unmounted on the end. Reason was simple - bad SDCARD writer. I used internal SDCARD writer in old laptop and boot up Ubuntu from external USB stick to do all the stuff with flashing. Everything is working now! Sorry for my ignorance. Until this moment I never had problems with my external USB SDCARD writer.

avafinger commented 6 years ago

yeah, throw away your USB SDCARD writer! I trashed two of mine until i found a good one. ;)