HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. This page needs HTML code to be minified as it can gain 1.4 kB, which is 18% of the original size. Network & Wireless Cards. A network interface controller (also known as a network interface card, network adapter, LAN adapter and by similar terms). Download the latest drivers for your Network & Wireless Cards to keep your Computer up-to-date.
- Silan Network Restaurant
- Silan Network & Wireless Cards Drivers
- Silan Network Sunny Anderson
- Silan Network Recipes
This is intended to be a repository for info on the MStar/SigmaStar SoCsand the associated mainling effort.
This will probably never get as big as linux-sunxi so github pages should bemore than enough.
Before MStar was bought out by MediaTek the company offered a wide rangeof SoCs focused at STB and camera applications. Since the company wasbought by MediaTek the camera SoC part of the company has been spun outinto the fully owned subsidiary called Sigmastar. The camera SoCs that are now marketed by Sigmastar will be the main focus here.
It’s worth noting that the MStar/Sigmastar camera SoCs seem to be derivedfrom the SoCs made by Alpha Imaging Technology which was merged into MStarat some point.
- Q: Why linux-chenxing?
A: The name is a parody of linux-sunxi for Allwinner SoCs. MStar in Chinese is chenxing and the newer SigmaStar name is xingchen.
- Q: Is this the official support site for MStar/SigmaStar?
A: No. There is no relationship between this site and the vendor. This is a “community” (community meaning one fat guy with a multimeter right now) research effort.
- Q: If I pay you money will you support me using the official SDKs?
- Q: Is there an IRC channel, discord or something for discussion?
A: Please use github’s dicussion feature for now.
- Q: Should I upload SDKs and post links here?
A: Please don’t. Extract the parts that are licensed in a friendly way (i.e. GPLv2 or BSD) and push them onto github or somewhere and link that instead.
The exception to this rule is where the SDK has already been leaked to github. For example there are some copies of the SDKs that seem to have been uploaded by manufacturers that are actually trying to comply with the licenses covering the kernel, u-boot etc and uploaded the entire SDK.
Basically, if someone else leaks their copy of an SDK that’s their problem.
- Q: Should I upload datasheets or other references here?
A: Maybe. If they are already easy to download then putting them here for non-profit educational/research purposes should be ok. IANAL but as far as I can tell github is in the US and fair use applies.
Materials that are behind an NDA wall like those in the SDKs might be interesting but most of the information they contain can be worked out from the kernel sources or about stuff contained the proprietary modules we don’t really care about anyways.
- Q: Why is Tux orange and why does he have a stalk and leaf sticking out of his head?
- A: The SigmaStar logo is an orange isn’t it? Looks like one to me.
For most chips u-boot is loaded by loading the SPL as IPL-CUST from the IPL so that blob is needed.The mercury5 however can boot with the u-boot SPL as the IPL so no blobs are required.Getting the other chips to boot without the vendor IPL is mostly a case of doing the DDR setup in the SPL.
|load u-boot SPL from boot ROM||load u-boot SPL from vendor IPL||load u-boot from SPI NOR||load u-boot from SPI NAND||load u-boot from SD|
|boots to shell from initramfs||boots to shell from local storage||full system from local storage with network etc||boots without blobs (no vendor IPL)||smp|
This table is an attempt to collect all of the different part numbers forthe different families and the resources that have been found to reverse engineer each of them.
If possible the data codes will have the earliest and latest known date codes so that we can tell roughlywhen each type of chip was produced.
|family||part||date codes||process size||sample device acquired||boot rom dumped||firmware dumped||SDK acquired||product brief acquired||datasheet acquired|
|msc316dc||1929S||yes||same as msc313e||yes||yes|
-  SDK seems to actually be for the infinity1 but the infinity3 is very similar
Spotted a chip that isn’t here? Please see adding new chips.
MStar used to make a lot of MIPS based SoCs for STBs. These aren’t thatinteresting in themselves but the IP blocks used in the MIPS SoCs werecarried forward to the later ARM chips so any datasheets that can be foundfor the MIPS SoCs might help with reverse engineering the current ARM basedones.
32bit ARM based
Silan Network Restaurant
- MSO9810 - Quad Core ARM Cortex-A9
- MST786 - Dual core Cortex A9 automotive (head unit) SoC
Infinity IP camera family
IP camera chips with video encoder and camera interface
- MSC313 - Cortex A7 + 64MB DDR2 in a QFN80
- MSC313D - Probably a Cortex A7 + 128MB DDR3 in a BGA
- part numbers not known. there are some references in the SDKs etc to infinity2 and it seemsto be dual Cortex A9
- Probably for the recording side i.e. has a video decoder and no camera interface.
- Closer to the infinity6 chips than the infinity2.
Probably a replacement for the recording side, has video decoder, framebuffer etc.
- SSR621D - Dual Cortex A7 128MB DDR3(TBC) in QFN128 with HDMI, VGA, SATA
- SSD201 - Dual Cortex A7 with 64MB of DDR2 in QFN128
SSD202D - Dual Cortex A7 with 128MB of DDR3 in a QFN128
- MSR620? Maybe “k6lite” family
- MSR630? Maybe “k6” family
- TL-NVR6104C-4PX (based on MSR630 being in the source paths in the kernel binary)
Updated version of the infinity1
- MSC313E - Cortex A7 + 64MB DDR2 in a QFN80
- MSC316DC - Cortex A7 + 128MB DDR3 in a QFN88
- MSC316Q - Cortex A7 + 128MB DDR3 in a 256 ball BGA
- MSC318 - Cortex A7 + 128MB DDR3 in a 324 ball BGA
Doesn’t seem to exist.
Seems to be a version of the infinity3 that can handle higher resoltion sensors.
- SSC328Q - Cortex A7 + 256MB DDR3 (this might be i6)
- SSC329Q - Cortex A7 + 256MB DDR3 + NPU (this might be i6)
Updated version of the infinity3.
- SSC323 - probably Cortex A7 + 64MB DDR2 in a QFN88
- SSC325 - Cortex A7 + 64MB DDR2 in a QFN88
- SSC325DE - Cortex A7 + 128MB DDR3 in a QFN88
- SSC326D - Cortex A7 + 128MB DDR3 + NPU
- SSC327DE - Cortex A7 + 128MB DDR3
- SSC335DE - probably Cortex A7 + ?? + in a QFN88
- SSC337DE - probably Cortex A7 + 128MB DDR3 + in a QFN128– MC-F50: https://item.taobao.com/item.htm?id=619778901522&spm=1101.1101.N.N.e3dd64c
- Infinity 6e seems to be a dual core variation in this family
Dash camera SoC.
- AIT8328/MSC8328 - Probably ARM9
- AIT8428 - Probably ARM9
Dash camera SoC based on the infinity3.
- SSC8336 - Probably Cortex A7 + 64MB DDR2 in a QFP128
- SSC8336N - Cortex A7 + 64MB DDR2 in a 128 pin QFN
- SSC8339D - Probably in this family, Cortex A7 + 128MB(?) DDR3(?) in a 268 ball BGA
- MSB2521 - ARM9 based SatNav on a chip
- MSB2531 - Cortex A7 SatNav on a chip
- MSW8535N - ARM9 based feature phone chip?
- SSC8629D - AI enabled
- SSD210 - Dual Cortex A7 QFN68
According to the code that is in the wild and SigmaStars page there are some Cortex-A53 based chips.
- SSW101B - Seems to be a wifi chip, maybe based on the same core as the XR819.
- See xradio.
Injoinic seem to be the recommended PMIC vendor for these chips. Maybe like the Allwinner/Xpowers relationship?
Silan MEMs accelerometers seem to be used for a lot of the dash cam devices.
- BootROM - Baked in BootROM
- IPL - First/Second stage bootloaders
- MXPT - Partition table used for SPI NOR
Sources of firmwares for reverse engineering
Silan Network & Wireless Cards Drivers
To get the device tree out of the kernel you can use binwalk + extract-dtb and dtc.
- Breadbee (Infinity3 - msc313e)
- 70mai Midrive D08 a.k.a Dash Cam Lite (Mercury5)
- aiwinn - seems to supply a bunch of AI enabled things based on SigmaStar SoCs
- comake.online - Sigmastar’s new open forum.
Silan Network Sunny Anderson