RaptorSDS
-
Posts
307 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by RaptorSDS
-
-
Zitat
The original dtb of your box may be helpful to understand if your board has particular settings or gpio configurations
i did not want back to android , the box works great with linux . is there a way to extract dtb from backup file ?
ZitatPhotos of the board are always welcome!
i attached the pic of the board
Spoiler
Spoiler
-
Hallo team
first thanks for the good work
i am now a long time active with balbes150 on the Amlogic S805/S812 forum side , but last week i bought two Rockchip box for small amount .
i am very happy for this good support on this box
my box Leelbox Q2 Pro RK3229 2gb ddr3 / 16GB emmc , Ap6255
but i have two problems
first is that both trigger of the rk322x-config tool ->emmc and nand are stop the initramfs script to boot the box i always get stuck that the uuid of emmc is missing or incorrect ,
without the emmc or nand config the box works great !!!!
secound the high idle temperature of the box , i have long time a M8S Box with a Amlogic S812 and the idle temp is around 30-35 celcius , this rockchip box are idle at around 55-60 celcius , some load and the box hit the 75 celcius and shut down ( also the other rockchip box with rk3328 idle around 55 celcius on android) is that normal or do i have a faulty chip ?
both problem on latest buster minimal 20.04 kernel 5.10 and bionic desktop 20.04 kernel 5.10 rom
i dont use the lagecy kernel 4.4 rom because i didnt not get wifi running
-
-
@Ruf73 Please do not use the android dtb for Linux , there are compatible but not all work proper.
on the sd-card there should be also a m8m2_n200_2G_sdio.dtb please use the files from SD-card ( but you wrote the box is a M8 S802 , but m8m2_n200 is more like a m8s S812 box , wifi is a broadcom modul )
-
Thank you for being a little more detailed this time
for 5.44 and 5.77 both use the 3.10 kernel which is identical to the Android 4.4 kernel so there are many boxes running with the default settings
that 5.44 only runs with HDMI and with less memory is due to the fact that not exactly all settings are workingafter flashing the SD_card should have 2 partitions 1. boot 2.Linux
in the 1. partition Boot files must be changed depending on the version as follows:for 5.44 and 5.77 you have to change the dtb.img file on the SD Card after flashing with the correct file from the subfolder
this must be copied and renamed as dtb.img in the main directory of the boot partition.for 20.xx images, due to the new kernel, only the link in the file uENV.txt is changed to the correct file in the subfolder of the boot partition of the SD card.
! some boxes always need a HDMI cable ;! the dtb file tells the kernel what , how , and where is available in the box
but also the kernel and the Linux must also be able to handle it
therefore it is not possible to move a working dtb file from 5.77 to 20.xx. -
First there is no A to Z guide how to make this android to linux box , because there are many diffirence between the box . feel free to write one
Download link to the Armbian version I need to try and dtbs I should attempt to use?
somewhere in this thread armbian.com/linux/balbes ( last 3 pages)
How to boot from the SD card (I assume this is the tooth pick method)?
toothpick is only to get to recovery partition / recovery tool
you also have to find a way to install the aml_autoscript , this script activte the multiboot option on bootloader for usb and sd-card boot
( i had to sideload TWRP from sd-card to temporary recovery and than replace recovery with twrp, install the aml_autoscript and also root the box)
Where to solder a uart bridge (I'm using my bus pirate for this) for uart?
look at the lower section on your picture. Are there the mark for RX;TX and GND ? maybe look at the other side of the board ! ; What is a bus pirate ? you need a uart rs232 to usb ( be aware you need maybe 3,3V UART adapter ) that enough,
dtb
there are some in the armbian boot section for testing , there is also a mxii.dtb
-
@menelike i look at the dts file for 5.xx kernel and see many i2c channels are state disable but rtc is still enable , i think that system try to reach the rtc but without i2c is like disconnect ,
@SteeMan i think the problem is more that some vendor have sometime change where thinks connected rtc somtimes on i2c_AO sometimes on i2c_A ;
and that many thinks are still diable in the mainline kernel dts files because the dev didn have time or have not hardware to test all ,
-
from where do you have the dts file for 5.10 Kernel ? what happen if you also disable RTC clock , its also possible thats i2c problem because pcf8563 has i2c interface
for GPU is normal to have no reserve memory because strucktur of dts / dtso are now
--> kernel / main chipset/ chipset / devices
like my my m8s
-->kernel 5.xx / meson.dts / menson8.dts / menso8m2_m8s.dtso
the reserve memory can also be descripte in menson.dts
-
on all USB Ports ? do you use Wifi ? or Ethernet , do have any tmp or swap file configure on SD card ?
-
vor einer Stunde schrieb g00n:
Hey, I have an old ARMADA MACH 8 / Amlogic S802 box, how do I flash ARMBIAN on it?
first active multiboot ( maybe root or change of recovery image need)
next write image on sd-card
next chose dtb files maybe you have search/test for right one
boot the image from sdcard
-
vor 3 Stunden schrieb voron:
Amlogic S805
Please upload the link to the working Armbian with the driver rtl8723bs ? Help !
all image the old armbian 5.xx with 3.xx Kernel and also the many(all 20.1x) new image 20.xx with 5.xx have the rtl8723bs driver inside , but the different kind of the S8xx chipset and s9xx chipset box make it hard to have the right pin for the right board with the right wififchip ( some information the s812 has 3 different wifi chips ap6330 rtl8723bs and a third one = hard to tell wich M8S label box has wich wifi chip )
next think is that the dtb ( that is the files that descripte the box) has change from 3.xx kernel to 5.xx kernel because 5.xx kernel are useable for a wide area of devices (some Information the 3.xx kernel dtb file has possible to set 3 state (high, low ...) of a pin the new kernel i thing 5 state ( high , low , low activ, high activ ....) )
so we need more information about your box ( we have S805 +rt8723bs
like : wich old kernel work with wifi , wich pin is for wifi enable from old 3.xx kernel dtb , wich dtb from 5.xx kernel work now and so on
-
@obaldon1 its very bad to lose someone with sysadmin and devolpment experince , yes Android root , fastboot and sideload is really mix of documents and also this thread is more mix with problems , weak solutions and links and not that one document from a over b to c
i mean a usb rsr232 debug connection , or i think it was possible with android usb debug mode ( Devolper menu) that one usb port was maybe also a adb-port in android or 3e-recovery then you can sideload a recovery.img from PC temporary and than from this to flash the zip buts its long ago ( 4 years now that done this to my box ) normaly i work with android phones
-
@AzuriAdore looks like timing problem at init at boot ( maybe usb host did not get right shutdown) thats why somethig thinks get deactivate with newer kernel first and than after test and beta back online
thanks for a guide for docker
@obaldon1sorry to hear that you frustrated , my first device for flash was a windows CE->XDA 1 , there is no step by step instruction because every android device is diifferent some have more secure features like software fuse and secure bootloader other have only non root user , but like azuriadore say you learn something in the 30h.
please dont waste your box ,
also please notice this is still a hack of a device someparts are still beta and not stable ,
also please notice this is not a windows device where your put your usb stick and one-click installer say hello i am windows installer , many things are still by adb-console and input commands into a black window
do you have a pc connection to your device ?
-
@obaldon1
read about sideload and fastboot over adb in Android Debug USB or 3e Reovery , get TWRP Running and install aml_script.zip from TWRP , maybe root your android
!! and please do not brick your box !!
-
Andorid has follow file system
1.Boot Loader (uBoot System)
2.Recovery ( 3e or TWRP or...)
3.Backup SystemFiles (backup of android 4.4)
4Android SystemFiles ( andoid 4.4)
toothpick -> most box have behind analog Video(Chinch) or Audio Port a push button to get into Emergency recovery mode ( you found it already)
Team Win Recovery Project ( TWRP) is a alternate Recovery for Android .
most 3e Recovery system have also adb/fastboot ( or in android USB Debug Mode) its like a special Serial Console to speak direkt to the Kernel/3e System files
adb->android debug bridge , fastboot is part of adb to flash boot or recovery img to file system
-
maybe this help
1. root the box or/and install TWRP -> toothpick methode
1.1 maybe get debug output from serial port at board ( !!! soldering !!, but its help a lot , Serial Console TTY)
2. activate Multiboot with aml_xx.zip for uboot bootloader at TWRP ,
3.use old or new Image
3.1 old image befor 5.xx Kernel take the right dtp from dtb folder to boot folder and rename to dtb.img ( Android 4.4 dtb files are more in common to Kernel 3.10.xxx dtb files )
3.2 new image 5.xx Kernel edit uEnv.txt and point to right dtb file
4 repeat step 3 with other dtb files if not boot ( !!! dtb from 3.10.xx not working with 5.xx Kernel)
5 if something not working like eth or wlan remeber its beta or work in progress maybe to study to edit dts files help
@balbes150please PM me if something missing i edit this post
-
thats because manything thange in the dtb files over the year -> dtb for 3.10.99 kernel was direct usable from android 4.4 ; ->dtb for 5.8 kernel many things are disable by default because of compatibili settings or get new interpreted ( i have the Realtek 23bs chip and in the old dtb it was a chip enable high in the new kernel i need a chip enable low)
secound there are no nand install ( because of unknow uboot settings for new kernel to boot from nand; risk to brick the box is to high ) most of use use only sdcard or usb , i know that "xdarklight" has testet the nand driver in the 5.8 kernel but its still beta
@obaldon1 thats correct u have to use the right dtb file in the uenv.txt ( normally when u use wrong dtb u should only the black scrren or color screen and not android boot when multiboot works )
-
4 hours ago, brunog said:
@RaptorSDS thank you for your help. Ive got it running with 20200523 from the meagadrive site and meson8b-ec100.dtb. No other dbs worked accept odroidc1 which crashed. The device running with meson8b-ec100.dtb seems stable for the most part but crashed a few times installing with apt-get. I will provide serial console logs when i get time if you want them.
another problem is that the display output over hdmi doesnt fit the screen and lines are cut off from all sides. I attached picture of this. you will see that zram config also failed .
if there is anything i can do to fix these issues please point me in the right direction and everyone thank you for your hard work.
on my samsung UE37Eh5200 it was wrong setting from tv , under display->fit display -> there a mode like 16:9 4:3 ,auto,wide screen , and smart screen . after switchen from auto to smart screen its fit back to screen , looks like same error on pic
-
26 minutes ago, s812us said:
@balbes150 thank you for answering, appreciate it!
@RaptorSDS I get "out of range" signal on my monitor but i can see the picture just fine (it gives an "out of range" signal every few seconds but i can see the console just fine) is there a way to solve it? im using HDMI on a 4K monitor.
For anyone interested I have an M8s+ device with S812/2G ram/8G emmc/1G ethernet, on the board it says S812_M8_Rev1.1 dated 2015/05/21 & the default DTB in balbes150 latest armbian images (meson8m2-mxiii-plus.dtb) works fine but no emmc detected - I tried extracting dtb from the box android 5.1.1 but it doesnt work...
I also have a mecool m8s+ pro with s905x which works out of the box with the images but unfortunately ethernet is only 100 even though its newer...
maybe its better to test with meson8m2-m8s.dtb (its more in common on your specs) , the linux kernel can only 1 device per controller at the moment ,so wen can have SD-Card+wifi or sd-card+NAND( the NAND u-boot does not support new Kernel )
also like i said above dtb from Kernel(also recompile) 3.xx.xx thats android 4 ,5 and 6 do not work on kernel 5 because of different system names and function
-
@brunog do you test also the lastes 20200523 from meagadrive site ? , please after 4.20.0 ( also all NEXT) Kernel only do the uEnv.ini edit thing , please do not copy and rename dtb.img
without a serial console log file we cannot see why your kernel stop please use the uart interface , like @elbuit use the meson8b_mxq.dtb in uEnv.ini and please stay calm
@ everyone that use the 5.6 and newer rom files please conisder that first boot take up to 5-10 minute because image automaticly reszise to complete SD-card also HDMI works only with multi mode TV ( because image switch between 1080p30(boot) 1080p60(Kernel load ) )
@elbuit looks like your box use same pins for bluetooth and Wifi . i hhave also some warnings but 5.7 kernel still beta , all image have hdmi output (also non desktop ) but desktop will start after root login and create new user boot to lightdm desktop envoirment , your tv get the hdmi information but "out of range" mean that reslution or refresh rate do not match ( my tv has all 720p25 to 1080p60 possible format ; and switching 3 time the mode when boot box)
-
@elbuit nice thanks for that hard work
dtb-> you can not use 3.10 dtb also not recompile version for 5.x image because 5.x has many different names for functions and systems .
pleasae can you attached your decompile dtb ( your dts file) maybe we can you use same wlan power pin like m8s box
there was somebody in this thread ( maybe from last year ) that already test to run docker but there was no new infos maybe you can contact him
monitor i think its because kernel do not support menson8b video chip at the moment (or like the wlan do not have the right information), we get last month the menson8m2 (mali450-chip) working .
-
@balbes150 some feedback
1. after screensaver goes active (switch screen black/ off) and back to destktop (wakeup) screen still has rosa overlay
2. bluetooth are on rfkill but i got a two error first: rfkill has bluetooth with softblock ,secound after unblock i got error FW rtl_bt/r8723bs_fw.bin not found ( inside /usr/lib/firmware/rtl_bt/ only r8723b_fw.bin inside ) after rename files bluetooth work ( discover able and connect able )
also add to /etc/modprobe/r8723bs.conf the line rtw_btcoex_enable=1
-
@elbuit nice to see that you get a linux on your box , first do use the desktop image ? secound this linux version kernel 5.xx are beta version ,also the mwson8b-mxq.dtb file do not start your wlan because still some information for wlan missing inside the dtb ,please can start android and look at serial terminal for wlan pin, irq and clk infos (GPIOX_10 or pin-166 or something)
-
i found the clue today and also martin got the infos today ( the r8723 has a 3 state Wlan_disable pin / low -> sdio on wlan off , open-> sdio off , high -> sdio on wlan on )
CSC Armbian for RK322x TV box boards
in Rockchip CPU Boxes
Posted
@fabiobassa thanks for fast answer , i know some tools from amlogic when android still at internal memoryy ->read boot partition , extract file , convert dtb to dts . but i have no instruction for read boot partition from a image ( and no i have no orginal image leelbox-tech.com is only a placeholder) , i have also no clou how read that from backup file
my infrared thermo meter say also around 45-50 degree , also my finger say it get warm