TemporarilyOffline / X6100-TOADs

Central Location for TOADs Hacking of the X6100
67 stars 10 forks source link

Requesting a discussion page on this repo #12

Open WheezyE opened 1 year ago

WheezyE commented 1 year ago

Just organizing info about the radio's CB166 SBC & STM32 onboard computers.

x6100 DispUnit (Allwinner CB166 single-board computer) 'front-end'

Allwinner R16 CB166 (MYZR-R16-CB166) SBC SoC/CPU: R16-J (4x ARM Cortex-A7@ 528 MHz, ARMv7-A 32-bit) (IC pinout page12). eMMC (on-board memory storage): likely 8GB RAM: likely DDR3/DDR3L 1GB Breakout/IO/development board: EK166 (pictures). Visual description: Blue PCB. Main chip says "Allwinner Tech R16-J M3203BA 63X1. PCB says "MY_AW_R16 CB166_Rev.B" and "2114". Pinout: See 'Pin Definition'

For comparison

Raspberry Pi 2 SoC/CPU: BCM2836 (4x ARM Cortex-A7@ 900 MHz, ARMv7-A 32-bit) RAM: 1 GB Power consumption (idle/stress): 220 mA (1.1 W) / 400 mA (~2.1 W) [Model 2B]

Raspberry Pi 3+ SoC/CPU: BCM2837B0 (4x ARM Cortex-A53 @ 1.4 GHz, ARMv8 64-bit / 32-bit) eMMC: 8 GB (or more) RAM: 1GB (or more) Power consumption (idle/stress): 350 mA (1.9 W) / 980 mA (5.1 W) [Model 3B+] Pinout: page9

Raspberry Pi 4 SoC/CPU: BCM2711 (4x ARM Cortex-A72@ 1.5 GHz, ARMv8 64-bit / 32-bit) eMMC: 8 GB (or more) RAM: 1 GB (or more) Power consumption: 540 mA (2.7 W) / 1280 mA (6.4 W) [Model 4B] Pinout: page17

CB166 SBC connects to: "XIEGU X6100 DispUnit V1.2 4521" board, which itself notably connects to the screen (ribbon cable connector), digital control dials/buttons, USB 2.0 hub & serial port controllers (GL850G/CH342f), wifi/bluetooth chip (BL-R8723BT1, 802.11b/g/n, BT v2.1, antennas nearby), audio chip (CM108B), (image1, image2, image3, image4, image5), and the X6100 BaseUnit board.

x6100 BaseUnit (STM32 F427ZGT6 system-on-chip) 'back-end'

The STM32F427ZGT6's Data Sheet (page 227) allows us to parse the chip's naming convention as such:

EDIT: Learned more about the x6100's on-board computers and wanted to update this.

TemporarilyOffline commented 1 year ago

You can continue to discuss in this issue, or you're welcomed to submit a markdown formatted file to the repo via pull request and I'll merge it into the main documentation. There is also a wiki system built in and I'm happy to collaborate there. So many options! Glad you're here to help!