marshall

Members
  • Posts

    8
  • Joined

  • Last visited

Recent Profile Visitors

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

marshall's Achievements

  1. Thanks for the reply, Here's the output: [ 2.912601] dwmmc_rockchip 30000000.dwmmc: IDMAC supports 32-bit address mode. [ 2.912760] dwmmc_rockchip 30000000.dwmmc: Using internal DMA controller. [ 2.912778] dwmmc_rockchip 30000000.dwmmc: Version ID is 270a [ 2.912851] dwmmc_rockchip 30000000.dwmmc: DW MMC controller at irq 45,32 bit host data width,256 deep fifo [ 2.912910] dwmmc_rockchip 30000000.dwmmc: No vmmc regulator found [ 2.912920] dwmmc_rockchip 30000000.dwmmc: No vqmmc regulator found [ 2.912942] dwmmc_rockchip 30000000.dwmmc: GPIO lookup for consumer cd [ 2.912951] dwmmc_rockchip 30000000.dwmmc: using device tree for GPIO lookup [ 2.912982] of_get_named_gpiod_flags: parsed 'cd-gpios' property of node '/dwmmc@30000000[0]' - status (0) [ 2.913033] dwmmc_rockchip 30000000.dwmmc: Got CD GPIO [ 2.913044] dwmmc_rockchip 30000000.dwmmc: GPIO lookup for consumer wp [ 2.913052] dwmmc_rockchip 30000000.dwmmc: using device tree for GPIO lookup [ 2.913062] of_get_named_gpiod_flags: can't parse 'wp-gpios' property of node '/dwmmc@30000000[0]' [ 2.913070] of_get_named_gpiod_flags: can't parse 'wp-gpio' property of node '/dwmmc@30000000[0]' [ 2.913079] dwmmc_rockchip 30000000.dwmmc: using lookup tables for GPIO lookup [ 2.913088] dwmmc_rockchip 30000000.dwmmc: lookup for GPIO wp failed [ 2.925921] mmc_host mmc0: Bus speed (slot 0) = 400000Hz (slot req 400000Hz, actual 400000HZ div = 0) [ 2.938821] dwmmc_rockchip 30000000.dwmmc: 1 slots initialized [ 2.939319] dwmmc_rockchip 30010000.dwmmc: num-slots property not found, assuming 1 slot is available [ 2.939415] dwmmc_rockchip 30010000.dwmmc: IDMAC supports 32-bit address mode. [ 2.939514] dwmmc_rockchip 30010000.dwmmc: Using internal DMA controller. [ 2.939533] dwmmc_rockchip 30010000.dwmmc: Version ID is 270a [ 2.939595] dwmmc_rockchip 30010000.dwmmc: DW MMC controller at irq 46,32 bit host data width,256 deep fifo [ 2.939654] dwmmc_rockchip 30010000.dwmmc: No vmmc regulator found [ 2.939663] dwmmc_rockchip 30010000.dwmmc: No vqmmc regulator found [ 2.939683] dwmmc_rockchip 30010000.dwmmc: GPIO lookup for consumer wp [ 2.939693] dwmmc_rockchip 30010000.dwmmc: using device tree for GPIO lookup [ 2.939704] of_get_named_gpiod_flags: can't parse 'wp-gpios' property of node '/dwmmc@30010000[0]' [ 2.939714] of_get_named_gpiod_flags: can't parse 'wp-gpio' property of node '/dwmmc@30010000[0]' [ 2.939722] dwmmc_rockchip 30010000.dwmmc: using lookup tables for GPIO lookup [ 2.939732] dwmmc_rockchip 30010000.dwmmc: lookup for GPIO wp failed [ 2.939814] dwmmc_rockchip 30010000.dwmmc: allocated mmc-pwrseq [ 2.952648] mmc_host mmc1: Bus speed (slot 0) = 976562Hz (slot req 400000Hz, actual 244140HZ div = 2) [ 2.963464] dwmmc_rockchip 30010000.dwmmc: 1 slots initialized [ 2.973996] mmc0: Problem switching card into high-speed mode! [ 2.974106] mmc_host mmc0: Bus speed (slot 0) = 25000000Hz (slot req 25000000Hz, actual 25000000HZ div = 0) [ 2.974229] mmc0: new SDHC card at address 0001 [ 2.976074] mmcblk0: mmc0:0001 ASTC 14.8 GiB [ 2.978743] mmcblk0: p1 [ 3.005160] mmc_host mmc1: Bus speed (slot 0) = 976562Hz (slot req 300000Hz, actual 244140HZ div = 2) [ 3.055260] mmc_host mmc1: Bus speed (slot 0) = 976562Hz (slot req 200000Hz, actual 162760HZ div = 3) [ 3.111249] mmc_host mmc1: Bus speed (slot 0) = 976562Hz (slot req 100000Hz, actual 97656HZ div = 5) [ 6.393533] EXT4-fs (mmcblk0p1): mounted filesystem with writeback data mode. Opts: (null) [ 9.302119] EXT4-fs (mmcblk0p1): re-mounted. Opts: commit=600,errors=remount-ro
  2. Oh, sorry I thought they weren't that necessary... First coldboot of the day: https://imgur.com/a/TbHgD72 (Same as before I think, it got detected, yet it can't connect or scan for APs) After a reboot: https://imgur.com/a/fv2pAmV (with dmesg, and sha1sum to make sure that the file is the same) Checksum on my side before copying into a flash drive:
  3. Not entirely sure as I can't really test it on Android... Not sure how... I'm speculating that it might be the same way as I am doing it right now, only with a Terminal Emulator app, but I haven't tried... On that dtb, the LEDs works exactly the same as the one before... About the WiFi, after trying that dtb, it still doesn't get detected on either ifconfig or rk322x-config Thanks for your time!
  4. Did as mentioned, here are the tests / results: - Bootup has the LEDs flashing red and blue each second - Ran ifconfig, no WLAN interface showing up - rk322x-config, undetected WiFi module - echo default-on > /sys/class/leds/working/trigger - turns on the red LED, and turns off blue LED... --- Expected: RED: on BLUE: ?? - echo heartbeat > /sys/class/leds/auxiliary/trigger - no effect, the blue LED is still off, red LED still powered on... --- Expected: RED: on BLUE: "beating" 2x per second - echo kbd-numlock > /sys/class/leds/working/trigger - numlock now toggles red / blue LED... red if numlock is active, blue if not... --- Expected: RED: on/off based on numlock BLUE: "beating" 2x per second - echo timer > /sys/class/leds/auxiliary/trigger - no effect, the blue is still the direct inverse of the red LED's state... off if the red LED is on, on if the red LED is off... --- Expected: RED: on/off based on numlock BLUE: toggling on/off state every second Made sure multiple times that /boot/armbianEnv.txt contained led-conf6 instead of led-conf5, current overlays: emmc wlan-esp8089 led-conf6 Image: https://imgur.com/a/SiJnFQs
  5. Oh I missed the **mega**bytes part... oof That's awesome though, I'll wait for the modifications and will test it on the board Thanks!
  6. Here's the backup: https://mega.nz/file/MBV0FbjC#SFhkL9yvnxsE9EKuwhJBSX2J_cGom3HQbZrwg1FjmdM I'm not sure if the literal first 32 bytes of the extracted file is significant, but if it actually is, for convenience, here's the hex dump for the first 32 bytes: 00 01 83 00 00 02 00 00 00 00 00 00 00 00 00 00 16 00 00 00 00 00 00 00 64 06 00 00 00 00 00 00 To my surprise, when I booted the second board up just now, it detects the esp8089 and even lists it at ifconfig as wlan0... And after a few reboots (probably 2 or 3) and switching between crystal_26M_en values, now it doesn't... It randomly works on 26M regardless if set as 1 or 0 At that time that it was working though, I still can't connect with it for some reason (using armbian-config), and ifconfig lists the wlan0 interface as an "Ethernet" device, + yeah the LEDs are still acting weirdly This is all using the led-conf5 option btw, which, shows `working` and `auxiliary` for `/sys/class/leds` but uses it as if it's just one LED and switches between red/blue, instead of being 2 individually controllable LEDs, and apparently its default trigger is mmc2 activity I haven't set it up on my network yet to copy/paste dmesg as that would require me to set a static IP for it and place it far away from my workdesk, and near the router as only the ethernet works... but here's a photo of dmesg, grepping through possibly relevant keywords: https://imgur.com/a/VjpJUkr Thanks for your time!
  7. The esp8089 works flawlessly on the stock android firmware, I made a backup of it with the multitool if that would be of any help, And I mentioned the LEDs because I've never gotten it to work properly on the second board 100%... But I've gotten it to work perfectly on the first board, as a network activity indicator. On the second board, the system seems to be just using it either as a CPU activity monitor, or just a straight one color when the system is on... When setting triggers on (iirc from the top of my head) `/sys/class/leds/working` and `/sys/class/leds/auxiliary` it either only gets detected as one LED... Or one of them is always on and only the other is controllable... Which is why I'm speculating that it might be a misconfiguration in terms of the pinout, rather than a hardware issue Thanks
  8. Loving the project a lot, got it working on an MXQ PRO 4K rk3229 complete with WiFi support after I figured out the correct led gpio config... But it was running off of the SD card, wasn't able to install to NAND, not sure why but it wasn't a big deal When I tried it on another board, an MXQ PRO 4K 5G it worked smoother with me being able to install to eMMC from multitool, however I'm experiencing gpio issues... The LEDs don't work as well as the other board and this also affects WiFi which is an ESP8089. It seldomly gets detected at random, and most of the time it's not detected at all. Tried all the info I could find about this by changing up the CPU types to lower speeds, editing esp8089.conf setting crystal 26MHz to 1, and trying every LED configurations on rk322x-config... None of those worked, as I'm assuming the gpio pins are still misconfigured If there's a specific procedure to fix the issue, I'd gladly follow to learn more Thanks for this great project, it's been fun Board Images: https://imgur.com/a/2eA3pmE