Jump to content

Randlin

Members
  • Posts

    10
  • Joined

  • Last visited

Recent Profile Visitors

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

  1. Alright, I built the x96q-lpddr3 image using the patches suggested. It booted (partially). Nothing on the screen, but it is starting! I chose that image because it is H313 and lpddr3 (the android uboot build that worked before detected it as such) I attached the serial log. It's getting late here and I may not get much more done on this until Monday, but this is a good sign in my opinion. uboot.txt
  2. Nice! I'll try that. Thank you for your help so far. Finding the right documentation has been a little tricky for me and I really appreciate the help.
  3. Doing a little digging, From https://patchwork.ozlabs.org/project/uboot/patch/20210822044649.13585-3-samuel@sholland.org/ "Most Allwinner sunxi SoCs have separate boot ROMs in non-secure and secure mode. The "non-secure" or "normal" boot ROM (NBROM) uses the existing sunxi_egon image type. The secure boot ROM (SBROM) uses a completely different image type, known as TOC0." I am not an expert, but I feel that is likely the issue here. Since the X96 s400 will launch the bootrom, it should only require a bootrom change. from https://linux-sunxi.org/TOC0#U-Boot.27s_mkimage It should only need a RSA key generated, as the X96 S400 will launch the sboot, thus no Vendor e-fuse should be set.
  4. The X96_S400_20220610-1210 will error out with: sunxi sprite: toc magic is error need secure image This was from an attempted flash with Phoenixsuite
  5. Oops, I screwed up which Android image works. The X96 image, not x96q will launch uboot during the Phoenixsuit flash, but will not fully complete and will complain it needs secure or something, I'll get logs, the Transpeed atv image will flash and will get stuck not getting past sboot. The images in question: X96_S400_20220610-1210 h313_20230921_atv_Transpeed_2_16_orig I can upload them if it will help.
  6. So, unfortunately all the images that I have tried get stuck in fel mode. I do know the G96 needs secure mode according to debug logs when I was using Phoenixsuit before and is signed in test keys if that helps. The h313_20230921_atv_Transpeed_2_16_orig android image will launch into uboot (I can get into uboot shell via serial) and flash in Phoenixsuit, but will get stuck in sboot upon rebooting and unable to get any farther, so no uboot shell. Armbian-unofficial_25.05.0-trunk_Tanix-tx6s-axp313_bookworm_edge_6.12.11 stuck at fel Armbian-unofficial_25.05.0-trunk_X98h_bookworm_edge_6.12.11_server stuck at fel Armbian-unofficial_25.05.0-trunk_Transpeed-8k618-t_bookworm_edge_6.12.11_server stuck at fel Armbian-unofficial_25.05.0-trunk_Vontar-h618_bookworm_edge_6.12.11_server stuck at fel Armbian-unofficial_25.05.0-trunk_X96q-lpddr3-v1-3_bookworm_edge_6.12.11_server also stuck at fel
  7. The Tanix-tx6s-axp313 image goes straight to fel, no serial logs
  8. Ok, I'll try all of them. I'll report back tomorrow.
  9. Alright, that took a little bit to find, that chip is small! AXP313A pc21BAA 64N1
  10. I have a couple of cheap Allwinner h313 tv sticks "G96" that I would like to try to port to Armbian. Not exactly sure where to start, but I managed to soft emmc brick one doing so (boots off sd card fine). No compatible firmware is available anywhere, so I rooted it and dumped the emmc firmware, available here: https://archive.org/details/G96_Firmware_Dump . This firmware boots just fine off a sd card. The wifi chip is BCM43340, which has been patched into Armbian before. There are a few more images at the link, let me know what I should do/dump to help.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines