Posts by oneillb

I've continued to work with the 10.x builds and if found that the sv6051p wifi driver is a the likely cause of many of the random lockups and crashes I've been seeing. I've blacklisted the module now completely, and stability seems to be much much better. I'm going to leave the box running for a soak test for several hours to check

I'd like to use the board with a wireless network... Does anyone have any recommendations for a reliable and preferably cheap USB dongle I can use with these Libreelec 10.x builds, preferably one already supported buy the available kernel builds?

Quote from jock2

The gzipped libreelec image is burned very quickly because the uncompressed libreelec image is quite small (500 megabytes circa); the backup of the existing Android is the same of the whole NAND (8 gigabytes I guess).

Multitool is quite capable to handle gzip and other compressed formats: it will decompress them on the fly while burning is in progress, so no need to do that manually.

A possible issue that may come from your steps is the Flash Erase step you said you did. I don't remember if it is so, but it may be that the Erase Flash step completely erases the NAND, idbloader included. idbloader can't be installed again by multitool because of the NAND rockchip driver limitation and you may need to do that manually using rockchip upgrade_tool (see this post on armbian forum, paragraph
NAND Bootloader Upgrade)

I don't think I've removed the idbloader, I can reinstate the Android backup image using Multitool, and return everything back to as it was. Does that mean that idbloader is still intact?

Is there a good place to read up on that part uboot, idbloader and the kernel play in the boot process...

Thanks again.

I suspect that Multitool isn't uncompressing the images, as the 130MB .img.gz image burns much quicker than a the 550 MB uncompressed .img which shouldn't be happening, but I haven't timed it so it may just be a perception. To be sure, I now only use multitool with uncompressed images, using the "5. Burn image to flash" option (not Jump Start or steP-nand options) and not skipping idbloader, but I still cant get LE to boot from Nand.

Looking at what dmesg reports when I run up Multitool

Kernel as Linux 4.4.194-rk322x

rknandbase v1.2 2018-05-08

rknand 30030000.nandc

No1 FLASH ID:2c 64 32 a5 0

The nand chip on the board is a Labelled Micron NW814

I've ordered a malemale USB cable, so may have a go using rkdeveloper. I've also ordered a CP2104 USB-Uart adapter to get at the serial console output directly off the board which may help diagnose what's going on.

Thanks for your help so far.

Barry

RE: the wireless issue with SSH and image LibreELEC-RK322x.arm-10.0-nightly-20220329-c3a59e9-rk322x.img

I've changed the extlinux.conf file to utilise the /rk3229-box-v88mars.dtb and then /rk3229-box-v88mars-ovclk.dtb overlay and the wlan seems to be generally more stable as a result.

RE: Burning the latest image to internal NAND...

I've now tried both options for the idbloader but both result in an un-bootable system from NAND.

I do get a warning that the driver cannot write to the idbloader area of the NAND, so maybe the request to write over the idbloader is not happening. Are there different types of NAND out there? and does the above image contain the required NAND drivers? (What I think is the NAND chip on my board is labelled 7MG22 NW814, but that doesn't give many results on google so I'm not 100% sure).

Also I'm using a recent Multitool build dated 6th Feb 2022 if that makes any difference. Is there a different approach i can try to write an image to internal NAND?

Any help would be welcome.

Barry

Hi again,

RE: WRT the Wi-fi & ssh issue...

I've spotted something odd, so it may not be completely router related. ( BTW - I use discreet wireless APs [TP-link EAP225] rather than the radio on my router. Unfortunately the beacon interval on the APs is not configurable)

If I boot up LE from SD card , without an Ethernet cable attached, inbound ssh doesn't work, but LE does connect to the wi-fi and I can see the network & internet etc.

However, if I now connect an Ethernet cable, even if it's just for a few seconds for the link to come up and acquire a DHCP address, I can now ssh onto LE via the WLAN address...

This suggests that something which occurs during the initialisation of the eth0 interface is fixing the issue with wlan0

Barry

Hi, I'm a complete newbie so please be patient...

I've been experimenting with the 20220329 LE 10 nightly build on my TV box booting from SD card, and it's been really stable, I'm really impressed with it, performance is so muhc better than Kodi on the Android 7.1 installation previously. Even the remote and wifi worked out of the box ( for some reason I cannot SSH into the box over wifi yet, but that may be and issue on my network tbh. possibly wireless isolation is on )

My TV box is branded as SMBOX SM1, but I've has a look inside and it looks like the R329Q v3.0 board seen in many of the others e.g. MXQ 4k

I'd like to burn the image to internal memory. I have a Multitool image on another SD card, which reports that the device is equipped with NAND, rather than eMMC

I backed up the Android image, then erased the flash using Multitool options 1 and 3. I then burned the LibreELEC-RK322x.arm-10.0-nightly-20220329-c3a59e9-rk322x.img.gz image file using Multitool (option 4 - skipping the idbloader area as recommended by Multitool) , which completes in about 45 seconds, but afterwards the device does not boot from the internal storage.

The .gz image was burned very quickly to the internal storage (when compared with a restore of the android image)... Do I need to unpack / ungzip the image before writing to NAND?

Restoring the original Android from backup was successful but took approximately 20 minutes.

Am I doing something wrong?

Thanks,

Barry