RaptorSDS
-
Posts
270 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by RaptorSDS
-
-
vor 1 Stunde schrieb n3o:
ok, the 2 bootloader here https://github.com/ilmich/rkflashtool/tree/master/bin do You know of what type are?
no but ilmich would post close ones , so i thing there will be open ones , but simple first if you havent problem with legacy armbian please dont do step 10 infront of step 1
vor 1 Stunde schrieb n3o:bullseye and jammy
bullseye debian 11
jammy ubuntu 22.04
vor 1 Stunde schrieb n3o:think it's bettere install legacy armbian to nand, and only after this flash armbian newest to sd (I think it's possible boot system directly from sd without install , true?)
yes you can nand first , yes correct sd card direct without install when bootloader 1 else you maybe need "jump start" from multitool
-
vor 16 Stunden schrieb n3o:
I want install the most recent image of armbian with gui (so I don't want android) and in first post is written that it's necessary update bootloader "For fearless and bold people who are having issues when (re)booting images, there is the chance to upgrade the bootloader on NAND".
Yes correct --> NAND install = legacy armbian
but you can boot latest Armbian from SD card or USB and ignore NAND complete
Bootloader update only possible with male - male USB cable and rktool outside of the box
there are 3 bootloader
1. open ones , SD-Card , USB and NAND boot allow , boot SD-CARD/USB also if there a OS in NAND or install Armbian legacy to nand
2. open ones , SD-Card USB Boot NAND boot allow but boot NAND first , there you can try the new point in Multitool "Jump start " that always redirect boot to SD-Card or install Armbian legacy to nand
3 close ones (rare ones), that the ones with probleme where you have to update bootloader
Please !!! do the simple steps first , simple install legacy to nand and try it --> flash multitool on SD-card , put image file in the folder , start multitool , save android , clean nand and install(flash) armbian to nand
or flash image file on sd-card and boot armbian legacy or newest
vor 16 Stunden schrieb n3o:ok, where I can find this file (and how to reach destination if android no more boot)?
we do need them only when all other failed , RK322x have some already inside armbian , many work with many diffirent setups and hardware already no need to do 10 step ahead
please simple first !!!!
please dont do this 10 steps ahead , i only want to say make a backup of android its good to have one also if corrupt .
-
please guys dont mix topix
thanks @ego worker for post link
@n3o
vor 19 Stunden schrieb n3o:t's possible use only legacy kernel?
that why i was wonder , kernel is a part of linux but some like Android sometime have that as a seperate partion or like rasberry you can update kernel only
also you talk about bootloader upgrade and i am was confuse about what you want and your knowloge about flashing this box with linux
vor 1 Stunde schrieb n3o:you mean load android image? what are dts/dtb ?
no save android
dts/dtb are config file for kernel--> tell kernel where to look at for lan or wich memory or clock to use for hdmi and so on
i thinks easy step are on page 1 when your box is nand than follow the step with a legacy armbian image and have fun with this box
-
vor 29 Minuten schrieb n3o:
it's possible use only legacy kernel?
i can not hep by flash any other bootloader or make nand work with newer kernel , i dont understand why only kernel that make no sense , flash legay armbian and go on with the box , else put legacy image on the box and than show the log
we can look why maybe the box dont boot full to armbian
you can save also android because maybe we need dts/dtb or anything else and extract it out of image file
-
vor 2 Minuten schrieb n3o:
it's not SSH
its better its a serial console , you can interact with linux over tty Serial connect (you have with this now with UART) , when multitool is running like in a ssh session
ssh is a forwarde serial console over ip (more or less)
when you run headless ( without gui) linux do the same a serial console is than also forwarde to HDMI (more or less)
vor 5 Minuten schrieb n3o:what do You recommend me?
both have same source , both use same tools and programm
Debian has philosophy "no close source" but your are able to install them when need
Ubuntu is from start with close source software but that makes its sometime bigger and more complex
both can use xcfe and other gui ( some of the image files already have xfce active) , when you only need server go with minimal
-
vor 59 Minuten schrieb n3o:
bookworm and jammy
bookworm is Debian 12
jammy is Ubuntu 22.04
-
vor 30 Minuten schrieb n3o:
ok, I want install armbian but also multiboot doesn't worked very well
but now you can see why it is not work , and also interact with armbian without HDMI if HDMI doesnt work
-
vor 18 Stunden schrieb n3o:
[ 8.215212] init: property_set("ro.hardware", "rk30board") failed
[ 8.223761] init: Running restorecon...
[ 8.288108] vendor storage:20160801 ret = -1
[ 8.312205] init: waitpid failed: No child processes
[ 8.313478] init: property_set("ro.board.platform", "rk322x") failedlooks like android has many false setting or broke
-
vor 26 Minuten schrieb YanCorote:
No, this screen was after completing the installation in multitool and turning it off. Pulled out the power cable and sd card and started again.
Yes, it is NAND, RK3329
witch version do you want to install to nand ? newer Kernel can not work with nand there are many problems
do you clean the nand befor flash armbian ?
i got this screen every time after rk322x-config set in ENv.txt the parameter nand or nand-emmc , i have to remove it that only standart setting are load
-
vor 19 Minuten schrieb YanCorote:
on the first boot the screen shows it:
ohave you done rk322x-config befor this happen?
do you boot from sd-card or internal , do you sure about nand memory ?
-
vor 15 Stunden schrieb TU-Student:
Does anyone have a tip?
looks like one of the new eMCP chip ( combination of emmc and ram ) it is working sometimes but you may be get problems
https://de.ifixit.com/Teardown/Teardown+des+MacBook+Pro+13-Inch+mit+Funktionstasten+Ende+2016/72415
there is also meantion the wifi chip set Universal Scientific Industrial 339S025 Wi-Fi Modul --> first time i see something in a box
like jock said some issue befor this box are made of the cheapest crap that they can finde and put that together
-
vor 4 Stunden schrieb mydeardiary:
Here is the photo of wifi chip.
thank you ,
i also found also lwfinger https://github.com/lwfinger/rtl8723au there are also some AS mention
also some fork but kernel 4.4 https://github.com/instantaphex/rtl8723as/tree/master
-
vor 1 Stunde schrieb mydeardiary:
Tried patching the kernel to add the device id to r8723bs
But RTL8723as is not 8723bs , you should not mix them .
8723as has definitive a diffirent firmware than bs https://kernel.googlesource.com/pub/scm/linux/kernel/git/jes/linux/+/rtl8xxxu-8188eu/drivers/net/wireless/realtek/rtl8xxxu/rtl8xxxu.h
many of the RTL 8723xx are part of Kernel 5 , it should be detect by linux automaticly with the right firmware/driver combination
have you check the chip by open the box ? maybe its a 8723ds (bs and ds have same format and pinout ) ,8723as has a diffirent board format so its very unusal that this board have another print extra for this 8723as format
-
vor 2 Minuten schrieb Wonder Xyril:
allwinner h313. can i still install it?
now you have your answer thats not working because not compatible anyway
-
vor 1 Stunde schrieb Wonder Xyril:
amlogic, but in reality it is RK322x
how do you know , do you open the box and remove the heatsink ? , maybe after all really a AmLogic maybe?
we seen like sell as amlogic , print on die as rockchip and after all allwinner chip or stupid things like sell as rockchip print as amlogic and really is rockchip older model
please show and tell us more
-
vor 4 Stunden schrieb Wonder Xyril:
compatibility issues,
Let's look into the crystal ball, I see something, it could be that something is not right here and someone has problems with a rk322x box. hope you understand this little fun, it would be of course especially with such a time pressure of only a week surprising if we could really solve your problem with such a crystal ball, so let's start here. Describe your box in more detail, which multitool which problem from which point, why this solution not something else and much much more ....
-
Am 27.4.2023 um 21:20 schrieb mr. madness:
6051p network card.
sorry for late answer
you have to try some LED-Config ( better name GPIO Config) settings inside rk322x-config tool and always reboot after every change,
it should be support by kernel 5.x , else you can try legacy image ( with kernel 3.xx)
-
vor 2 Stunden schrieb fabiobassa:
Armbian env doesn't change anything.
Thank You , ok switching things by adding a part of it
-
vor 5 Stunden schrieb jock:
The question is absolutely relevant and very welcome.
The answer is quite simple although: for historic reasons, those overlays are called led-conf but actually, during time and studies on the boards, they should be more properly called gpio configs or board configs: they deal with the peculiarities of the specific boards and integrate the "base" device tree.
Thank you ok understandable
vor 5 Stunden schrieb jock:The led-conf dtbs overlays don't necessarily carry the information about the wlan chip: the boards are designed to host several different wifi chips and the wifi chips are in turn designed to be "drop in replaceable".
Wifi chips exchange data with the SoC via SDIO bus, but also have other pins for other essential purposes (power, reference clock, antennas, etc...). One of these pins is the enable pin.
The enable pin turn on and off the wifi chip. It is like a button, which is in turn connected to a SoC GPIO pin that can be controlled by the software: the linux kernel can turn on and off this pin which will turn on and off the wifi chip.
The problem is very simple: most boards use the same SoC GPIO pin to control the enable pin of the chip, but some others use another one, or swap its polarity. You need to tell the kernel which GPIO pin is the right one, otherwise the kernel just can't turn the wifi chip on and, in fact, the wlan0 device does not even appear to the system. The GPIO pin for this functionality is specific to the board design, hence it is described in the led-conf overlay.
As an example, the boards with T066 marking needs such treatment (led-conf4, see here), but also other boards require it (I count at least three different configurations in those overlays, plus the base one).
Using the right led-conf is usually enough to get the wireless appear and work, because the kernel can turn on the wifi chip, poke the SDIO bus for the device id and load the right driver.
In some other cases, there is the need for a supplementary dtb overlay to get full functionality for the wifi chip: rtl8723cs/rtl8703bs is right the case to get also the bluetooth working, because it requires some other bits for complete configuration.
wifi enable and GPIO state is clear for me also the SDIO part , i done some testing with Martin Blumestangl (xdarklight) on AMlogic 805 (nand and he help me with wifi enable , had a rtl8723bs with inverted signial) , but its not clear how a armbianENV can change /switch dtb things
vor 6 Stunden schrieb jock:Normally the rk322x-config script deal with this automatically. You may need to run it a second time after reboot to complete the configuration though, in case in the first run it was unable to detect the wifi/bluetooth chip.
ok that was new for me that script do autodetect and that after config you have do start again the config sometimes
-
vor 10 Stunden schrieb jock:
right led-conf from rk322x-config
I have a more educational question , if the answer is too long or not appropriate please also PM me
What does the right led-conf from rk322x-config have to do with the wlan chipset pins and why can't we separate them from the LED config ? How can the DTB be changed through the armbianENV.txt or must all information be present and these options are just a switch ?
Can you maybe add in the rk322x config some information about the LED config so that we have a clue which wlan chip is activated (maybe an additional information page in the tool) ?
Translated with www.DeepL.com/Translator (free version)
-
vor einer Stunde schrieb Tiago Barsan:
RTL8703BS
that a little unusal chip but linux compatible
normally 8703 is part of 8xxxu standart linux libary
but i found also some guys that have a driver at github for building yourself
-
vor einer Stunde schrieb Tiago Barsan:
I have a T95D
it looks like you already open your box , please send also the Wifi chip code .
Maybe your wifi chip is not support by linux
-
vor 14 Stunden schrieb rafaeldavid:
I have no idea how to change that! Hehehe
inside linux
goto /boot
open with nano or other editor armbianEnv.txt
add the new line cpu-stability
save and reboot
-
vor 13 Stunden schrieb n3o:
Hi, I don't know if Android still boot (last time it was in recovery mode). However, the logs showed on terminal app are the same of logs asked by @jock?
@RaptorSDS the difference between stock boot loader speed and new bootloader speed is written here
yes red are UART
please use 3,3V on you ch341 adapter
rx tx should be cross --> , tx form usb to rx from board , and rx from usb to tx from board , GND to GND
you can not break anything with change of Baud rate , try both and you are fine
the text that run automaticlly on UART is the serial log ,
when nothing or only some unreadable thing is show in putty please change baudrate
than copy the text from putty or other tool and post here for jock ,
also ANdroid will produce a log on UART ( with some diffirence)
many of this serial log also in android terminal demsg log
i dont know the usb port order , for multitool over USB the port is normally irrelevant ,some box need normal USB , some the USB otg , some box hasnt the usb otg
CSC Armbian for RK322x TV box boards
in Rockchip CPU Boxes
Posted
Have you tried with SD-Card insert and manuall by press recovery button with tootbrush (trough audio port) --> than switch to bootloader or maybe sd-card boot direct
the box has to have the sd-card already in slot to read it ID and some other stuff when bootloader has to read from it
when boot first to recovery without SD-card than maybe some information missing (for the bootloader)