./mk-uboot.sh rk3399-orangepi problem

iinvestigator

admin replied at 2018-8-9 20:00
./build/mk-image.sh -c rk3399 -t system -s 4000 -r out/OrangePi-rk3399_Debian9_20171218img

This  ...

Hi admin.

I have preinstalled Android on my OrangePi RK3399.

OrangePi RK3399_RK3399_User Manual_v1.4 for PCB V1.5.pdf {

On Linux, the tool we use is upgrade_tool which is same with working on Windows. Enter into
Loader flashing mode like the following:
 Type-A Connect to PC (Done)
 Press on Recovery key of Orange Pi RK3399 (Done) [Press and hold | Press and free -- both ways tried]
 Type-C Connect to Orange Pi RK3399 (Done) [Recovery key -- free at that step]
 Insert DC power supply (Done) [Recovery key -- free at that step]
Since OrangePi RK3399 supports powered by TypeC, power voltage on USB of PC is enough for
flashing image. However, it may not enough to support Orange Pi booting. In that case, we need to
insert DC power supply to make sure the Orange Pi could boot successfully after flashed image.

}

insert DC power supply (but that step where perfomed before) at  Insert DC power supply.

Ok All done. At the current time I can see black screen that in "Active" stage. Nothing more. Also via usb connector I have see at my local machine

root@u# ./upgrade_tool
List of rockusb connected
No found rockusb,Rescan press <R>,Quit press <Q>:q
root@u# adb shell
shell@rk3399_mid:/ $
130|shell@rk3399_mid:/ $ exit
root@u# dmesg  | grep usb
[162198.775304] usb 1-4: new high-speed USB device number 28 using xhci_hcd
[162198.916237] usb 1-4: New USB device found, idVendor=2207, idProduct=0011
[162198.916247] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[162198.916254] usb 1-4: Product: rk3399-mid
[162198.916261] usb 1-4: Manufacturer: rockchip
[162198.916267] usb 1-4: SerialNumber: CBI9SBJG62
[162200.687352] usb 1-4: USB disconnect, device number 28
[162413.245568] usb 1-4: new high-speed USB device number 29 using xhci_hcd
[162413.386558] usb 1-4: New USB device found, idVendor=2207, idProduct=0011
[162413.386569] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[162413.386576] usb 1-4: Product: rk3399-mid
[162413.386582] usb 1-4: Manufacturer: rockchip
[162413.386588] usb 1-4: SerialNumber: CBI9SBJG62
[162473.917299] usb 1-4: reset high-speed USB device number 29 using xhci_hcd
[162474.445416] usb 1-4: reset high-speed USB device number 29 using xhci_hcd

So. If I've correct understand next step by doc -- is short connect to CleaR eMMC....


OrangePi RK3399_RK3399_User Manual_v1.4 for PCB V1.5.pdf {

If there is no Loader device, then you need to flash image with short connect like the following:
When short connect EMMC Clk and GND, insert DC power supply, enter into Maskrom mode. And
insert Type-C cable to connect both PC and RK3399

}

But if done that

1.where is guarantee that health of my board is normal after that short connect by doc?

2. how does "upgrade_tool" can see device after short connection if now "upgrade_tool" doesn't see the board?


Please help me understand what I've done wrong.

Also could you please

1. (Linux) make shell script to install all required packages and modules with last automatic step flasing (Debian/L/Ubuntu).img.
2. (Windows) modefy AndroidTool to flasing (Debian/L/Ubuntu).img.


Thank you

pbies

Recovery button=key is making Pi boot into flash-firmware mode. The same does the short connect those two pins, but should be used only if eMMC is not booting (not giving possibility to be seen by PC).

gounthar

Why do I have to go into MASKROM mode to flash a Linux image, and can I do under Windows for Android with just LOADER mode?