Jump to content


  • Posts

  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. is it possible to boot android from usb? when i flashed the image with sdboot tool 1.69 it boots up partially and fails in short of no eMMC... if i flash android to my 16gb usb thumbdrive and leave the micro sd card inserted so it can boot from usb.... android 9 is the first one i wanna try
  2. how do i get this to boot off a usb external hdd or thumbdrive ? do i just flash it to the usb hdd and plug it into the usb 2.0 port ? or the usb 3.0 Port? my emmc is cooked due to an error i made with the emmc clock ground button mod i did (i learned from that mistake and will improve the basic part of it.) but now the thing won't boot without a bootable sd card either in multitool (no eMMC = No Good...) but in armbian raw flashed to sd card, it boots up and begins the initial setup like username/etc... i tried before 5.15.2 to boot exclusively from a usb hdd and i had no luck even when the eMMC is empty or inaccessible (yet again boiling down to clock/gnd pcb track damage the pad separated from the pcb due to too much heat caused from a crappy soldering iron and a loose wire pulled the track and dot and now the eMMC is kaput unless there is a way to get it working again...Grrr...!) i've tried to get it to boot from the 2.0 port and nothing... i tried the 3.0 port and still nothing with the card or the hdd... i'm at a loss here.
  3. it appears that someone has made a method to install libreelec for 3318/3328 on an sd card simply write the img file from libreelec to a usb sd card reader then fire up vmware with ubuntu and mount the usb sd in vmware and have the trust.img on the vm and send the command as root dd if=trust.img of=/dev/sdb seek=24576 unmount ant shut down the vm, then edit /extlinux/extlinux.conf to point to rk3318-box.dtb then put the rk3318-box.dtb wherever you pointed the /extlinux/extlinux.conf file to. eject the usb sd adapter from windows. insert the sd card into the box and boot it up, it will resize the sd card to any remaining free space for libreelec use version 10.0.1 rk3328-arm a1 box and it mostly works except bt/wifi/led/ir, but everything else more or less works normally
  4. so it appears that the rk3318/rk3328 are more or less the same so it is a possibility to get lakka / libreelec to work use the os image with the trust file and correct dtb file and it should work pretty normal, but there needs to be more digging into the rk3318 trm and datasheet does anyone anywhere have the technical reference manual in its entirety? all i can find is the datasheet.... rk3318 Manual+dtb.7z
  5. can the verbosity level go higher than 10? if so then set it to the highest available. and now getting into MaskROM is easier if you solder on a push button to the emmc clock then anywhere on ground and use 2 wifi antennas pcba and solder the button to it and make sure that the button when pressed , makes connection and goes into MaskROM mode and all you need is 2 wires on the button and 1 wire on emmc clock and the other one on on ground and tape the button pcb with capton / polyamide adhesive tape so you don't short out the cpu otherwise it will halt and restart
  6. i'll check for other monitors with dvi-d. hope we can turn this into a full blown computer that supports nearly all hdmi / dvi-d displays basic resolutions 640x480 720x480 / 720x576 800x480 / 800x600 1024x600 / 1024x768 1152x864 1280x720 / 1280x768 / 1280x800 / 1280x960 / 1280x1024 1360x768 / 1366x768 1440x900 1600x900 / 1600x1200 1680x1050 1920x1080 / 1920x1200 2048x1536 and so on
  7. here is the edid dump for the monitor and so on edid.bin edid.txt L196WTQ.txt l196wtqbf.txt
  8. here is the inf file and service manual for the monitor L196WTQ-S_BFQ_E.pdf L196WTQ.inf
  9. does it fix the issue with dvi to hdmi on devices that don't support 1920x1080? in multitool the monitor worked but after flashing the emmc and rebooting the monitor went into power saving mode. the monitor is an lg L196WTQ-BF in android it was locking to 1280x1024
  10. what about using the emmc on the device instead of the sd card?
  11. it seems that the mali-450 gpu can be clocked at 750 MHz and the ram can be clocked to 1.066 GHz and the cpu can be clocked up to 1.512 GHz
  12. i used this in ubuntu wslg dtc -I dts -O dtb -f rk3318-box_1.5Ghz_SDCARD_v1b_ST_sdhr104.dts -o rk3318-box_1.5Ghz_SDCARD_v1b_ST_sdhr104.dtb and the thing threw warnings about missing phandle references and it compiled as you can see... it appears that the format syntax is as follows: the start of the settings uses a curled bracket without a semicolon and the end of that part has 2 line endings opp_table0 { compatible = "operating-points-v2"; opp-shared; phandle = <0x05>; opp-408000000 { opp-hz = <0x00 0x18519600>; opp-microvolt = <0xe7ef0>; clock-latency-ns = <0x9c40>; opp-suspend; }; opp-600000000 { opp-hz = <0x00 0x23c34600>; opp-microvolt = <0xe7ef0>; clock-latency-ns = <0x9c40>; }; opp-816000000 { opp-hz = <0x00 0x30a32c00>; opp-microvolt = <0xf4240>; clock-latency-ns = <0x9c40>; }; opp-1008000000 { opp-hz = <0x00 0x3c14dc00>; opp-microvolt = <0x10c8e0>; clock-latency-ns = <0x9c40>; }; opp-1200000000 { opp-hz = <0x00 0x47868c00>; opp-microvolt = <1200000>; clock-latency-ns = <0x9c40>; status = "okay"; }; opp-1296000000 { opp-hz = <0x00 0x4d3f6400>; opp-microvolt = <1225000>; clock-latency-ns = <0x9c40>; status = "okay"; }; opp-1392000000 { opp-hz = <0x00 0x52f83c00>; opp-microvolt = <1250000>; clock-latency-ns = <0x9c40>; status = "okay"; }; opp-1512000000 { opp-hz = <0x00 0x5a1f4a00>; opp-microvolt = <1350000>; clock-latency-ns = <0x9c40>; status = "okay"; }; }; rk3318-box_1.5Ghz_SDCARD_v1a_ST_sdhr104.dtb rk3318-box_1.5Ghz_SDCARD_v1b_ST_shr104.dtb rk3318-box_1.5Ghz_SDCARD_v1b_ST_sdhr104.dts log3318.txt
  13. all i did was edit the raw dts file in notepad++ but the 1.5GHz is broken but it is just a bad setting in the dts file. how exactly do you edit the dts file in windows? should i use nano in ubuntu-wslg?
  • Create New...