社区对 SSC377 的了解

摘自 Tino Darkness 在 OpenIPC Telegram 群组中的消息。每一条都链接到其出处消息。

• SSC377 is a single-core Cortex-A35, up to 1 GHz according to various Chinese sites. (消息 1, 消息 2, 消息 3)
• The plain SSC377 has 64 MB of DDR2 (SSC377D[E] has 128 MB and SSC377Q[E] 256 MB); a boot log from an SSC377 shows Memory: 32588K/38720K available. (消息 1, 消息 2, 消息 3)
• SSC377 looks like a new SSC335/337 but is a different family, I6C, and as Tino recalls uses a 5.x kernel, while 335/337 are I6B0. In 2023-09 all new Anjoy devices used the 377. (消息 1, 消息 2)
• Tino guessed the chip ID would be 0xF9 (249), INFINITY6C SSC027A-S01A. (消息 1)
• With 64 MB DDR, not much should be expected from SSC377: it looks like an updated SSC335, more like SSC335 with extras, and Tino compares it to the 335/337. (消息 1, 消息 2, 消息 3)
• His rough ranking (IMHO), weakest to strongest: ssc335/377, ssc335de, ssc337DE, ssc378DE, ssc30kd, ssc30kq, ssc338q, ssc339g, ssc359. (消息 1)
• As of 2024-03-26, SSC377 was not yet supported by OpenIPC. (消息 1)
• (Infinity6C family) SSC37x (Maruko) chips use Cortex-A35 cores, not Cortex-A7 like the Pudding/SSC338 generation. (消息 1, 消息 2, 消息 3)
• (Infinity6C family) Tino recalls that SSC37x (Maruko SDK) has a newer version of the IPU; he clarified the improvement is a new IPU IP block, a separate core, not the CPU. (消息 1, 消息 2)
• (Infinity6C family) In 2026-02 Tino compared SSC377/378 to the SSC30KQ/D: 1x Cortex-A35 versus 2x Cortex-A7, but with a newer ISP and, it seems, newer DDR. Earlier, in 2024-03, he said 'who knows?', but some of the I6Cs and (maybe) the new I6Fs look as good as, if not better than, the popular SSC338 (I6E). (消息 1, 消息 2)
• (Infinity6C family) Maruko, I6C and SSC37x refer to the same platform: SSC377/378 belong to I6C, and infinity6c is the SDK SoC codename/family. (消息 1, 消息 2, 消息 3)
• (Infinity6C family) The I6C SDK codename is Maruko, while I6E uses Pudding, so the two need different SDKs. A Maruko SDK build dated 2022/10/27 (ILS00V2) looked to Tino like a release candidate. (消息 1, 消息 2, 消息 3)
• (Infinity6C family) Tino recalls (IIRC) the kernel is 5.10.x and thought binary incompatibility was more likely due to the different kernel version; he also noted the new I6C SDK looks to use more recent uClibc/glibc and kernel. (消息 1, 消息 2)
• (Infinity6C family) I6C, I6F and I7 are 'new'-style SigmaStar SDKs where devId is the first parameter in most API calls, while I6E is 'old' style; for example in Maruko (I6C) and Tiramisu (I6F) MI_VENC_CreateChn takes an extra MI_VENC_DEV argument, and some pipeline workflow changed. (消息 1, 消息 2)
• (Infinity6C family) As Tino recalls, starting from I6C SigmaStar made very strong API changes (a completely changed ABI and a new 5.x kernel), so porting from I6E is not as simple as the Ispahan-to-Pudding move; older I6x families have far more similarities than differences. (消息 1, 消息 2)
• (Infinity6C family) Of the Infinity6C configs infinity6c_ssc027a_s01 and infinity6c_ssc027b_s01, ssc027a is for the QFN88 chip and ssc027b for QFN128. (消息 1)
• (Infinity6C family) The I6C dtsi puts uart0 at 0x1F221000, uart1 at 0x1F221200 and fuart at 0x1F220400, each a 0x200-sized register block. Tino thinks PM_UART is probably on pins 57 and 58 of the SSC37x QFN128 package. (消息 1, 消息 2)
• (Infinity6C family) SSC37x does not work properly with firmware from SSC338, and SigmaStar IQ files are usually incompatible even across SDK versions, let alone across families such as I6E and I6C. (消息 1, 消息 2)
• (Infinity6C family) OpenIPC support history: as of 2024-04-12 the I6C SDK was still not available on GitHub; on 2024-04-21 Tino said that, AFAIK, only I6E/I6B0 were supported in OpenIPC and I6C was in progress; on 2024-05-07 mini-i6e and mini-i6c looked to be in progress at the same time. (消息 1, 消息 2, 消息 3)
• (Infinity6C family) In 2024-06 I6C was still quite new for OpenIPC but there were test builds for the 378; as of 2024-12-10, as far as Tino could see on GitHub, SSC377/378 (I6C) support was already there. (消息 1, 消息 2)
• (Infinity6C family) There is no majestic-fpv for Infinity6C: majestic.infinity6c.fpv.master.tar.bz2 returns 403 Forbidden (2025-04-27), and AFAIK only majestic.infinity6c.lite exists. Tino fears the lite build simply has no FPV optimisations. (消息 1, 消息 2, 消息 3)
• (Infinity6C family) Majestic is freeware, not open source. AFAIU Majestic for SSC37x has existed for a long time, even in a new build style with the SDK linked statically (as of 2025-07). (消息 1, 消息 2)
• (Infinity6C family) On Maruko, RGN (OSD regions) can attach to SCLx/WIN/JPEG/DISP, but in majestic-i6c-lite RGN is bound to VENC, not SCL. Tino thinks msposd is already fixed for I6C (2025-05-20). (消息 1, 消息 2, 消息 3)
• (Infinity6C family) Divinus: on 2025-05-13 Tino thought it still did not support I6C, and on 2025-05-18 he said it already has partial/initial I6C support; in 2025-08 he noted Divinus on SSC37x is not that easy. (消息 1, 消息 2, 消息 3)
• (Infinity6C family) In 2025-02 Tino asked whether the I6C MI_VENC had already been unlocked from its 60 fps limit for FPV use. (消息 1)
• (Infinity6C family) As Tino recalls, Maruko (SSC37x) and later support X/Y correction, where SSC338/Pudding supports only Y. (消息 1)
• (Infinity6C family) Infinity6C is a new, cheaper SigmaStar chipset; Anjoy is slowly moving to this cost-effective generation (SSC377/378), with modules such as MC-J86 and MC-A81 using SSC378/SSC377DE. As of 2024-05-08, though, SSC377/378 were not that common yet. (消息 1, 消息 2, 消息 3)
• (Infinity6C family) In Tino's opinion (2025-02), SSC37x/30x/38x are a new series of SoCs that will gradually replace or extend the familiar I6E Cortex-A7 SoCs. (消息 1)
• (Infinity6C family) The Maruko SDK was never available for download on the vendor website Tino was referring to, not even on the old site (2026-08). (消息 1)