search

daniel-thompson / poplar-usbstick

Build script to generate a bootable debian-on-a-stick image for poplar (now with built-in installer goodness)
4 stars 2 forks source link

for help. u-boot not autostart #3

Closed way1001 closed 6 years ago

way1001 commented 6 years ago

Dear danielt: i hava a poplar board.i wanted use linux on the board.followed below guide: https://github.com/96boards-poplar/Documentation/blob/master/debian/debian_build_instructions.md but read image error,the console log should give some details: Bootrom start Boot Media: eMMC Decrypt auxiliary code ...OK

lsadc voltage min: 000000FE, max: 000000FF, aver: 000000FE, index: 00000000

Entry boot auxiliary code

Auxiliary code - v1.00 DDR code - V1.1.2 20160205 Build: Mar 24 2016 - 17:09:44

Reg Version: v134 Reg Time: 2016/03/18 09:44:55
Reg Name: hi3798cv2dmb_hi3798cv200_ddr3_2gbyte_8bitx4_4layers.reg

Boot auxiliary code success
Bootrom success

LOADER: Built 2018/05/03 20:48:30+0800 Commit-id 1de2bbf
LOADER: Switched to aarch64 mode
LOADER: Entering ARM TRUSTED FIRMWARE
LOADER: CPU0 executes at 0x0200e000

INFO: BL1: 0x2016000 - 0x201c000 [size = 24576]
NOTICE: Booting Trusted Firmware
NOTICE: BL1: v1.4(debug):e5dbebf
NOTICE: BL1: Built : 20:47:10, May 3 2018
INFO: BL1: RAM 0x2016000 - 0x201c000
INFO: BL1: cortex_a53: errata workaround for 835769 was applied
INFO: BL1: cortex_a53: errata workaround for 843419 was applied
INFO: BL1: cortex_a53: errata workaround for 855873 was applied
INFO: BL1: Loading BL2
INFO: Using mmap
INFO: Using FIP
INFO: Loading image id=1 at address 0x201e000
INFO: Image id=1 loaded at address 0x201e000, size = 0x4010
NOTICE: BL1: Booting BL2
INFO: Entry point address = 0x201e000
INFO: SPSR = 0x3c5
NOTICE: BL2: v1.4(debug):e5dbebf
NOTICE: BL2: Built : 20:47:14, May 3 2018
INFO: BL2: Loading BL31
INFO: Using mmap
INFO: Using FIP
INFO: Loading image id=3 at address 0x202a000
INFO: Image id=3 loaded at address 0x202a000, size = 0x7020
INFO: BL2: Loading BL33
INFO: Using mmap
INFO: Using FIP
INFO: Loading image id=5 at address 0x37000000
INFO: Image id=5 loaded at address 0x37000000, size = 0x6b7cf
NOTICE: BL1: Booting BL31
INFO: Entry point address = 0x202a000
INFO: SPSR = 0x3cd
INFO: Boot BL33 from 0x37000000 for 440271 Bytes
NOTICE: BL31: v1.4(debug):e5dbebf
NOTICE: BL31: Built : 20:47:18, May 3 2018
INFO: ARM GICv2 driver initialized
INFO: BL31: Initializing runtime services
INFO: BL31: cortex_a53: errata workaround for 835769 was applied
INFO: BL31: cortex_a53: errata workaround for 843419 was applied
INFO: BL31: cortex_a53: errata workaround for 855873 was applied
INFO: BL31: Preparing for EL3 exit to normal world
INFO: Entry point address = 0x37000000
INFO: SPSR = 0x3c9

U-Boot 2018.01-rc2-ga82c100 (May 03 2018 - 19:27:32 +0800)poplar

Model: HiSilicon Poplar Development Board
BOARD: Hisilicon HI3798cv200 Poplar
DRAM: 1.9 GiB
MMC: Hisilicon DWMMC: 0
In: serial_pl01x
Out: serial_pl01x
Err: serial_pl01x
Net: Net: configured
No such device: mdio0
No such device: mdio0
No such device: mdio1
gmac1
Warning: gmac1 (eth0) using random MAC address - a6:65:70:14:26:8b

Hit any key to stop autoboot: 0

MMC read: dev # 0, block # 8192, count 262144 ... 262144 blocks read: OK
invalid android image
booti - boot arm64 Linux Image image from memory

and then see you reply to 96boards : https://discuss.96boards.org/t/build-with-poplar-source-but-not-work/2893 use a usb stick to boot , but not boot… information is the same as above . "make" confirmation completion . usb stick sda1 filesystem is FAT32 sda2 is ext4 and the contents are also complete. i could not find any other problems. help to see the problem there ,thanks

daniel-thompson commented 6 years ago

You should raise this on the forums. The problem is unlikely to be related to poplar-usbstick since it occurs when you do not use it.

To be honest, even if it was a problem with poplar-usbstick then you would probably still be better off discussing on the forums (since more people would read it).