Jump to content

Recommended Posts

Posted

Hello everyone!
I update you on my situation, I managed to delete the emmc and to start armbian with the mainline kernel.
But now my problem is another, I would like to flash the armbian image directly on the emmc but I can't understand the procedure to do on windows, any help?

Thanks in the meantime

Posted
  On 4/22/2020 at 5:34 PM, MMarcio said:

Hello everyone!
I update you on my situation, I managed to delete the emmc and to start armbian with the mainline kernel.
But now my problem is another, I would like to flash the armbian image directly on the emmc but I can't understand the procedure to do on windows, any help?

Thanks in the meantime

Expand  

Windows?

You could either run armbian-config to transfer the system from the sdcard to the emmc or use rkdeveloptool to write the image directly on the emmc.

Posted
  On 4/22/2020 at 6:52 PM, jock said:

Windows?

You could either run armbian-config to transfer the system from the sdcard to the emmc or use rkdeveloptool to write the image directly on the emmc.

Expand  

I'm trying to use rkdeveloptool on windows but I don't understand how to set it, it gives me firmware loading error

Posted

Hi, I'm a newbie and first of all, I would like to thank you @jock and @fabiobassa for this. I've got an MXQ Pro 4k lying around and out of curiosity I saw this post that it's possible to run Linux on this box. I've tried the steps on the first post and I boot with SD card on successfully, however, whenever I'm trying to do the sudo armbian-config command, there is no option to install to emmc (only one option is available - update boot). I can successfully rkdeveloptool ef and rkdevelop wl 0x0  the Armbian 20.05.0 - Ubuntu Focal Desktop - Legacy kernel 4.4.194 img into the box, but it is not booting. Only weak blue and red lights were on. Any idea on how I can install this to the emmc? BTW, my box says RK32Q v3.0.

Posted

hello @Mark Khevin Rogacion and ty for joining in this adventure
Yes you right because your 329q has a nand and not an mmc

But

@jock is actively and strongly working on a simple tool that in future will avoid all this mis-confusing due to different commercial names . So kindly wait just some little time that the new tool will be perfectly functional

Posted (edited)
  On 4/23/2020 at 5:24 PM, fabiobassa said:

hello @Mark Khevin Rogacion and ty for joining in this adventure
Yes you right because your 329q has a nand and not an mmc

But

@jock is actively and strongly working on a simple tool that in future will avoid all this mis-confusing due to different commercial names . So kindly wait just some little time that the new tool will be perfectly functional

Expand  

is it possible that I am also confusing the memory types? I also can't find the command on armbian-config to install on emmc / nand

 

nand-e-rev.jpg

Edited by MMarcio
Posted

@MMarcio
yes you too have a nand, but I already said this to you: mostly r329q have nands... ( mostly :( )

But on the other hand.. they have wonderfull ddr3 at 600 mhz very powerfull, while some boards with emmc have " only " ddr2 at 330 mhz

 

Posted

@MMarcio @nokirunner

Here we are, here there is the first version of the Multitool.

That's an image to burn on an sd card: plug it into the tvbox and it will boot allowing backup, restore, erase and image burn on the internal eMMC.

To burn armbian/libreelec images directly to internal eMMC memory, place the compressed images into images folder of the sdcard and use the relative function of the Multitool. Any feedback is welcome!

 

@Mark Khevin Rogacion I'm sorry but your box is unlucky to have a NAND chip instead of more common eMMC memory. Since there are no open drivers for rockchip nand, there are limited functionalities (like no kernel/uboot updates) and putting the rootfs on the NAND still require manual working. Me and @fabiobassa are working on a way to let armbian installation work the best, but at the moment you should stick to external sdcard.

Posted

@MMarcio

MMhhh, I just noticed that your internal flash is a NAND too. Sorry but the same limitations applies to you and for now you are limited to external sdcard -_-

Posted

@fabiobassa thanks for the information as well as to @jock. That being said, is there a possibility that we can boot from the USB OTG port instead of the sdcard? tried to burn it to usb and replaced the sd card with the burned image to usb and no luck booting.

Posted
  On 4/24/2020 at 2:29 PM, Mark Khevin Rogacion said:

@fabiobassa thanks for the information as well as to @jock. That being said, is there a possibility that we can boot from the USB OTG port instead of the sdcard? tried to burn it to usb and replaced the sd card with the burned image to usb and no luck booting.

Expand  

Hello. Yes, there should be the chance to boot from USB stick.

 

First I want to apologize because after a recent discovery I get aware that doing rkdeveloptool ef on a NAND device also removes the bootloader. Due to the NAND peculiarities, tooling around with that piece of software makes further restore of the firmware very difficult.

 

I just updated the first post with new instructions, there is the Jump Start procedure for those who own a box with NAND flash that will install the bootloader into NAND to let SD Card and USB stick boot. You may give it a chance.

Posted

Hi there, I recently just came across this thread and is pleasantly surprised and happy that there are still on-going developments on our old-ish RK322x devices! :)

Before seeing this thread, I was rockin' a MX4-V10 RK3229 (?) Android Box with an old respeaker img on a sd card which I found months ago.

Pictures of the android box and internals for reference:  MX4-V10 Pics

 

I actually already tried to burn "Armbian_20.05.0-trunk_Rk322x-box_buster_current_5.5.16_minimal.img.xz" into an sd card and the box failed to boot. I then burned "LE_bootloader_Armbian_20.05.0-trunk_Rk322x-box_buster_current_5.5.16_minimal" into an sd card and the box successfully booted.

It seems to be working fine upon initial check but I just wanted to clarify a few things so I can do over the setup in case there's a more optimal/correct way of doing it:

 

1. Does my box have NAND or eMMC internal storage?

2. If NAND, is it ok to use any of the 3 types of images (focal legacy, buster legacy, buster mainline)? I'm a bit confused on "NAND is available only on legacy" on 1st post.

3. Also if NAND, which is better:

       a. Use newly created Multitool and install Jumpstart. burn 1 of the 3 original img to sdcard and plug in to the box.

       b. Use the IMGs posted by @Maker39 with the built in Libreelec bootloader

4. Finally, upon installation, which of the boards do I pick when running rk322x-config? Is it ok to pick again after initial selection? If I were to do trial and error, what do I watch out for to check that I picked the correct board?

 

Thanks so much!

Posted

@paulml

your board is a 3228b with 1 giga ram and nand 
1) once more , and unfortunately at the moment , your board has a nand storage
2) as long as you run by sd card and SKIP the approach to flash internal storage ( since it is nand) everything will be ok
3) simply don't touch internal android installation and run from sd, for the moment

tool for manage even nand is on the way :-)
 

Posted
  On 4/23/2020 at 7:13 PM, jock said:

Here we are, here there is the first version of the Multitool.

Expand  

I tried a new tool and have some results.

On one board (RK3229, 8G eMMC, 1G RAM), operations with eMMC are available from the menu.

But on another board (RK3229, 16G eMMC, 2G RAM, it is blue in the photo I used to upload) eMMC is not seen as a tool.

lsmmc also displays only mmcblk0.

If you need more information, tell me what and how to do it.

Unfortunately SSH is not here :(

Posted
  On 4/24/2020 at 5:34 PM, Maker39 said:

I tried a new tool and have some results.

On one board (RK3229, 8G eMMC, 1G RAM), operations with eMMC are available from the menu.

But on another board (RK3229, 16G eMMC, 2G RAM, it is blue in the photo I used to upload) eMMC is not seen as a tool.

lsmmc also displays only mmcblk0.

If you need more information, tell me what and how to do it.

Unfortunately SSH is not here :(

Expand  

I have seen the photos you posted. The eMMC is a sandisk and should be well supported in HS-200 mode.

If you feel brave, you can decompile the device tree (rk322x-box.dtb in the FAT partition), find and remove mmc-hs200-1_8v; then recompile it back and try again. That's the only thing it may interfere with hardware detection -_-

Posted
  On 4/24/2020 at 4:15 PM, paulml said:

I actually already tried to burn "Armbian_20.05.0-trunk_Rk322x-box_buster_current_5.5.16_minimal.img.xz" into an sd card and the box failed to boot. I then burned "LE_bootloader_Armbian_20.05.0-trunk_Rk322x-box_buster_current_5.5.16_minimal" into an sd card and the box successfully booted.

Expand  

Yep, Armbian image is not "plug&play", requires some preparation of the board because the purpose (server machine/all purpose desktop) is different than LibreElec.

 

  On 4/24/2020 at 4:15 PM, paulml said:

2. If NAND, is it ok to use any of the 3 types of images (focal legacy, buster legacy, buster mainline)? I'm a bit confused on "NAND is available only on legacy" on 1st post.

Expand  

NAND is available as a storage device only if you use legacy kernel 4.4 images. Mainline kernels do not have the necessary driver to access it.

As a boot device it is not usable at all at the moment.

  On 4/24/2020 at 4:15 PM, paulml said:

3. Also if NAND, which is better:

       a. Use newly created Multitool and install Jumpstart. burn 1 of the 3 original img to sdcard and plug in to the box.

       b. Use the IMGs posted by @Maker39 with the built in Libreelec bootloader

Expand  

Option a (JumpStart) is almost full Armbian, so it allows all the updates of the kernels when they will be programmed and software, also allows to boot from external SD Card and USB Stick, but prevents the internal image to boot (due to missing NAND driver above)

Option b (Maker39 images), are plug and play, don't require tinkering with internal NAND, but may miss some low-level updates in the future

  On 4/24/2020 at 4:15 PM, paulml said:

4. Finally, upon installation, which of the boards do I pick when running rk322x-config? Is it ok to pick again after initial selection? If I were to do trial and error, what do I watch out for to check that I picked the correct board?

Expand  

Usually they fix LED behaviour, WiFi detection and NAND/eMMC selection.

You can do by trial and error, you should not get stuck but in case, just remove the line "fdtfile=" from /boot/armbianEnv.txt on the sdcard to restore the default board.

Posted
  On 4/24/2020 at 5:58 PM, jock said:

I have seen the photos you posted. The eMMC is a sandisk and should be well supported in HS-200 mode.

If you feel brave, you can decompile the device tree (rk322x-box.dtb in the FAT partition), find and remove mmc-hs200-1_8v; then recompile it back and try again. That's the only thing it may interfere with hardware detection -_-

Expand  

Yes !!! :thumbup:  it worked :beer:

 

p.s. since with such a powerful tool I can now save and restore the android on this box I tried to flash armbian in eMMC .

Armbian_20.05.0-trunk_Rk322x-box_buster_current_5.5.16_minimal    fully loaded

but

Armbian_20.05.0-trunk_Rk322x-box_focal_legacy_4.4.194_desktop

Armbian_20.05.0-trunk_Rk322x-box_buster_legacy_4.4.194_minimal

stop at "random: nonblocking pool is initialized"

 

Posted
  On 4/24/2020 at 6:27 PM, Maker39 said:

Yes !!! :thumbup:  it worked :beer:

 

p.s. since with such a powerful tool I can now save and restore the android on this box I tried to flash armbian in eMMC .

Armbian_20.05.0-trunk_Rk322x-box_buster_current_5.5.16_minimal    fully loaded

but

Armbian_20.05.0-trunk_Rk322x-box_focal_legacy_4.4.194_desktop

Armbian_20.05.0-trunk_Rk322x-box_buster_legacy_4.4.194_minimal

stop at "random: nonblocking pool is initialized"

 

Expand  

Hmm, never experienced such problem, also because the message is from kernel and is totally normal.

  1. Do you mean it stopped because the progress bar was not increasing or did it give you an error?
  2. Do you get the message on the screen of just on the serial? Also was the serial still responding?
  3. Did you try to load up all the three images in the same session or in separate sessions?
  4. Note that the blue led is normally blinking fast when you read or write into emmc, did you notice if it was blinking or it was steady on or off when it stopped?

It happened to me that the screen freezed after 10 minutes, it is normal because the kernel blanks the screen after some minutes of inactivity. Rockchip HDMI kernel driver has an issue that makes freeze the screen, but is sufficient to press a key to restore the screen updates.

I disabled this in the kernel command line, so it should have not happened... but don't know

 

Anyway thanks for testing!

Hint: the multitool works also for libreelec images ;)

Posted

As I did in the steps:

1 Burn Multitool on SD

2 Put in  /images all armbian from first post

3 Boot from SD

4 Erase flash

5 Burn image to flash

6 Shutdown and power off

7 Remove SD and  power on

A monitor is connected to HDMI, the series on this board has not been soldered yet

the system log is loading on the monitor screen

as I reported

Armbian_20.05.0-trunk_Rk322x-box_buster_current_5.5.16_minimal    fully loaded

but

Armbian_20.05.0-trunk_Rk322x-box_focal_legacy_4.4.194_desktop

Armbian_20.05.0-trunk_Rk322x-box_buster_legacy_4.4.194_minimal

log stoped at "random: nonblocking pool is initialized"

 

LED  is always ON .

 

Now I will try to erase the flash and transfer the system using armbian-config...

In general, I failed.

Erase eMMC, boot from SD with Armbian_20.05.0-trunk_Rk322x-box_buster_legacy_4.4.194_minimal

But no eMMC

root@rk322x-box:~# lsblk
NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
mmcblk0     179:0    0   1.9G  0 disk
└─mmcblk0p1 179:1    0   1.7G  0 part /
zram0       253:0    0    50M  0 disk /var/log
zram1       253:1    0 997.6M  0 disk [SWAP]
root@rk322x-box:~#

 

I try remove mmc-hs200-1_8v from /boot/rk3229-box-hk1mini.dtb (because this config selected).

did not help.

Try other 3229 configs from rk322x-config -nothing don't help.

It looks like the eMMC on this board is somehow special, or I'm doing something wrong. One thing is clear - Mulitool is not guilty

 

Armbian_20.05.0-trunk_Rk322x-box_buster_current_5.5.16_minimal - all ok !

root@rk322x-box:~# lsblk
NAME         MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
mmcblk0      179:0    0   1.9G  0 disk
└─mmcblk0p1  179:1    0   1.7G  0 part /
mmcblk2      179:16   0  14.7G  0 disk
mmcblk2boot0 179:32   0     4M  1 disk
mmcblk2boot1 179:48   0     4M  1 disk
zram0        252:0    0    50M  0 disk /var/log
zram1        252:1    0 987.2M  0 disk [SWAP]
zram2        252:2    0 987.2M  0 disk /tmp
root@rk322x-box:~#

 

Posted

@Maker39

The multitool did its work, but I think that the problem you're having is the same as before: the mmc-hs200-1_8v; line in the device tree prevents the correct detection of the eMMC by the kernel, so it hangs. Normally the driver automatically resorts to a slower but safer mode, but it is not happening for your board.

Need to fix this in the Armbian images

 

Posted
  On 4/25/2020 at 8:48 AM, jock said:

@Maker39

The multitool did its work, but I think that the problem you're having is the same as before: the mmc-hs200-1_8v; line in the device tree prevents the correct detection of the eMMC by the kernel, so it hangs. Normally the driver automatically resorts to a slower but safer mode, but it is not happening for your board.

Need to fix this in the Armbian images

 

Expand  

I tried changing my dtb in /boot/dtb-4.4.194-rk322x - it did not help.

Posted
  On 4/25/2020 at 8:57 AM, Maker39 said:

I tried changing my dtb in /boot/dtb-4.4.194-rk322x - it did not help.

Expand  

Just to be sure, since that happened a ton of times to me: did you remember to compile the dts back to dtb?

A dmesg log would be interesting to see.

Posted

I'm sure, i recompile patched dtb to dts and read this B)

dmesg with "original" dtb

  Reveal hidden contents

 

Posted

dmesg with "patched" dtb (remove mmc-hs200-1_8v)

  Reveal hidden contents

 

Posted

@Maker39

Well, I don't see any eMMC controller in your dmesg (30020000.dwmmc)

Try with another board with rk322x-config. Still you need to remove hs200 mode from the device tree you select.

I think the eMMC node of the board you selected is just disabled in the device tree. :unsure:

Posted
  On 4/25/2020 at 10:07 AM, Maker39 said:

Is it correct, do I understand, I need to remove hs200 from all 3229.dtb and try different configurations?

Expand  

You can change status="disabled" into status="okay" from your HK1 device tree to activate the emmc node. Then recompile dtb, reboot and it should work.

Or, as you said, remove the hs200 from all the 3229 dtbs and try them all.

 

edit: I'm going to upload refreshed Armbian images without the hs200 line later, also because Focal now has been released and  contains official packages.

 

 

 

Posted

"You can change status="disabled" into status="okay" from your HK1 device tree to activate the emmc node. "

Then recompile dtb, reboot and it should work."

Yes, it work ! :thumbup:

Now i boot from sd and move system to eMMC.

System started and loaded succesfully .

 

ps Maybe because of these settings the image recorded by Multitool did not load?

Posted

Great work! @fabiobassa @Maker39 and @jock biggest thanks on earth for the development and that you still hang on finding solutions for NAND boards! Please keep on developing and I think the boards are better choices than raspberry pi's... 

 

How is the performance with your images and do we really get gpu acceleration for videos? Is it working with h265 too? 

Posted

@fabiobassa @jock Thank you very much for the help. I’ll be using what I have now (img with LibreELEC bootloader on ext sd card) for the meantime as it works much better than what I previously had (respeaker). Btw will using the multitool write anything in the internal NAND? I’m actually hesitant to use it now fearing I might not be able to use future method of writing to NAND if you guys do eventually succeed in making it.

 

Also, if ever you release updated builds, how do I properly update? Do I need to setup and install everything again from scratch?

 

@Alex83 I’m actually wondering about the same thing re raspberry pi (I don’t own any). Aren’t these rk322x boards better and more powerful than rpi? It might be cheaper too after case and accessories. Rpi boots from sd cards as well right?

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines