Jump to content

RaptorSDS

Members
  • Posts

    307
  • Joined

  • Last visited

Posts posted by RaptorSDS

  1. 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

     

     

     

     

  2. 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

  3. 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 ....

  4. 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)

     

     

  5. 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

  6. 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)

  7. vor einer Stunde schrieb Tiago Barsan:

    RTL8703BS

    that a little unusal chip but linux compatible

     

     normally 8703 is part of 8xxxu standart linux libary

    https://kernel.googlesource.com/pub/scm/linux/kernel/git/jes/linux/+/rtl8xxxu-8188eu/drivers/net/wireless/realtek/rtl8xxxu/rtl8xxxu.h  "line106 "

     

     

    but i found also some guys that have a driver at github for building yourself

    https://github.com/java-batista/rtl8723cs

  8. 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

     

     

  9. Hi N3O

     

    i think there a missunderstanding  both are right

    it depends on what you want

     

    the real first boot loader talk at 1.5M than the UART get change by the bootloader from NAND or SD card or android to 115200

     

    you only need to UART -> UART-USB-> USB of windowsPC or linux and a tool like Putty or Kitty

     

     

    you dont need connect UART back to box or male male cable for normal Logs

     

    the male male cable only for hard flash new bootloader or recovery with another PC with a rockchip tool

     

     

  10. hi

    eMCP is RAM and Flash on one Chip most time  , --> when you have only one big chip beside the CPU

     

    NAND and eMMC is more tricky but its look the first picture , with the not solder Area ist the place for NAND ( often the NAND ships have many pins on both oposide ends)

     

    to be really sure please look at the big ship below the AMS1117 power regulator

     

    some hint the 4 smaller chip are the RAM (on top and below board)

     

  11. @fangis do yo have link for a manual / instruction  for install JWM or Openbox+tint2

     

    i have not much experience when the desktop not already preinstall and preconfig at startup

     

    last time i install desktop without preinstall ( Dietpi and xfce ) all text and all symbol where missing . Thats was not a good experiance .

     

     

     

  12. vor 6 Stunden schrieb Arden King:

    rkconfig reports the it as 02e7:9086 and unknown

     

    thats a clone of realtek with name S9012P , i had also a box with a similar clone . Its close source and the Manufacture has no real linux driver

     

     

     

    my solution was reflow/resolder a realtek RTL8723 DS/BS from ali... 

     

    its pin and pin behavior compatible , but without a proper driver the AP S9012P is useless in linux

  13. vor 29 Minuten schrieb chakatun:

    Thanks for answering. I think that I have a board with NAND, and therefore I can only install the old kernel on it. Yesterday, during installation, I chose the place "Burn image to flash" and erased the bootloader))), I could not switch to maskrom mode, so I disassembled the prefix and closed the test point and restored the bootloader.

    How do I find out what type of memory is on my board?

    Here is a photo of my board
    And from the multitool menu.

     

    I would say EMCP

     

    because on left ro right i see wifi chip ; empty Memory chip space ; the Rk322x ;one Memory chip

     

    thats only one memory chip on upper right corner that maybe  EMCP (combined RAM and ROM chip) please look at this chip and google it 

     

     

  14. @Max Sterg there are two ways

     

    first way : put the linux image as compress file on the multitool

     

    or

     

    secound way: first boot multitool , than the partionion get resize to around 2 till 4 gig and than put the compress or unzip files on the multitool

     

     

    @chakatun

    i got something similar when i start armbian with nand option from rk322x-config tool --> than initram did not know where to start from but i have nand space

    or maybe you have one of the new emcp memory (RAM and ROM on same chip)  than its difficult to boot from internal space

     

  15. @jock @Max Sterg thats correct the first time the image only occupied some GigaByte , after first run is enlarge .

    But you you can also put , after burn the sd card , the images  as  a compressed file on it (tar.zx or something like that) the multitool can decompress this file on the fly ( at the moment this tool burn the image to the box)

    the one gig is enough for that desktop image

     

     

     

     

×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines