Jump to content

Nick A

Members
  • Posts

    589
  • Joined

  • Last visited

Recent Profile Visitors

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

  1. @Sergioclr output of USB-to-TTL converter. sudo dmesg
  2. @Sergioclr Can you post your boot logs? both android and armbian. Try this. phy-supply = <&reg_dldo1>; /* Try reg_dldo1 if aldo1 (1.8V) fails */
  3. @Sergioclr You don't need patches to edit the kernel config: config/kernel/linux-sunxi64-legacy.config sicxnull already has this patch, but with a different name: drv-pwm-sun50i-h616-enhance-pwm.patch drivers-pwm-Add-pwm-sunxi-enhance-driver-for-h616.patch To add Zero2W Ethernet settings to your DTS, you can create your own patch using git commands: Run ./compile.sh Press Ctrl+C in the middle of the kernel compilation. Navigate to the directory: cd cache/sources/linux-kernel-worktree/6.6*/ Use the following commands: sudo git status sudo git add . sudo git commit -m "dummypatch" sudo pico arch/arm64/boot/dts/allwinner/sun50i-h313-x96q-lpddr3.dts sudo git add . sudo git commit -m "Fix Ethernet" sudo git format-patch -1 1 for the first commit (0001-Fix-Ethernet.patch)... 2 for the first and second commit (0002-dummypatch.patch) ) The first "add" and "commit" cleans the kernel of previous patches, leaving you with a clean, patched kernel. The format-patch command will create a patch in the root directory of the kernel. Copy it to your patch directory. For original Armbian kernel patches, you must add them to series.armbian and series.conf.
  4. @Sergioclr I remember someone was able to get Ethernet working by changing 16 to 0. There's two locations ethernet-phy@16 and reg = <16>; +&mdio1 { + rmii_phy: ethernet-phy@0 { + compatible = "ethernet-phy-ieee802.3-c22"; + reg = <0>; + }; +};
  5. @qq20739111 thanks I'll remove the patch and compile a new image.
  6. @qq20739111 I have this patch included in my latest build. I wonder if this will change the cooling and performance. I'll release a test image so you can perform a benchmark on it. I only have a heat sink and fan for the A7A right now. https://github.com/radxa/allwinner-device/commit/7716c3aacfe0ca4432ad3973ec7ea864d2b91195
  7. @Sergioclr you need to extract your Device Tree DTS. Does your box have gigabit Ethernet?
  8. @qq20739111 The only change I can think of is the Thermal Governor is set to STEP_WISE by default. Without it the fan would run full speed all the time. Radxa had it set to CONFIG_THERMAL_DEFAULT_GOV_POWER_ALLOCATOR=y . I guess it would be safer to switch back to POWER_ALLOCATOR and figure another way to fix the fan issue. The 0.6.x images don't have these changes. Is this an image you compiled yourself? The CPU needs proper cooling you should install one of these. https://radxa.com/products/accessories/heatsink-6530b Extreme throttling introduced on A733 https://forum.radxa.com/t/extreme-throttling-introduced-on-a733/30688/4
  9. @Sergioclr Try this build. If Ethernet works then we can borrow the dts settings.
  10. @tiobily https://radxa.com/community Try these forums.
  11. @Sergioclr Well that is the u-boot root directory. Where the main Makefile is located. I added my own root_key.pem in the patch. You don't have to generate one. The root_key.pem for Allwinner H616/618/313 devices is not a single, universal file, but rather an RSA private key file used for signing bootloader images (TOC0) in secure boot implementations. In many commercial H616-based TV boxes, Secure Boot is enabled by the manufacturer, but the efuses (which store the root key hash) are not permanently locked, allowing the use of custom keys openssl genrsa -out root_key.pem
  12. @Sergioclr Search the forums for "PL2303HXA". I think it will work. After you compile your build, check build/cache/sources/u-boot-worktree/u-boot*; you should find root_key.pem there
  13. @Sergioclr Those unpopulated pads in the top-left corner are likely the UART (Serial) debug port. Check the underside of the board—are the pads labeled GND, TX, and RX there? The most reliable way to boot Linux on this box is to use a USB-to-UART TTL adapter. Without one, we’re essentially working blind.
  14. @Sergioclr are you sure the board has secure boot enabled? You should install a USB-to-UART TTL device.
  15. @Sergioclr Try this one next. 159-add-x96-q-lpddr3-v1.3-defconfig.patch
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines