Board proposal: TP-LINK CU300Y (China Unicom custom), PCB code S70906, SigmaStar SSC335 (Infinity6B0), 16 MB SPI NOR, SSW101B WiFi over USB, two-axis four-phase stepper PTZ. No shell on stock firmware; information below was parsed offline from a programmer-read whole-flash dump (attached, kept private). Stock identity (from identity block inside the dump): - dotModelId TP_SS_SSC335_IPC_CU300Y, devName CU300Y, hwVer 2.1, board S70906 - MAC , serial , focalLength 4 - Sensor not identified offline; candidates sc3335 / sc3336 / imx307. PTZ GPIO parsed from the stock kernel: - Pan: phases 11 13 2 3, direction -1, +/-163 deg, max_steps 3709 - Tilt: phases 18 19 17 16, direction -1, -30..+90 deg, max_steps 2048 - Home switch on gpio 0, active low. What we tried: - Programmer-wrote a 16 MB image assembled from the current OpenIPC nightly for SSC335 NOR: u-boot-ssc335-nor.bin @0x000000, env @0x040000, kernel @0x050000, rootfs @0x250000, rootmtd=10240k, rootsize=0xA00000. Both lite and ultimate built; lite was programmed. - Read-back MD5 matches the programmed image byte-for-byte, so this is not a write/contact issue. Symptoms after power-on: - Red LED only, faint blink; no motor self-test; no buzzer/relay click. - No L2 response: MAC does not appear in ARP, ping fails, 80/22/554/8554/8080 closed. PHY link reports 1 Gbps but the SoC network stack does not start. - Restoring the stock dump makes the camera fully normal again (red/green alternating, motor/buzzer actuate, back on stock network), so chip, programmer, clip and board hardware are good. Offline checks already done: - Bootloader/IPL header, kernel and rootfs MD5 match the official nightly; env CRC32 valid; partition offsets match the OpenIPC SSC335 NOR layout. - Stock dump regions 0x770000-0xF7FFFF are all 0xFF; no customer key/signature blob lives in that NOR range. Whether secure boot is enforced lives in efuse and could not be read from flash. Questions for maintainers: 1. Is this board already in the catalogue under another model/alias? 2. Does the released u-boot-ssc335-nor.bin initialize DDR/PMU on I6B0 by itself, or does it need the vendor IPL-CUST blob retained for memory training on some boards? 3. Could this unit have secure boot enabled in efuse, causing an unsigned OpenIPC IPL/UBT to be rejected at the first BROM/IPL stage? Is there any way to determine that without UART? 4. Any known DDR size/timing variant for SSC335 on this board? 5. Which sensor and gpio-step PTZ profile should this board use? No UART adapter on hand; if the next step needs a boot log we will get a USB-TTL and capture the console.