No poplar# prompt

valir · February 3, 2018, 7:03pm

Hello - new user here

Just received my poplar board and followed the build instructions from the Documentation page.

Following these instructions:

96boards-poplar/Documentation/blob/master/debian/debian_build_instructions.md#flash-images-onto-the-poplar-board-emmc

# Building Poplar Debian System Media From Source

The instructions that follow describe the process for creating image
files suitable for use in a Poplar system.

## Gather required sources

First you'll gather the source code and other materials required to
build the images. These instructions assume you are using Linux based
OS on your host machine.

### Step 1: Make sure you have needed tools installed

  This list may well grow, but at least you'll need the following:

```shell
      sudo apt-get update
      sudo apt-get upgrade
      sudo apt-get install device-tree-compiler libssl-dev u-boot-tools
      sudo apt-get install screen simg2img

This file has been truncated. show original

I successfully connected to the board using screen
I power on the board and press a key in the screen terminal as instructed.

The boot process would ignore any of my keys and go on booting Android 5 which was pre-installed.

Reading the logs, I noticed a prompt “Press Ctrl+C to stop autoboot” so I attempted it. It worked, but I got a fastboot# prompt instead of a poplar# prompt and that one do not have the source command, so I cannot go further and install linaro debian binaries following official instructions.

valir · February 3, 2018, 7:09pm

Here is the log I captured with screen:

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: Apr 7 2016 - 09:27:09

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

System startup

Relocate Boot

Jump to C code

Fastboot 3.3.0 (stb@collin-ubuntu) (Aug 25 2016 - 19:07:47)

Fastboot: Version 3.3.0
Build Date: Aug 25 2016, 19:08:18
CPU: Hi3798Cv200
Boot Media: eMMC
DDR Size: 1GB

Found flash memory controller hifmc100.

MMC/SD controller initialization.
Tuning clk_sample[2,0],set[4],type[1]
Tuning datastrobe[1,15],set[8],type[0]
MMC/SD Card:
MID: 0x15
Read Block: 512 Bytes
Write Block: 512 Bytes
Chip Size: 7456M Bytes (High Capacity)
Name: “8WPD3R”
Chip Type: MMC
Version: 5.0
Speed: 150000000Hz
Mode: HS400
Voltage: 1.8V
Boot Env on eMMC
Env Offset: 0x00100000
Env Size: 0x00010000
Env Range: 0x00010000

SDK Version: HiSTBAndroidV600R002C00SPC031_v2016051915

get chipid =37980200
get chipType (Hi3798CV200)
count=2
mac:00:16:8e:62:66:B2
Reserve Memory
Start Addr: 0x3FFFE000
Bound Addr: 0x8D39000
Free Addr: 0x3ED9A000
Alloc Block: Addr Size
0x3FBFD000 0x400000
0x3F8FC000 0x300000
0x3F87B000 0x80000
0x3F878000 0x2000
0x3F874000 0x3000
0x3F08A000 0x7E9000
0x3F086000 0x3000
0x3EEF0000 0x195000
0x3ED9D000 0x152000
0x3ED9A000 0x2000

Press Ctrl+C to stop autoboot

MMC read: dev # 0, block # 307200, count 20480 … 20480 blocks read: OK

170666666 Bytes/s

Found Initrd at 0x04000000 (Size 825958 Bytes), align at 16384 Bytes

Booting kernel from Legacy Image at 01ffffc0 …

Image Name: Linux-3.18.24_hi3798cv2x
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 8744503 Bytes = 8.3 MiB
Load Address: 02000000
Entry Point: 02000000
XIP Kernel Image … OK
OK

Starting kernel …

Uncompressing Linux… done, booting the kernel.

Bus Width:   8bit
Boot Addr:   0 Bytes

valir · February 3, 2018, 7:48pm

To try to workaround, I decided to create the USB stick and the board recognized it. Only, it stops into an ASSERT. Here is the log:

Bootrom start
Boot Media: eMMC

Entry usb bootstrap

Usb disk(1):
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/02/02 22:22:29+0100 Commit-id ef73d10
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):v1.4-605-g9c00555b
NOTICE: BL1: Built : 22:21:33, Feb 2 2018
INFO: BL1: RAM 0x2016000 - 0x201c000
INFO: BL1: cortex_a53: CPU workaround for 835769 was applied
INFO: BL1: cortex_a53: CPU workaround for 843419 was applied
INFO: BL1: cortex_a53: CPU workaround for 855873 was applied
INFO: BL1: initializing emmc
INFO: BL1: Loading BL2
INFO: Using eMMC
WARNING: Firmware Image Package header check failed.
ERROR: error initializing fip
ASSERT: plat/hisilicon/poplar/plat_storage.c:194

shawnguo · February 4, 2018, 2:49am

Hi valir,

There is a prebuilt fastboot.bin in https://github.com/96boards-poplar/l-loader/tree/master/installer, which should be working for sure. Can you try that?

If you really want to build a fastboot.bin from source by yourself, please read https://github.com/96boards-poplar/Documentation/blob/master/debian/debian_recovery.md

Shawn

vchong · February 4, 2018, 3:17am

For USB stick, you need to build with recovery mode. Instructions are as Shawn listed above, in debian_recovery.md.

valir · February 4, 2018, 11:26am

OK guys, thanks for the reply.

The pre-built boot loader did the trick and now I’ve got the poplar# prompt.

marcosmourino · September 14, 2018, 12:59pm

Hello, another new user here!

I’ve just received my poplar board, and I would like to build and install Android on the board.

I followed the instructions (https://github.com/96boards-poplar/Documentation/blob/master/android/ANDROID-Build.md) and I was able to build AOSP

Then I followed again the instructions and was able to create a USB drive for flashing (https://github.com/96boards-poplar/Documentation/blob/master/android/ANDROID-Flash.md#create-a-usb-drive-for-flashing).

My problem is when I try to install partition table and bootloader. I successfully connected the board using screen and I was able to stop autoboot using Ctrl + C. But I got a fastboot# prompt instead of a poplar# prompt.

I also used the prebuilt fastboot.bin as indicated by shawnguo, but I got the same result.

Any idea?

Thank you!

shawnguo · September 14, 2018, 2:32pm

Can you paste your full screen output? I do not even know what fastboot# prompt is.

dunsin99 · November 26, 2018, 4:43pm

I have gotten to the flashing part and having some issues.
Board Side: fastboot 0
Host side: fastboot devices
//also ran it with sudo
both shows nothing