Last active
November 12, 2024 06:27
-
-
Save djbr1/3c1410523d05bb0e2a2595a3d169718c to your computer and use it in GitHub Desktop.
X6100 block diagram
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
+------------+ | |
Power 12v | STM 32 | RJ45 Mic | |
Antenna | DSP engine | S/P (headphone) | |
I/Q | (Base) | KEY (paddles or straight) | |
| | ACC (linear amplifier interface) | |
+-----+------+ USB DEV (CAT control and tx/rx audio) | |
|I2C or ? | |
----------------|------------------------------------------ | |
| | |
+-----+------+ | |
| A31 R16 | | |
Bluetooth | linux | USB HOST (eg. external keyboard) | |
WLAN | QTGUI APP | SD CARD | |
| | three rotary encoders (VFO, Volume, MFK) | |
+------------+ 20+ front panel buttons |
Author
djbr1
commented
Apr 9, 2022
•
possible but CAT did not work with out the APP running.
so my current estimate is that the APP controls the MUX chip and with out it the CAT from USB is not routed correct.
Intressting too is that CAT from the SoC / Linux is possible too so the SoC may has a Serial to the same MUX chip but I did not find the connection yet. 160+ connections on the SoC module is a loot 😉
performance comparison X6100 Allwinner R16 vs. Raspi 2
https://browser.geekbench.com/v5/cpu/compare/19056301?baseline=18891273
comparison R16 vs raspi3
https://browser.geekbench.com/v5/cpu/compare/19056301?baseline=19055597
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment