Jump to content

RaptorSDS

Members
  • Posts

    191
  • Joined

  • Last visited

Posts posted by RaptorSDS

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

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

     

     

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

     

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

     

     

     

     

  5. vor 7 Minuten schrieb fukowaka:

    think there isnt server options for this board yet, remember that we are installing unofficial versions . Check @jock versions.
    You need dts file especifically for your hardware

    your wrong the minimal are the headless variant = that is server like

    also the dtb is very compatible to all rk322x board , you can use the rk322x-config in bash  for your special hardware after first start ( like nand and emmc or ddr2 or ddr3 )

  6. Hello Group

     

    some month ago i bought a secound rk3229 box but with a stupid SV9082c wifi chip that is not supported by linux

     

    i finally get hands on a rtl8723bs chip from china and succesfully swap the wifi modul . But the the china store mislabel the product and i got a rtl8723ds .

    fortunately IWFINGER had a driver for this and i succesful build the kernel module and wifi now works .

     

    is it possible to insert/activate the rtl8723ds driver in next build of rk322x ?

     

    for the kernel module i had to Update the box there i got a message that some driver missing please can you check that @jock

    Spoiler

    IMG20220722092854_1.thumb.jpg.299e9ef534a79111fc18a783c95775e9.jpg

     

     

  7. vor einer Stunde schrieb greenais:

    download these old S805 images from?

    look at this thread somewhere are the yandisk link

     

    normally nand install was not possible because no nand driver in the old builds, impressive if you did it

     

    why not test the new image with 5.xx kernel also RTL8189 should maybe now work

     

     

    --> which Android One (11.x 9.x 8.x...) ? Never saw someone do this because android 4.4 was last build for S805 , this why android one had no driver for this box

  8. vor 8 Stunden schrieb ArtSHIM:

    There is an error even if I don't fix the file and just do a two-way conversion.

    your secound dtc string is wrong from dts to dtb

    -I = input type you have dtb should  dts

    -O = output type you have dts should dtb

    -o = output file = ok

     

    also odroid use realtek LAN but many HDMI CRC and HDMI i2c

    ODROID C1 source file

    mxq use internal(amlogic) LAN and standart HDMI output

    MXQ source file

     

     

    i thing your box need also the HDMI Communication CRC and i2c pins to work

     

     

  9. vor einer Stunde schrieb 심승보:

    SD Card Write Armbian_21.02.0-trunk_Aml-s812_bullseye_current_5.10.0_.img and meson8b-mxq.dtb, the network works, but the screen does not appear.
    (At Armbian_5.67_Aml-s805_Debian_stretch_default_3.10.108_desktop_20181207.img & meson8b-mxq.dtb,  Display screen on.)

     

    How about other dtb files from armbian 21.02.0 any other with display , its more easy to look at dtb files from same Kernel.

     

    dtb files from 3.10.0 to 5.10 are more difference -->that why there are not compatible .

     

     

  10. vor 1 Stunde schrieb jock:

    Never heard about sv6030P and never saw any driver for it. It looks very similar so ssv6051p, but can't say what kind of support it has.

    ok thank you , looks also bad supported --> ssv6051p is maybe a big brother of 6030p i found some coreElec information and some datasheet from icomm  (iottech)

     

    Zitat

    CoreELEC 9.2.14 changelog

    Updated Wifi driver ssv6xxx-aml

    Implemented Wifi driver SSV6030P

     

    they force ssv6051p driver for 6030p 

     

    Question is the SSV6051p and the patch also inside the rk322x images

    ssv6xxx-aml-003-force-SSV6051P-when-SSV6030P-is-detected.patch

  11. vor 7 Stunden schrieb Rohaaq:

    What else could I be missing?

    this is still a beta for this tv-box.

     

    yes when boot from sd-card you should edit uEnv.txt with right dtb file,

    but it could happen that none of the dtb work.

    if this happen, than please try one of the older Armbian S812 Version 5.xx with Kernel 3.10.xxx there is a higher chance that one dtb is correct for your box.

     

    be aware the dtb files not changeable between 5.xx Kernel and 3.10.xx Kernel

     

  12. vor einer Stunde schrieb Rohaaq:

    I see. But how exactly can I resolve these errors then?

    what do you see ? what do mean resolve error ?

    you do not need toothpick , you do not need recovery , only insert SD-Card and start the box

     

    befor patch

    bootloader-->internal memory-->android

     

    after patch

    without sd-card

    bootloader-->sd-card-->usb-->internal memory-->android

    or with sd-card

    bootloader-->sdcard-->debian

  13. vor 1 Stunde schrieb Rohaaq:

    The APK worked really well and I was able to enable multi-boot, and without root. I suppose in the future if using the stock app isn't an option for some user, using this APK would be useful suggestion. Much appreciated.

     

    However, I now get the following error in recovery mode:

    (stvm8b is the name of the board)

    E: Bad bootloader arguments "(null)"
    Finding update package...
    
    Start to check secure update...
    stvm8b board is encrypted
    not find bootloader.img in upgrade pachage. skipping...
    not find boot.img in upgrade package. skipping...
    not find recovery.img in upgrade package. skipping...
    Check secure upgrade package pass!
    
    Opening update package...
    Verifying update package...
    E: footer is wrong
    E: signature verification failed
    Installation aborted.

    Some Googling suggests that I might have to chose a different .xz file (in my case, a different one from this Yandesk directory), or something about my setup of the SD card is wrong. Is that correct? If the latter, what exactly am I missing other than changing the first line of the uEnv.txt to point to a specific DTB file?

     

    Thanks

    you are still in Recovery Menu not multiboot

     

     

     

    it should be more like this

     

     

    Boot from SD:
    --------------
    
    exit_reason:0x06
    set vddee to 0x03e8mv
    Enter ddr resume
    pub training time: 2630
    ddr resume done
    store restore gp0 pll
    cfg15 3b0d000 
    cfg15 63b0d000 
    GXBB:BL1:08dafd:0a8993;FEAT:EDFC318C;POC:3;RCY:0;EMMC:0;READ:0;CHK:0;
    no sdio debug board detected 
    TE: 71706
    
    BL2 Built : 12:06:06, Jun 13 2016. 
    gxb g176ecdb - laiyin.mo@droid12-sz
    

     

     

     

×
×
  • Create New...