Jump to content

Ramblings and progress with the RK3399

pbies

By pbies
in Rockchip

 Share

Recommended Posts

R2fan

R2fan

Posted
Posted

This is so painful! out of about 50 attempts, I got it to boot once with the different DDR Version 1.14 20180803 displayed on serial comms,  but then it hang, I presume because I removed the short pin too quickly. 

 

I also tried shorting the both sides of R90303 out in turn (which is closer to the eMMC IC in terms of electrical) , and I think  this did help for the 1 time I got it to work. 

 

Now, the way that works best is to use a very short length of wire (its actually a header pin folded over 180 degrees) , to short out TP50265 and GND pins - this works 3 out of 5 times now., and I am able to get the Armbian login. Great!!

 

I also managed to press space bar within 2 seconds of booting, to access uboot, and did:

 

 

setenv devnum  1

run mmc_boot

 

but this did not persist on rebooting the unit. 

 

I also tried changing the apparent order of boot devices:

 

setenv boot_targets 'mmc1 mmc0 usb0 pxe dhcp'
saveenv

 

but get this:

 

Saving Environment to EXT4...
** Unable to use mmc 0:auto for saveenv **
Failed (1)
 

did you do anything else to your uboot?

 

Thanks. 

 

  Reveal hidden contents

 

for reference - schematics.

  Reveal hidden contents


 

R2fan

R2fan

Posted
Posted

Just for my understanding @martinayotte - when we make changes by "setenv ..."  after entering uboot by pressing space bar, that is trying to write to the uboot on eMMC, right? Do you think there is any write protect on this by default? 

 

when trying to saveenv I still get 

 

Saving Environment to EXT4...
** Unable to use mmc 0:auto for saveenv **
Failed (1)

 

Thanks

 

Igor

Igor

Posted
Posted
  On 1/31/2019 at 1:44 PM, R2fan said:

when we make changes by "setenv ..."  after entering uboot by pressing space bar, that is trying to write to the uboot on eMMC

Expand  


Have you installed Armbian to eMMC? Only after that, you can use those commands to boot from SD card again. If you need to - if you broke the OS on eMMC. If you totally broke everything, you need to enter Maskrom mode again by shorting pins ...

R2fan

R2fan

Posted
Posted

No - its running the factory Android on eMMC. Only have Armbian on SD card.  Is "nand-sata-install" the right thing whilst booted from SD card armbian? 

martinayotte

martinayotte

Posted
Posted
  On 1/31/2019 at 3:25 PM, R2fan said:

Is "nand-sata-install" the right thing whilst booted from SD card armbian? 

Expand  

If you wish to get rid of Android and having Armbian installed on eMMC, yes, "nand-sata-install" is the tool for that ...

 

R2fan

R2fan

Posted
Posted

OK, well good and bad news - 

I started getting very slow / inconsistent SSH and serial comms, but did manage to go through nand-sata-install via serial, and install to eMMC. Now I dont have Android on eMMC, and appears to be Armbian - great. 

 

but now,  it just gets stuck in reboot cycle: 

 

 

  Reveal hidden contents

 

when I try to boot from SD card (I tried 3 different, recently opened from packet, and tried bionic images and Stretch), using space-bar to uboot, setenv devnum  1, run mmc_boot, I get this:

  Reveal hidden contents

 

EDIT:

one of the SD cards just worked, so am in via serial, but it is all a little strange at the moment,  ill try installing to eMMC again with nand-sata-install. 

EDIT2: 

Ill try to verify the genuine-ness of these SD cards with H2testw. (they are Sandisk Ultra 16GB A1). 

 

Any ideas?

Thanks

 

Igor

Igor

Posted
Posted
  On 1/31/2019 at 8:00 PM, R2fan said:

Applying user provided fixup script (fixup.scr)
## Executing script at 39000000
Wrong Ramdisk Image Format
Ramdisk image is corrupt or invalid
SCRIPT FAILED: continuing...

Expand  


This suggest some corruption. Make sure you use good SD card (sometimes SD card brand or too fancy SD card could be an issue) and proven writing method ... and a good PSU to rule out most stupid errors.

Myy

Myy

Posted
Posted

Post pour `printenv` just for confirmation.

I think that mmc_boot just throw a setenv devnum X before running another script, which basically cancel your modification.

R2fan

R2fan

Posted
Posted

printenv:

  Reveal hidden contents

 

when I try to boot from SD card now by pressing space bar to get into uboot, and do setenv devnum 1, run mmc_boot. 

 

I just re-burnt this SD card with Etcher (validated OK), and changed PSU to a ATX PC style PSU.  (made no difference to the situation). 

 

  Reveal hidden contents

Thanks

R2fan

R2fan

Posted
Posted

plugging in an HDMI and keyboard, I can login OK. I did nand-sata-install, and this time selected option 5 (Install/Update the bootloader on SD/eMMC), and then re-selected option 2 (boot from eMMC - system on eMMC). 

 

so it boots now, but for some reason either the ethernet does not get a DHCP sometime, or when it does, putty hangs (as does SSH from a raspberry pi) when I type in the password. This is for root and normal users. 

 

I need to take a break from this board for a while, but in passing, has anyone managed to get mini PCIe wifi boards working with this board? or with any RK3399 board (NEO4, etc)? I see no output from lspci. 

 

Thanks

 

Igor

Igor

Posted
Posted
  On 2/1/2019 at 11:28 AM, R2fan said:

so it boots now, but for some reason either the ethernet does not get a DHCP sometime, or when it does, putty hangs (as does SSH from a raspberry pi) when I type in the password. This is for root and normal users. 

 

I need to take a break from this board for a while, but in passing, has anyone managed to get mini PCIe wifi boards working with this board? or with any RK3399 board (NEO4, etc)? I see no output from lspci. 

Expand  


RK3399 board support and especially this board is months/a year away from being stable/matured. Those images were made for development/testing purposes only.  PCI stack on a modern kernel is completely broken at this moment. On all boards.

gounthar

gounthar

Posted
Posted

How can we power an SSD when using Sata on this board? Is there some kind of power splitter somewhere?
I'm using the barrel connector to power the board.
Thanks.

 

NicoD

NicoD

Posted
Posted
  On 5/14/2019 at 4:25 PM, gounthar said:

How can we power an SSD when using Sata on this board? Is there some kind of power splitter somewhere?

Expand  

Hi.
There are multiple threads about that.
Look here.

Quote from @Da Alchemist
 

  Quote

There must be two connections to the SSD of course, power and sata (there are cables for both connections).  If everthing is allright, there must be a green and a red LED turned on. Is your SSD formatted?  If not use Gparted to get it formatted.

Expand  

I hope that helps.

pfry

pfry

Posted
Posted
  On 5/15/2019 at 5:56 AM, gounthar said:

The OrangePi RK3399 doesn't have that kind of Molex connector, but I will keep searching.

Thanks for your help.

Expand  

The Orange Pi RK3399 has 5V and 3.3V available on the 40-pin header (and nowhere else that I can see offhand). Pinout is in the manual; it's a standard .1"/2.54mm header - lots of connector options. The mSATA interface is a bit inconvenient (uncommon); it also has 3.3V power available - perfect for an mSATA device; not much use if you're adapting it to a 2.5" device. I didn't check to see how much power is available, but I'd expect it to be fine for typical devices.

 

1
gounthar

gounthar

Posted
Posted
  On 12/3/2018 at 12:04 AM, Myy said:

Alright, turns out that the 

/path/to/your/rkdeveloptool rd # Reboot

step in my procedures wasn't rebooting the board anyway.

So, basically, when in Maskrom mode (the mode you are in when the serial console is quiet, or when you keep the "Recovery" button pushed with the Right U-Boot), all writes are "as-is".

If you reboot (unplug and plug the power cable back again) with a Loader, a Firmware and the Trust image, you'll get into a special "rockusb" mode that offset everything by 0x2000 sectors (0x2000 * 512 bytes).

 

Since I'm not interested in that special rockusb mode, here's the "right" process for installing a U-Boot and Trust.img when you are in "quiet" mode :

  

/path/to/your/rkdeveloptool db /path/to/RK3399MiniLoaderAll_V1.05_DDR600MHz.bin # Write the Bootloader
/path/to/your/rkdeveloptool ul /path/to/RK3399MiniLoaderAll_V1.05_DDR600MHz.bin # Which is also their firmware
/path/to/your/rkdeveloptool wl 0x4000 /path/to/uboot.img # Write the U-Boot image
/path/to/your/rkdeveloptool wl 0x6000 /path/to/trust.img # Write the Trust bits
# "Turn it off and on again" by unpluging and plugging the power cable back (Either the USB-C cable or the power plug)
# Rebooting through the little button generate "Tinkerboard"-esque issues with the eMMC, which won't be properly power up anymore.

 

Now, if you already have an eMMC image, you can do this instead :

  

/path/to/your/rkdeveloptool db /path/to/RK3399MiniLoaderAll_V1.05_DDR600MHz.bin # Write the Bootloader
/path/to/your/rkdeveloptool ul /path/to/RK3399MiniLoaderAll_V1.05_DDR600MHz.bin # Which is also their firmware
/path/to/your/rkdeveloptool wl 0 /path/to/eMMC.img # This will be STUPIDLY slow. You'll have to wait betweens 10 and 30 minutes.
# Unplug and plug the power cable back again, after the command finishes.

 

I tested successfully these last steps and, therefore, have been able to directly flash my semi-working Armbian installation based on the Firefly RK3399 image.

 

So, the current step now is "Getting a Rockchip kernel working correctly with this board".

Expand  

Thanks for these commands. They helped me getting my board out of a strange mode where it only displayed hw 0 0 0 0 0 0 0 0 0 0 and powerOn "someNumbers". Before that, I could not get into MASKROM mode anymore, nor in LOADER mode... It appeared kind of bricked to me.
By the way, I read there that one could get into MASKROM mode from software by zeroing part of the boot partition.
That's what got me into that "almost bricked" mode.
If anyone has the correct sequence of commands that could do it, I will use it from now on.

1
gounthar

gounthar

Posted
Posted

I made some progress with this board, but am still stuck with its Debian version because of the HDMI-IN thingie (upgraded to Sid).
I now have a working hardware accelerated ffmpeg for decoding (thanks to rkmpp), but no hardware accelerated encoding.
The RockChip gstreamer fork has h.264 hwaccel, but it freezes the board way too often.
OrangePi has finally made available a camera for this board, as the one from FriendlyArm froze the board too.

I haven't been able to recompile a kernel on the board itself yet, but I'm working on it.

gounthar

gounthar

Posted
Posted

I rebuilt the image for my RK3399 two days ago, and it is stuck at boot with this message:

  Reveal hidden contents

I rebuilt it today, and have the same output:

  Reveal hidden contents

 

gounthar

gounthar

Posted
Posted

I also downloaded Armbian Buster desktop legacy kernel 4.4.y and I got

  Reveal hidden contents

With Buster minimal 5.4 I got

  Reveal hidden contents

 

gounthar

gounthar

Posted
Posted

With Buster server I got:

  Reveal hidden contents

 

gounthar

gounthar

Posted
Posted

Today's build went farther on the OrangePi RK3399:

  Reveal hidden contents

It is now stuck, but it never got that far previously for me.

Guest
This topic is now closed to further replies.
 Share
Go to topic listing
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines

  I accept