./mk-uboot.sh rk3399-orangepi problem

constantius

radek@celeronG1610:~/DYSK22/rk-linux/build$ ./mk-uboot.sh rk3399-orangepi
Building U-boot for rk3399-orangepi board!
Using orangepi-rk3399_defconfig
make: *** Brak reguł do wykonania obiektu 'orangepi-rk3399_defconfig'. Stop.( no rules to make object orangepi-rk3399_defconfig. STOP
MAKE UBOOT IMAGE FAILED.

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

admin

constantius replied at 2018-3-21 17:01
Hi - thanks it helps
1. And then I have created uboot and kernel.img
2. and then i did ./build/mk-im ...

./build/file:///C:\Users\Administrator\AppData\Roaming\Tencent\QQ\Temp\%W@GJ$ACOF(TYDYECOKVDYB.pngmk-image.sh -c rk3399 -t system -s 4000 -r out/OrangePi-rk3399_Debian9_20171218img

This command is worng.  OrangePi-rk3399_Debian9_20171218img is a complete image.
Pls take a carefully look at the user manual of rootfs.

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).

teo

Hi

The directory location of the script you are running is incorrect.
Please execute the script by the following procedure.

cd ~/DYSK22/rk-linux/
./build/mk-uboot.sh rk3399-orangepi

constantius

Hi - thanks it helps
1. And then I have created uboot and kernel.img
2. and then i did ./build/mk-image.sh -c rk3399 -t system -s 4000 -r out/OrangePi-rk3399_Debian9_20171218img
system.img is created.
3. next i put single board in maskroot mode according tro manual
4 did ./build/flash_tool.sh -c rk3399 -p system -i out/system.img
5. output from this command is.:
./build/flash_tool.sh -c rk3399 -p system -i out/system.img
PARTITIONS OFFSET: 0 sectors.
[sudo] hasło użytkownika radek:
Downloading bootloader succeeded.
Write LBA from file (100%)
Reset Device OK.
7. when i put orangepi-rk3399 into power connection i have black screen
no system at all - monitor i blanking blue -is recognized but nothing is running

8 Question what i did wrong????

constantius

PS. when i have working system.img's i can share it via google.drive

constantius

No one wants help???

constantius

I tried build and flash image according to the manual using existing rootfs.img file.:
./build/mk-image.sh -c rk3399 -t system -s 4000 -r out/OrangePi-rk3399_Debian9_20171218.img
next i put single board in maskroot mode according to manual
./build/flash_tool.sh -c rk3399 -p system -i out/system.img

and when i run single board i have black screen, nothing is booting
Is your manual correct??????????????? or i did something wrong
please reply

constantius

I have tried flash build system.img and flash separetly img uboot and boot and prepeared rootfs.img file without lack.
Is manual written correct? or is rootfs.img prepared correctly?
When do you prepared working img linux files for orangepi rk3399?

DataMannen

constantius replied at 2018-3-24 20:04
I have tried flash build system.img and flash separetly img uboot and boot and prepeared rootfs.img  ...

I have had pretty much the same problems as you, but while trying to get it to boot from a sdcard instead of flashing the eMMC. I thought that maybe I had a crappy sdcard but now I'm not so sure.

I've tried all the things you list and a couple of other "tricks" without success. It simply will not boot.

My guess is that OrangePi RK3399 and the sdcard are working fine and that I'm simply doing something wrong, so I will probably get it to work eventually. But I totally agree with you that the manual is not very clear on some issues and the pre-built image-files (for example OrangePi-rk3399_Debian9_20171218.img) should work right away by just writing them to my sdcard and boot. They don't. Atleast for me.

iinvestigator

Hi All

Could anybody get sucsess to flashing "OrangePi-rk3399_Debian9_20171218.img" or any another Linux images (Ubuntu/LUbuntu)?