Jump to content

Recommended Posts

Posted

Hello @Nick A i did everything git cloned now im in setup,

heres what i choosed:

1. Do not change kernel configuration

And after that, i don't found any compactible for my h313

also note that mine firmware is based off d9 Pro 5g so i think it could use the same dram settings and wifi chip except for the cpu. Hope this helps!

Posted

@Nick A heres the complete info

🧠 DRAM

Chip 1:

Marking: MPF694C4G-P

Maker: UniIC (UnilC)

Type: DDR3/DDR3L

Density: 4 Gb (512 MB)

Date code: 2021 (week 11)

Chip 2:

Marking: SBC13H4G150

Maker: UniIC (UnilC)

Type: DDR3/DDR3L

Density: 4 Gb (512 MB)

Date code: 2020 (week 11)

Total RAM = 1 GB (2 × 512 MB)

💾 Storage (eMMC)

Chip:

Marking (line 1): NCEMAM60-08G

Maker: FORESEE

Type: eMMC Flash (not raw NAND)

Capacity: 8 GB

Marking (line 2): 000

Serial/Batch: Z1S1801147073

Date code: 1802 → Year 2018, Week 02

Total storage = 8 GB eMMC (manufactured early 2018)

Posted (edited)

@Nick A 

full log (failed):

[💲|🌱] Starting main configuration
[💲|🌱] Using REVISION from [ main VERSION file: '25.05.0-trunk' ]
[💲|🌿] Enabling extension [ armbian-config ]
[💲|🌱] Sourcing family configuration [ /home/nguye/build/config/sources/families/sun50iw9.conf ]
[💲|🌿] Enabling extension [ sunxi-tools ]
[💲|] change-tracking: after sourcing family config [ KERNEL_MAJOR_MINOR='6.12' ]
[💲|] change-tracking: after sourcing family config [ KERNELBRANCH='tag:v6.12.11' ]
[💲|] change-tracking: after sourcing family config [ LINUXFAMILY='sunxi64'  # (was: 'sun50iw9') ]
[💲|] change-tracking: after sourcing family config [ KERNELPATCHDIR='archive/warpme-6.12' ]
[💲|] change-tracking: after sourcing family config [ BOOTBRANCH='tag:v2025.01' ]
[💲|] change-tracking: after sourcing family config [ BOOTPATCHDIR='u-boot-h616' ]
[💲|] change-tracking: after sourcing family config [ ATFBRANCH='tag:lts-v2.10.14' ]
[💲|] change-tracking: after sourcing family config [ NETWORKING_STACK='network-manager' ]
[💲|🌱] Sourcing arch configuration [ arm64.conf ]
[💲|] change-tracking: after sourcing arm64 arch [ ATFDIR='arm-trusted-firmware' ]
[💲|🌱] Using NETWORKING_STACK [ NETWORKING_STACK: network-manager ]
[💲|🌱] Adding networking extensions [ net-network-manager, net-chrony ]
[💲|🌿] Enabling extension [ net-network-manager ]
[💲|🌿] Enabling extension [ net-chrony ]
[💲|🌱] Extension manager [ processed 17 Extension Methods calls and 27 Extension Method implementations ]
[💲|🌱] x96q-lpddr3 [ Using allwinner/sun50i-h313-x96-q-lpddr3.dtb for edge ]
[💲|💥] Error  1 occurred in SUBSHELL [ SUBSHELL at /home/nguye/build/lib/functions/configuration/config-desktop.sh:48 ]
[💲|💥] Cleaning up [ please wait for cleanups to finish ]
[💲|🌿] ANSI log file built; inspect it by running: [ less -RS output/logs/log-build-5e1956f5-4bb3-4cdf-b026-7bcfa7d1794e.log.ans ]
[💲|🌱] Share log manually: [ use one of the commands below (or add SHARE_LOG=yes next time!) ]
[💲|🌿] Share log manually: [ curl --data-binary @output/logs/log-build-5e1956f5-4bb3-4cdf-b026-7bcfa7d1794e.log.ans https://paste.armbian.com/log ]
[💲|🌿] Share log manually: [ curl --data-binary @output/logs/log-build-5e1956f5-4bb3-4cdf-b026-7bcfa7d1794e.log.ans https://paste.armbian.de/log ]
[💲|🌿] Share log manually: [ curl --data-binary @output/logs/log-build-5e1956f5-4bb3-4cdf-b026-7bcfa7d1794e.log.ans https://paste.next.armbian.com/log ]
[💲|🌿] Share log manually: [ curl --data-binary @output/logs/log-build-5e1956f5-4bb3-4cdf-b026-7bcfa7d1794e.log.ans https://paste.armbian.eu/log ]
nguye@DESKTOP-IFEAUMD:~/build$

 

EDIT: it continued while i tried Debian 12

 

Next i choosed

xfce

config_base (onlyone)

internet

Edited by Ducdanh Nguyen
Posted (edited)

@Ducdanh Nguyen do you know which axp chip you have on your board? It’s a very small chip with axp written on it.

 

I don’t see the H313 markings on your SOC chip. Are you sure you have a H313? If you don’t see an axp chip you might not even have a allwinner SOC.

 

If your android is rooted then it probably has one installed.

Edited by Nick A
Posted (edited)

@Nick A su binary installed, but not working correctly, i don't know why, the chip is def h313 because i used cat /proc/cpuinfo(and others) and with grok commands i can confirm it uses cortex-a53 (which includes in h313) and bigfish manufactor/ or codename idk but it's part of  allwinner, i mean enought to prove that mine is h313 

Edited by Ducdanh Nguyen

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines