Posted on — Leave a comment

Rooting (or failing to root) a Heights HT-8766BE — with nothing but a UART

Status: in progress, but a lot further along than the title suggests. Ethernet, Wi-Fi, VLAN-aware switching and LuCI are all genuinely working on this hardware now — just not yet all stitched together under a single unattended OpenWrt boot. I’m publishing this as a running account, written as it happens, warts and all, because the honest version of this story is more useful than a tidy one.

The target

The Heights HT-8766BE is a Wi-Fi 7 gateway supplied by UK ISPs — the kind of box that turns up, pre-provisioned, bolted to the wall, and never thought about again. This one is brand new out of the box. There is essentially zero public information about it: nothing in the OpenWrt Table of Hardware, nothing on the OpenWrt forum, no FCC filing I could find, no teardown photos. The closest public relatives are the Heights HT-6766BE (same silicon family, different cosmetic SKU) and its ISP-branded variants sold by BeFibre and Zzoomm in the UK.

Heights states its product line is built on Broadcom chipsets and SDK. That turns out to be exactly right, and it shapes everything that follows.

The one constraint that defines this whole project: the PCB sits under a heatsink/shield I’m not opening. The only access point is a UART header. Everything here — the recon, the backup, the porting, the debugging — happens over a 115200-baud serial link, nothing else, until very late in the piece when a wired Ethernet port came alive enough to test with a direct cable.

Tools

  • An ESP32 “Bus Pirate” board used purely as a UART-to-USB bridge (115200 8N1, 3.3 V).
  • A small Python daemon (uartd.py) that logs everything to a timestamped file and exposes a FIFO for sending commands — built because the browser-based serial terminal I started with missed the first ~21 seconds of boot, and because the router’s 1-second autoboot window needs something hammering the keyboard faster than a human can.
  • Standard Linux tools on the laptop side: objdump (ARM cross), readelf, Python for ad-hoc binary parsing (FDT walking, LZO/LZOP decompression via ctypes against liblzo2, FIT image parsing).

First boot: what’s actually in this box

With the UART logger running from power-on, the full boot chain is visible:

BTRM
V4.0
...
U-Boot SPL 2019.07 (Apr 29 2026 - 13:55:51 +0800)
RevID: 67660A0
Board is non secure

“Board is non secure” is the single most important line in the whole log. No secure boot, no signature verification on the boot chain. That’s the thing that makes the rest of this project possible at all.

The hardware, pieced together from the boot log and later confirmed live:

  • SoC: Broadcom BCM96766 — 4× ARM Cortex (32-bit, armv7l) at 2 GHz, 1 GiB DDR4 at 1600 MHz.
  • Wi-Fi: two SoC-integrated radios, wl0 (BCM6039, 4×4, 2.4/5/6 GHz — Wi-Fi 7 capable) and wl1 (BCM6038, 2×2), both using Broadcom’s proprietary wl driver (version 17.10.369.39076).
  • Switch/Ethernet: a Broadcom-internal “SF2” switch fabric, plus a separate external AN8855 switch chip handling three of the Gigabit copper ports, plus two SERDES-capable ports (labelled “2.5G WAN/LAN” on the rear panel) driven directly by the SF2.
  • Voice: an Intel/MaxLinear SLIC for FXS/analogue phone lines.
  • Storage: eMMC, 3.64 GiB, with the usual boot0/boot1 hardware boot partitions (4 MiB each) plus an RPMB region.
  • Boot chain: boot ROM → U-Boot SPL → U-Boot TPL → full U-Boot 2019.07 → a FIT image containing the Linux kernel and device tree.
  • Software: Broadcom’s BDK/SDK 5.04L.04p3, Linux 4.19.294 (armv7, BusyBox 1.36.1 userland, built with Buildroot 2021.02.4 / GCC 10.3), TR-069 (usp_md) and OpenPlat for ISP remote management.

The firmware identifies itself as 2.0.0.14-HT-6766BE-EM, customer config HT_6766BE_EM_BeFiber_default.conf — the BeFibre rebrand of the same hardware family, consistent with the sparse public information available.

U-Boot gives a one-second window to interrupt autoboot (Hit any key to stop autoboot: 1 0), with no authentication at all. The boot environment itself prints several things in cleartext during boot that I am deliberately not reproducing here, including an admin password, a default Wi-Fi key, the device serial number, and a set of TR-069 ACS credentials for the ISP’s provisioning server. None of that belongs in a public writeup, regardless of how it was obtained.

The eMMC layout is a plain GPT table with a dual-bank design — two complete copies of bootfs/rootfs (100 MiB / 200 MiB squashfs each), so the device can fail an update and fall back. This dual-bank structure turned out to be the single most useful thing about the whole device, for reasons that become obvious below.

Getting a root shell — without any credentials at all

U-Boot’s bootcmd is printenv;run once;sdk boot_img — a Broadcom-specific helper (sdk boot_img) that loads the active bank’s FIT image and boots it. Critically, U-Boot lets you append arbitrary extra kernel command-line arguments before that boot, and nothing validates them:

setenv bootargs_append 'cma=72M init=/bin/sh'
sdk boot_img

That’s it. The kernel boots its normal squashfs root filesystem, but instead of running the vendor’s real init system, it drops straight to a BusyBox ash shell as PID 1 — fully root, no login, no password, nothing persisted (since we never saveenv, this reverts to the normal boot on the next power cycle). This became the base working environment for essentially the entire project.

Two gotchas showed up immediately:

  1. The hardware watchdog resets the board after about a minute, because init=/bin/sh never feeds it (the real init system normally has a dedicated watchdog-feeding service, wdtd.sh, running very early). Fix, run as the very first thing after getting a shell: �CODE2� V is the magic-close character that disarms the Broadcom watchdog driver cleanly. Follow it with a tiny background loop that writes to it every 10 seconds, just in case something else re-arms it.
  1. USB isn’t live in this minimal boot. The USB PHY power-up module (/lib/modules/4.19.294/extra/bcm_bca_usb.ko) and usb-storage/xhci-plat-hcd all need loading by hand — none of this is in modules.dep for the vendor’s out-of-tree modules at all; load order is only encoded in the vendor’s own (never-run, in this boot path) init scripts.

Backing up the whole eMMC, over USB

Before touching anything, I wanted a full backup. Over raw UART that’s impractically slow for 3.6 GiB, so the plan was: get USB mass storage working in the minimal shell, then dd everything onto a USB stick plugged straight into the router.

A few things bit along the way:

  • The kernel has no exFAT support — the first stick I tried, pre-formatted exFAT, just sat there unmountable. Switched to a blank ext4 stick instead.
  • BusyBox’s mount -o remount,rw silently fails on this kernel’s ext4 driver (it passes a relatime mount option the kernel rejects) — umount and a fresh mount -o rw works around it.
  • No od, wc, cat -v, base64, or blkid in this BusyBox build; dd, gzip, sha256sum, xxd and hexdump (from a fuller toolset found elsewhere on the real rootfs), ifconfig/ip, wget, curl, tftp, nc, fdisk are all present.

With USB sorted, the backup was three dd passes — mmcblk0boot0, mmcblk0boot1 (4 MiB each), and the full 3.64 GiB user area — each verified by hashing the source device and the resulting image file separately and comparing. (Lesson: reading 3.6 GB back off a USB stick to verify it takes noticeably longer than writing it did; budget for that.) RPMB wasn’t dumped; it needs an authentication key I don’t have, and nothing in this project needed it.

Two copies of the backup now exist, on a USB stick and on the laptop, both checksum-verified against the live device. Everything that follows is reversible because of this.

Getting OpenWrt to boot

The realistic goal, decided early: mainline OpenWrt has no target for the BCM96766 at all – I checked the current release tree directly, nothing. Writing one from scratch would mean reimplementing the DDR controller bring-up, the PMC, the eMMC controller, the Archer packet-offload engine, and the AN8855 switch glue, entirely from binary reverse-engineering, with zero vendor source available (no GPL source-code offer exists anywhere in this firmware as of the time of writing). For scale: Linux’s one genuinely open driver for a comparable chip in this family, the AN8855 switch, took over a year and more than twenty patch revisions from an experienced upstream kernel developer, working with a different vendor who at least cooperated. Writing a whole SoC BSP blind is not a realistic solo undertaking.

So: keep the vendor’s already-working, already-signed-off kernel and device tree. Replace only the userland. The vendor kernel already has everything procd (OpenWrt’s init) needs – CONFIG_NAMESPACES, cgroups, overlayfs, devtmpfs, ext4, loop devices, all present, confirmed by pulling the live .config via gunzip -c /proc/config.gz. A quick ABI check (readelf -A on a vendor binary) confirmed soft-float EABI, matching OpenWrt’s armsr/armv7 target build exactly.

OpenWrt ships a prebuilt image for exactly this scenario – openwrt-25.12.6-armsr-armv7-generic-ext4-rootfs.img, a 104 MiB plain ext4 filesystem meant to be written straight to a block device and booted via root=, with no squashfs-plus-overlay switch_root dance needed. Its /etc/inittab already has an entry for ttyAMA0 – the exact UART this board’s console uses – so it needed zero editing.

Using the spare bank (bank 1) as the target, leaving the running stock bank (2) completely untouched:

dd if=/dev/mmcblk0p5 of=/dev/mmcblk0p3 bs=1M      # copy the known-good kernel/FDT onto the spare slot
dd if=<usb-stick>/openwrt-....img of=/dev/mmcblk0p4 bs=1M   # write OpenWrt's rootfs onto the spare slot

then, from U-Boot:

setenv bootargs_append 'root=/dev/mmcblk0p4 rootfstype=ext4 rootwait rw'
sdk boot_img 1

sdk boot_img 1 boots bank 1 specifically, without touching the metadata/commit state — so a plain power cycle, with no further action, always lands back on the stock firmware. This is a one-off test boot, not a bank switch.

It worked first try:

OpenWrt 25.12.6, r33311-981c978eff Dave's Guitar
root@OpenWrt:~#

A real procd/ubus OpenWrt userland, running on this SoC’s own vendor kernel, over the serial console. No Ethernet yet – deliberately not attempted in this first test, to isolate variables.

Ethernet: the kernel panic, and the long way round

Loading the vendor’s Ethernet module chain under OpenWrt (same .ko files, copied in from the read-only-mounted stock rootfs – same kernel build, so the module ABI matches exactly) goes fine, right up until the actual driver:

insmod bcm_enet.ko

→ a hard kernel panic. Full ARM backtrace, tainted kernel, forced reboot in three seconds. The crash backtrace pointed at two symbols: _phy_drv_init and phy_drv_serdes_146class_init_lock. Checking bcm_enet.ko‘s own symbol table showed neither of them actually exist in that module — they’re kernel-builtin symbols, confirmed by cross-checking the live kernel’s /proc/kallsyms (c0922504 t _phy_drv_init, address in the 0xc0... vmlinux range, not the 0xbf1... module range). So this wasn’t a missing-module problem at all: bcm_enet was calling into a SERDES PHY-class framework compiled directly into the kernel, and some piece of that framework’s internal state wasn’t set up the way the driver’s probe path expected.

The device tree detour

With the router’s entire eMMC backed up, I could work entirely offline against the backup image. The FIT image inside the boot partition is itself a device-tree-structured container (U-Boot’s “Flattened Image Tree” format), parseable with the same FDT-walking logic used for the main device tree – so I wrote a small parser and found the real port topology:

port_gphy    reg=0  phy-mode=gmii    status=okay
port_sgmii0  reg=5  phy-mode=serdes  status=okay
port_sgmii1  reg=6  phy-mode=serdes  status=okay
port_imp     reg=8  phy-mode=gmii    status=okay   (management/CPU port)

Both SERDES ports – the two “2.5G WAN/LAN” ports on the rear panel — share the PHY-class code path that was crashing. The devicetree status property is a standard way to disable a node; "okay" and "disabled" are both five bytes including the terminator, and "fail" is a value the kernel treats as equally unavailable and is also exactly five bytes – meaning a two-port fix could, in principle, be a trivial in-place byte patch with no FDT restructuring at all.

It wasn’t quite that simple: FIT images store a SHA-256 hash of each sub-image, and U-Boot checks it. Patch the device tree, and the stored hash no longer matches – Bad Data Hash, followed by a hang that needs a hard power-cycle. The actual fix needed two patches: the five bytes of the status string, and the stored SHA-256 of the whole device tree blob, recomputed and written to its own location in the FIT header. Both applied only to the spare bank’s boot partition – the running stock bank was never touched.

With one SERDES port disabled this way, bcm_enet loaded clean. A genuinely new milestone: the first physical Ethernet link lights of the whole project, auto-negotiated at 1000 Mb/s full duplex, confirmed on the actual hardware.

The correction

Later the same day, while working on Wi-Fi in parallel (see below), I loaded the Wi-Fi driver prerequisite chain – hnd.ko and friends – before bcm_enet, out of simple necessity (it turns out bcm_enet and the Wi-Fi driver share dependencies; more on that below). With that load order, bcm_enet loaded cleanly with the device tree fully reverted to its original, unpatched state – both SERDES ports enabled, original hash restored, no hack in place at all.

That was a real “oh” moment: the device-tree patch was never the actual fix. Something in the Wi-Fi prerequisite chain – almost certainly hnd.ko, Broadcom’s shared hardware-abstraction module – populates the same kernel-builtin PHY-class state that bcm_enet‘s probe path needs, as a side effect of its own initialisation. Loading it first was the real fix, and it’s much cleaner: no FIT-image patching needed at all, and all three wired ports are available simultaneously rather than having to sacrifice one.

I’m leaving the device-tree-patch story in this writeup rather than editing it out, because it’s honestly representative of how this kind of work actually goes: a plausible, working-seeming fix that turns out, on broader testing, to have been coincidental.

The part that was still broken — and then wasn’t

With real PHY-level link established – auto-negotiation correct, LEDs on, speed and duplex both correctly negotiated – actual traffic still didn’t pass. Sending a ping got no reply, in either direction. The question was whether this was a signal-integrity/calibration problem or something else.

A previously-undocumented debug interface answered that cleanly:

echo 'stats 2' > /proc/driver/enet/cmd      # argument is a MAC index, not an interface name
dmesg | tail -n 40                           # output goes to the kernel log, not back to the proc file

This gives the full hardware MIB counters per port. The result was unambiguous: rx_dropped equalled rx_packet exactly, across every traffic class and every frame-size bucket, with zero FCS, alignment, fragment, jabber, or overflow errors. The switch hardware was receiving perfectly clean, valid frames and discarding every single one before they reached Linux’s networking stack.

I spent a long time tracing this in disassembly, following a hooks-table early-return inside bcm_enet.ko‘s enetxapi_rx_pkt, convinced the bug lived somewhere in Broadcom’s proprietary Archer/Crossbow packet-acceleration engine. It didn’t. The actual fix was absurdly small, and I only found it by going back to the vendor’s own debug CLI (ethswctl) and working through its command list methodically rather than guessing inside a disassembler:

ethswctl -c hw-switching -o enable

That’s a global switch-fabric enable, independent of any per-port setting, VLAN membership, or STP state – and it was simply off. Our manual boot path never calls it, because it’s normally asserted by a proprietary userspace management daemon during a full stock boot, which we skip entirely by booting straight to a shell. One command. Immediate effect: the next hardware MIB read showed rx_dropped: 0, and the first real ping (10.99.99.2 ↔ 10.99.99.1) came back clean – 20/20, 0% loss, ~0.7 ms RTT.

(There’s a sharp gotcha hiding in the same debug tool worth flagging: ethswctl -c portctrl -i <if> has no pure query mode. Omitting its -v flag doesn’t read the port’s state – it silently defaults to -v 0 and disables the port. I “checked” a port’s status this way more than once and immediately un-did my own fix by doing so.)

With that one flag in place, all five physical Ethernet ports work: the two SERDES-driven “2.5G WAN/LAN” ports on the rear panel (driven by the SF2 fabric directly), plus the three plain Gigabit LAN ports (driven by a separate AN8855 switch chip, confirmed via the MediaTek/Airoha mt753x lineage hinted at by its own CLI tool, /bin/switch) — tested with sustained TCP throughput, not just ping.

Full per-port VLAN isolation, for free

The AN8855 turned out to have a complete, working control path that I’d initially assumed didn’t exist. /bin/switch talks to a Generic Netlink family (an8855_nl_family) compiled straight into bcm_enet.ko – confirmed by grepping /proc/kallsyms for an8855_* symbols (an8855_reg_read, an8855_hw_reset, an8855_gsw_nl_init, and so on). It’s a genuinely capable tool: register-level read/write, full clause-22/45 PHY access, MAC/ARL table management, port mirroring, a complete ACL engine, and the important part – full 802.1Q VLAN control (vlan dump/set, per-port PVID, egress-tag modes).

Better still, I found /etc/switch-airoha.sh – the vendor’s own AN8855 setup script, sitting unused on the stock rootfs because our manual boot path skips vendor userspace init entirely. Running it directly configures exactly what you’d want from a router like this: one AN8855 port is a tagged uplink trunk to the SoC, and the other three are each an untagged, isolated member of their own VLAN. Confirmed by moving one cable between all three physical LAN jacks in turn, creating a standard Linux 802.1Q sub-interface (eth0.1/eth0.2/eth0.3) for each VLAN, and getting a clean, independent ping on each one. No DSA kernel driver involved at all – this is standard 802.1Q tagging over a single physical uplink, handled entirely by the switch chip itself.

One command found by deep-diving this same tool turned out to be the single most dangerous thing in this whole project: switch ... reset visibly reset the real chip (confirmed by a port’s link light dropping instantly) – but the very next call into any AN8855-related code afterward hung the kernel completely, uninterruptibly, immune even to Ctrl-C. Recoverable only with a full power cycle. Everything else about this tool, including register writes, has been completely safe; reset specifically never gets called again.

Wi-Fi: solved, and a real client connected

(The next several sections were the previous day’s “equally unresolved” story – kept below because the dead end and the eventual fix are both worth reading. Skip ahead to “The actual fix” if you just want the resolution.)

The dead end

The Wi-Fi driver has the same “nothing’s in modules.dep” problem as Ethernet – the real module load order only exists encoded in a vendor init script (bcm-wlan-drivers.sh) that never runs in the minimal boot path. Recovered from reading that script directly:

wlshared → firmware_class → cfg80211 → hnd → bcmmcast → emf → igs → bcm_pcie_hcd → wl

with real parameters (intf_name=wl%d instance_base=<n> for wl) also recovered from the same script.

One genuinely surprising discovery: Wi-Fi and Ethernet are not independent subsystems on this SoC. wl.ko needs bcm_pcie_config_bar_addr/bcm_pcie_map_bar_addr from bcm_pcie_hcd.ko – and bcm_pcie_hcd.ko itself needs enet_init_done, an export from bcm_enet.ko. Trying to test Wi-Fi in true isolation, without any Ethernet modules loaded, hits a hard dependency wall immediately. They share the same underlying packet-acceleration fabric.

With the correct module chain and the Ethernet prerequisite loaded first, wl.ko loads with zero missing symbols – real, measurable progress. The actual hardware attach still fails, though:

si_doattach: Embedded WLAN core (devid:0x6039) pseudo-PCI ...   <- succeeds
M2MDMA / BME / M2M ring alloc ...                                 <- all succeed
M2MDMA: core 0/1 deinit                                           <- rolled back
wl driver 17.10.369.39076 (...) failed with code 15

Disassembling wl.ko traced this to wl_pci_probe calling wlc_attach(..., &err); on failure it prints exactly this message, with err (15) read back through an output parameter. wlc_attach is the actual radio/firmware/calibration attach routine – and it is, and apparently always has been, completely closed. I confirmed this isn’t specific to our build by checking the equivalent open-source glue code from the long-running broadcom-sta Linux driver project: the exact same call pattern exists there too (wlc_attach(..., &err) → printf("... driver failed with code %d", err)), with wlc_attach itself still a sealed blob even in that project, across every chip generation it’s supported. There has never been a public table mapping these error codes to causes.

I tried restoring the device’s real NVRAM/calibration data properly, via the actual supported mechanism rather than guessing – /bin/nvram kernelset /etc/wlan/nvram/HT6766BDM.nvm (the nvram binary has an alarming ~30 shared-library dependencies, but they’re all just .so files already present on the vendor’s own rootfs; nothing needs to be running, so it executes fine standalone, prints restore done!, and is a clean, safe way to apply calibration data, unlike the ad-hoc route described below). It made no difference – same error 15 before and after, so whatever’s missing isn’t (just) calibration.

At the time, this looked like the Ethernet story before its resolution: genuine progress, blocked on an opaque, closed function with no public reference anywhere. I even tried the obvious alternative driver, dhd.ko (Broadcom ships two WLAN drivers historically) – it loaded cleanly but explicitly rejected this chip’s PCI device ID (dhdpcie_pci_probe: chipmatch failed!! Unsupported vendor 14e4 device 6039), conclusively ruling it out: dhd.ko is built for discrete PCIe WiFi dongles, not this SoC-integrated radio, so wl.ko genuinely is the correct driver, and the error 15 was a real problem inside it.

The actual fix

The breakthrough came from asking the obvious question I’d somehow skipped: why can’t we just look at the vendor’s own boot process for how it brings Wi-Fi up, given it demonstrably works in stock firmware? I’d read the Wi-Fi driver load order script already, but never the NVRAM population script, /etc/init.d/hndnvram.sh.

It calls a function, nvram_mfg_conf_mlo(), that runs a real binary (wifi_init_mlomode, deep in the vendor’s TR-069/CMS management framework, too heavy to replicate standalone) to get a numeric “MLO mode” value, then uses it to write a wl_mlo_config=... line into the NVRAM settings file – before the calibration restore we’d already been doing correctly. Checked the raw calibration blob directly: it contains no wl_mlo_config entry at all. For context, MLO (Multi-Link Operation) is a genuinely core Wi-Fi 7 feature (using multiple bands simultaneously for one client connection), and this chip is Wi-Fi 7 hardware. A missing, uninitialised MLO link configuration is an extremely plausible reason for a hard attach failure on exactly this kind of radio.

Read the small helper script (mlo_nvram_setting.sh) that consumes that mode value rather than replicating the whole binary chain: mode 1 sets wl_mlo_config="0 1 -1 -1"; anything else leaves it at "-1 -1 -1 -1". Tried the 1 case directly — which meant first discovering that the raw .nvm calibration file isn’t the newline-separated text format I’d assumed; it’s NUL-separated (confirmed with hexdump: ... $Rev: 83751 $\0boardnum=1780\0 ...), while the plain-text file the vendor’s own scripts edit with sed is a different, converted representation. tr '\0' '\n' converts it cleanly. Appended the one missing line, ran the real restore mechanism (nvram kernelset), and loaded wl.ko.

Both radios attached immediately, with zero errors. wl0 (BCM6039, 4×4) and wl1 (BCM6038, 2×2) both registered real network interfaces, both explicitly logging MLO_BA64/MLO_BA256 buffer pool configuration on attach, confirming the MLO subsystem itself was now correctly active, not just skipped. ip link set wl0 up brought the radio fully up: SMAC/CM7 firmware downloaded, PHY DSP firmware downloaded, MAC clock configured clean, with no crash. One missing NVRAM variable was the entire root cause of the WiFi blocker, from the very start of this project.

A real phone, a real connection

Getting an access point running from here hit two more real bugs, each worth its own paragraph:

Wrong band. My first hostapd config asked for 2.4 GHz (hw_mode=g) and got “Could not determine operating frequency” – because wl0 was already sitting in AP mode on channel 36, 5180 MHz, by default. Matched the config to the hardware instead of the other way round, and the AP started cleanly, genuinely visible over the air from a laptop’s own Wi-Fi scan (correct BSSID, correct channel, WPA2).

Stuck handshake. A real phone associated and got through message 2 of the WPA 4-way handshake cleanly (so the passphrase was right), but message 4 never arrived back, hostapd timed out and disconnected, every single retry. Root-caused to forcing pure legacy 802.11a mode on a chip that’s natively Wi-Fi 7/EHT: the driver’s key-install path evidently isn’t reliable in that mode. Adding ieee80211n=1 (ordinary HT mode, nothing exotic) fixed it on the very next attempt – EAPOL-4WAY-HS-COMPLETED, genuine two-way traffic counters climbing.

The only thing left after that was DHCP – the phone reported “timeout, could not connect” for a few minutes even though it was fully authenticated and passing real traffic at Layer 2, simply because nothing was serving leases on the Wi-Fi interface yet. A scoped dnsmasq instance later: DHCPACK in the log, a real lease handed out, and confirmation, in person, on the phone: it works.

Porting it all onto OpenWrt itself

Everything above was proven on the vendor rootfs, driven by hand over UART. The real goal is OpenWrt with all of it working unattended, so the next step was converting the whole manual sequence into real OpenWrt /etc/init.d services.

OpenWrt runs on the exact same vendor-built kernel as the stock firmware (only the bootloader’s root= argument differs), so the proprietary .ko files are 100% kernel-ABI compatible and insmod under OpenWrt with zero changes. The vendor’s own CLI tools (ethswctl, switch, nvram, hostapd) are a different story – they’re glibc-linked, and OpenWrt itself is musl. Copying the glibc runtime pieces (ld-linux.so.3, libc.so.6, and around forty other shared libraries) straight into OpenWrt’s real /lib, alongside musl’s own differently-named equivalents, turned out to just work for most of them. One genuinely nasty exception: nvram‘s dependency chain pulls in libgcc_s.so.1 — a filename musl also ships, at the same path, with an incompatible ABI, producing a cryptic internal error from the dynamic linker. Fixed by shadowing just that one library in an isolated override directory and replacing the real binary with a tiny wrapper that explicitly points the dynamic linker at it.

A live, unattended cold-boot test caught one more real bug the hard way: hostapd failing with libatomic.so.1: cannot open shared object file – a transitive dependency of libcrypto.so.3 I’d missed entirely by hand-tracing the dependency list. Copied the one missing file (mounting the vendor’s read-only rootfs directly from inside the running OpenWrt session, no reboot needed) and re-ran the exact same cold boot: both Wi-Fi radios came up and both successfully joined the LAN bridge automatically, confirmed in the system log, zero manual intervention. Wi-Fi is now a genuinely automated, reboot-proof OpenWrt feature.

The one thing that wasn’t reliable: wired LAN under OpenWrt (now root-caused)

The wired side of this same automation is written, and is proven correct on the vendor rootfs, the exact same module chain and VLAN sub-interfaces work every time. Under OpenWrt specifically, there’s a genuine, reproducible bug: netifd (OpenWrt’s own network management daemon) can never successfully create the LAN bridge itself. Isolated this properly rather than guessing: netifd’s own debug log shows precisely which internal call fails:

system_bridge_addbr(1573): Error adding bridge 'br-lan': -10

– and manually performing the exact same operation (ip link add br-lan type bridge, or the older brctl addbr) works instantly, every time. So the kernel can make bridges; something about netifd’s particular request was being refused. The wired side worked completely reliably by hand; it just wasn’t automated.
Update: root-caused, from the firmware dump alone, without touching the router. The clue was that -10 isn’t a Linux errno. netifd uses libnl-tiny, whose own error code 10 is NLE_OPNOTSUPP, so the kernel had answered -EOPNOTSUPP. The vendor kernel embeds its own build configuration (IKCFG), and extracting it from the image shows CONFIG_BRIDGE_VLAN_FILTERING is not set (nor is the upstream CONFIG_BRIDGE_IGMP_SNOOPING; Broadcom ships its own snooping code instead). The image also carries a kallsyms table, so vmlinux-to-elf could rebuild a symbol-named ELF from the raw blob, and disassembling br_changelink shows exactly what happens: if the netlink request contains an IFLA_BR_VLAN_FILTERING attribute at all (even with the value 0) it returns -EOPNOTSUPP. A kernel built without the feature doesn’t ignore the attribute, it refuses it.
netifd’s system_bridge_addbr() sends that attribute unconditionally:

nla_put_u8(msg, IFLA_BR_VLAN_FILTERING, !!cfg->vlan_filtering);

with no configuration option to leave it out. ip link add and brctl never send it, which is why they always worked.
The fix is a one-instruction binary patch: NOP out that single nla_put_u8 call in the stripped netifd binary (a 4-byte change, found by following the "Error adding bridge" debug-string reference back to the function). The patched binary is built and verified by disassembly, but I haven’t run it on the router yet, as this analysis was done away from the hardware. Whether it fully fixes the bridge, and whether other netifd calls trip over the same kernel gaps, is still to be confirmed.
Update, same day: tested on the hardware, and it works. As a control, the original netifd given a bridge-only device section never created the bridge; the patched binary created it over netlink with no error. With the init scripts no longer building br-lan by hand (and no longer pre-creating the VLAN sub-interfaces, which made netifd skip them), a plain cold boot now has netifd create br-lan itself with the three LAN ports, the extra 2.5G port and both Wi-Fi radios as members, at 192.168.1.1/24. A laptop in LAN port 3 got a DHCP lease and pinged the router at under a millisecond with 0% loss and no receive drops. With sdk metadata 1 the router now boots OpenWrt by itself with no U-Boot intervention, and stock firmware is one sdk metadata 2 away.
One more thing worth knowing: with apk‘s stock packages the stock firewall4 is built on nftables kernel modules for Linux 6.12, which cannot load on this 4.19 vendor kernel, so NAT and firewalling still need to be done with the vendor’s own iptables modules. That is next.

A mistake worth documenting honestly

Partway through the Wi-Fi investigation, trying to supply calibration data the wrong way, I wrote roughly 2,500 lines of real board NVRAM data into /proc/nvram/set – a kernel interface that turned out to be capped at 16 KB, far smaller than the ~76 KB calibration file. This didn’t just fail cleanly: it left malformed entries in the persistent flash-backed NVRAM store (not RAM-only, as I’d assumed), which then caused a flood of kernel warnings on every subsequent boot, severe enough in one case to blow the boot-time watchdog before a shell was even reachable.

The fix was a straightforward image restore – the corrupted region lives entirely inside the small mmcblk0boot0/mmcblk0boot1 hardware partitions, both of which were in the very first backup taken, before any of this. dd-ing the pristine 4 MiB images back (after clearing the kernel’s force_ro write-protect flag on those block devices, then re-setting it afterward) restored normal boot behaviour completely, checksum-verified against the original backup. Nothing was lost; the stock bank’s reliability as a fallback was never actually compromised, just the thing I’d been testing with recklessly. The lesson – verify the actual capacity of a kernel interface before bulk-writing to it, and never assume a knob called /proc/something is RAM-only without checking – earned its place in this writeup.

Where this stands

  • Rooted: completely, trivially, via an unauthenticated U-Boot bootarg injection. No exploit needed.
  • OpenWrt: genuinely boots, on the real hardware, on a spare bank that leaves stock firmware completely intact and recoverable with a plain power cycle.
  • Ethernet: all five physical ports working with real, sustained traffic – the two SERDES “2.5G” ports and the three AN8855-driven LAN ports, the latter with full per-port 802.1Q VLAN isolation. Proven solid on the vendor rootfs; the same automation under OpenWrt itself hits a reproducible netifd bridge-creation bug, now root-caused (the vendor kernel has no bridge VLAN filtering and rejects netifd’s unconditional request for it); a one-instruction binary patch fixes it, verified on the hardware (see below).
  • Wi-Fi: fully working. Both radios attach cleanly (the real fix was a single missing NVRAM variable, wl_mlo_config, that the vendor’s own boot process sets and ours never had). A real phone associated, completed a WPA2 handshake, and got a DHCP lease – confirmed in person. Automated as a proper OpenWrt /etc/init.d service, reboot-proof, confirmed working unattended.
  • LuCI: reachable and rendering correctly over the router’s own Wi-Fi/Ethernet, the moment Ethernet started passing traffic – nothing extra needed installing.
  • Full switch/VLAN control: a complete, working control path for the external AN8855 switch chip (register access, ACLs, full VLAN management) – not a kernel DSA driver, but genuinely capable and confirmed live.
  • Full eMMC backup, taken and verified before any of this, in two separate locations – meaning everything above is undoable, and the default boot bank is still deliberately left as stock firmware until the wired-LAN automation under OpenWrt is sorted.

This has gone from “rooted, with a working OpenWrt shell and nothing else” to “every subsystem the original goal named is individually proven working on real hardware,” in one extended session. What’s left is less “can this work at all” and more “stitching it into one unattended boot.” I’ll keep this updated as it moves.

Posted on — Leave a comment

JVC CV-F503PAL Viewfinder

EVF Bottom
EVF Bottom

It’s time for another CRT-based post! This time it’s a Matsushita 40CB4-based viewfinder from 1980. These came from JVC colour tube cameras, and are physically massive! I’ve already worked out the pinout on the multicore cable here & attached a usable connector.

Information Label
Information Label

There’s lots of information on the bottom label of this unit, including a notification in German that the X-Ray emission from the device is shielded, and the maximum CRT acceleration voltage is 8kV. This last point is a bit strange, since the 40CB4 datasheet states a maximum design voltage on the final anode of 6kV. I did measure the voltage at the anode cup, and it’s stable at 7.15kV!

Internal Overview
Internal Overview

Popping a couple of screws out & removing the enormous eye cup allows the top cover to come off. This unit is very tightly packed inside, with 3 PCBs! The magnifying lens (~45mm diameter) & mirror on the left enlarge & turn the image so the camera operator can see it. The CRT’s at the top, with a copper grounding band around the face.

CRT Face
CRT Face

The CRT face is neatly slotted into the plastic housing, with the tally LEDs to the right of it. The legends on the LEDs are naturally printed in reverse, since they’re intended for viewing through the mirror. The optical section is entirely spray painted black for better contrast & stray light control.

Electronics Area
Electronics Area

The other 5″ of the casing is packed with electronics to support the CRT. The bottom PCB even “wraps around” to the right, with copper staples connecting the boards together. The CRT tube itself is hiding inside the deflection yoke and under a foam pad at the top of the unit. It’s secured in place with a copper grounding strap wrapped around the face of the tube, and a spring. A single screw secures the strap to the case. This also provides a local earth for the outer Aquadag coating on the tube, which is the negative plate of the final anode smoothing capacitor. The other plate is formed by the coating on the inside of the CRT glass, and the dielectric is of course the glass itself.
The main anode wire snakes off from the flyback at bottom left to the anode cup at the top of the CRT, insulating the 7kV from everything else.

There aren’t many reasons to jack up the final anode voltage on a CRT, past the design voltage of the tube as JVC have done here. The only plausible one I could think of is to increase brightness of the image, but the Sony 4CB4-based units I have only run at around 3kV, and those are plenty bright enough! The downside here of course, is that with higher energy electrons and a brighter image, the phosphor of the CRT will wear out faster.
Increasing voltage also increases X-Ray emission, but even at the 8kV maximum, such X-Rays would be so weak as to not make it through the CRT faceplate glass, which is loaded with lead anyway.

There’s not much sense in yanking the tube out of this unit, it’s identical to the Sony one’s I’ve done in the past:

Bare 40CB4 CRT
Bare 40CB4 CRT
Voltage Regulator Pass Transistor
Voltage Regulator Pass Transistor

Slotted into a gap above the CRT is a large TO-220 2SD476 NPN transistor, this is part of the power circuit; it’s the series pass element regulating the input 12v down to 9v for all the remaining circuits. The aluminium sheet on the back provides some heatsinking as this part gets warm! Current draw of this unit with no video input is about 260mA.

CRT Removed & Vertical Board
CRT Removed & Vertical Board

Popping the CRT out allows a view of the Vertical & Power Board. This hosts the input linear voltage regulator, and the vertical output control circuitry. Hiding at the back on the right is a NEC µPC1031H2 Vertical Deflection Controller.

Horizontal & Video Boards
Horizontal & Video Boards

Separating the boards reveals the other two PCBs, the Video & Horizontal/HV boards. The bottom board takes care of the Horizontal output, and the lefthand board the video input, sync separation & amplification.

Horizontal Control IC
Horizontal Control IC

The Horizontal section is controlled by a Matsushita AN294 device. Unfortunately I haven’t been able to locate a datasheet for this one. The flyback transformer (Horizontal Output) is on the right, with another smaller transformer I don’t quite know the purpose of. Oddly, there’s no large switching transistor for the horizontal output stage – as the PCB notes the flyback as being a “HVM” this may in fact be more tightly integrated with some of the drive circuitry in the potting. There aren’t anywhere near as many pins on it as a usual CRT flyback has either.
This section also generates the other voltages required by the CRT – 2.8v for the filament, and ~80v & ~400v for the grids.

Video Board
Video Board

A closeup of the video board shows the relative simplicity. Only 4 transistors are doing all the video actions. There is relatively high voltage on here though – an 85v feed from the power supply which is the rail voltage for the video amplifier to the CRT cathode/G1.

Focus & Horizontal Hold Adjustments
Focus & Horizontal Hold Adjustments

There’s a few adjustments available on this unit, here are the Focus & Horizontal Frequency (Hold) pots. Amazingly, even though this unit is about 43 years old at the time of writing, the unit fired straight up when I applied power & a composite video signal, with no adjustments required at all!

Unfortunately there’s no service manual or schematics that I could find on the web for this or the camera it came from, but connections to make this unit work are very simple:

Wire ColourSignal Name
YELLOW+12V DC
BLACKGND
Coax - CoreComposite Video 1v p-p
Coax - ShieldComposite Video GND

There’s another blogger who’s done this particular viewfinder, but they didn’t dig into the unit anywhere near as far as I usually do:

https://hex.ro/wp/blog/matsushita-40cb4-mini-crt/

This blog has a lot of CRT-based viewfinder teardowns, mainly from newer cameras. It’s an interesting read.

Datasheets for the important parts (the ones I could find!) below:



 

Posted on — Leave a comment

DeWalt Clone 18v Battery Pack Teardown

Clone Battery Pack
Clone Battery Pack
Clone Battery Pack

I bought two of these packs for my new DeWalt combi drill, as the branded packs are very expensive and there’s unlikely to be much of a difference in cells used. I was a little mistaken on this, as you’ll see!

Battery Terminals
Battery Terminals

The top of the unit has the battery connections, with all the cell balance lines, along with an ID pin, and a TH pin. The TH pin connects a 10K NTC thermistor up to B+.

Battery Label
Battery Label

The bottom of the unit has the rating & warning label. This claims to be a 6Ah pack, but it’s nowhere even close!

Top Cover Removed
Top Cover Removed

Removing 4 Torx screws gives access to the internals. The cells are all fitted into a plastic holder. There’s a small PCB holding the connector pins, and all the cells connect up to this for the balance outputs. There’s a small PCB on the side of the pack that holds the components for the battery meter.

Connector PCB
Connector PCB

The back of the connector PCB has some passive components, but not much else. There’s the connections for the NTC at the bottom right of the board. There is an IC on this board, on the other side, but without desoldering all the pins, it’s not possible to see properly as it’s mainly hidden by the connector frame.

Battery Indicator LEDs
Battery Indicator LEDs

Not much on the front of the battery meter board, apart from the 3 bright green LEDs and the tactile switch.

Battery Indicator Components
Battery Indicator Components

The other side has a small ST microcontroller, a TL431 shunt reference, and some other passives.

Cell Links
Cell Links

All the cells are linked together with hefty interconnects, as expected for a high current pack. This is laid out as a 5S2P configuration, giving 21V max, 15V flat. Unfortunately I can’t see any markings on the cells – they may be off brand, or pulls from other products.

I figured as I always do with Chinese battery packs that the stated capacity of 6Ah was too good to be true, so I ran my usual cycle tests to see what the real capacity was, and was met with the following results:

Cycle NumberPack APack B
13969mAh3917mAh
23963mAh3947mAh
33961mAh3956mAh
43953mAh3959mAh

As can be seen from the table, these packs are 4Ah, not 6Ah. 2Ah cells sort of make sense for a pack like this, as the high-current capacity cells tend to be a lower capacity.

Posted on — Leave a comment

Clone DCB090 DeWalt USB Battery Adaptor Teardown

DCB090 Clone USB Adaptor
DCB090 Clone USB Adaptor
DCB090 Clone USB Adaptor

Since I got my new DeWalt combi drill, I needed a way to charge the batteries without having to resort to sticking blade terminals into the pack connectors – I didn’t purchase the branded charger, mainly due to cost. I also have a very capable multi-chemistry charger that handles multi-cell lithium packs with no issues, so I saw no need to replicate things. This little gadget was ordered just for it’s main pack connector; I can then use this to make up a charger adaptor cable. What this normally does is allow the use of DeWalt XR battery packs to charge mobile devices via 5v USB outputs, so there’s going to be some kind of DC-DC converter in here. There’s also a “charge level indicator” built in, which doesn’t actually do anything sensible – even on a flat battery pack, showing a single LED on it’s charge indicator shows the full 3 LEDs on this unit.
The remaining feature is a trio of white LEDs to function as a torch, but it’s less than stellar in the brightness department. Given that there’s not much in the way of control inside the battery packs themselves, I reckon this unit could actually overdischarge a pack, causing damage.

Torch LED & Charge Indicator
Torch LED & Charge Indicator

The top of the unit has a large label with windows in for the various LEDs, and a pad covering the tactile switch to operate the torch function.

Label
Label

The label on the side indicates the unit will operate down to 10.8v, good for the 3S packs, as well as the 18/20V packs.

Pack Connector
Pack Connector

Here’s what I was after – the battery pack connector. This has the full compliment of pins for all the balance taps too.

Casing Opened
Casing Opened

Removing a label, and a single screw gives access to the internals. There’s not much in here apart from a large PCB, with a few components.

Main PCB
Main PCB

The PCB is pretty sparse. There’s a microcontroller in the top right corner that does the torch LED switching, and the “battery indicator LEDs”. This is completely unmarked, which is very common now for Chinese microcontrollers. The only way I’m identifying this one is via a decap operation on the IC!
The USB ports have MOSFETs in their negative pin paths, probably to switch off the ports if they’re overloaded. The data pins are bridged together on one port, and connected to the DC-DC converter on the other port.

DC-DC Converter
DC-DC Converter

The main DC-DC converter IC is in the bottom right corner of the board, next to the input pins. This is an IP6503S multi-protocol USB charging converter, with a 24W power limit. This explains why the data pins of one of the USB ports is connected back here – it’s doing some communications with the connected device for fast charging. Chinese datasheet below.

Posted on — 1 Comment

ATC-1000 Serial to IP Converter Teardown

Front Cover
Front Cover

Just a quick teardown this month! This is an industrial RS-232/RS-485 to Ethernet serial converter.Not much to say about the outside of the unit, there’s the DB-9 connector for the 232 interface, and Phoenix connector blocks for the 422/485 interface. The main power input, and the Ethernet jack are on the other side.

PCB
PCB

Under the hood, there’s a pretty densely populated board. The brains of the operation is a IP210T Serial to Ethernet SoC with A/D Converter. This is an 8051 based core, wuth 10/100 MAC. No flash memory here either, only 64KB of OTP EPROM. On the left there’s a few bus transceivers to interface the serial ports, along with some glue logic. At the top we have the Ethernet magnetics, configuration EEPROM for the SoC & a trio of indicator LEDs.
Power supplies are dealt with via an LM2576-3.3 DC-DC buck converter, providing the main 3.3v rail for the logic.

Posted on — Leave a comment

Chinese LED Projector Teardown

Cover Removed
Cover Removed

Another Chinese eBay teardown! This is a “720p” LED projector, available from nearly everywhere for very little cash. But they are very little cash for a reason – they’re total shit. The resolution as stated is a blantant lie – the LCD panel used in these is usually around 320×240, nowhere near the 1280×720 as stated. Being small & portable, there’s very little lighting power available, and they barely work to a level watchable without eye strain even in a completely dark room. You literally get what you pay for! Above is the projector with the top removed, showing the main board, which is fairly densely populated.

Mainboard Top
Mainboard Top

The main processor appears to be an MST3M182VGC-LF-Z1, a SoC designed specifically for LCD TV applications. This runs the internal firmware from a serial flash, a PN25F32 32Mbit (4MB). As this projector has the capability to play files from USB & SD Card, as well as from A/V inputs, there’s an Alcor Micro AU6438BS USB 2.0 Single LUN Flash controller on the right to deal with the MicroSD slot interfacing. The left top corner of the board is completely dedicated to power control, with various switching converters & transistors.

Mainboard Bottom
Mainboard Bottom

The bottom of the board is also dedicated to the remaining portion of power control – more switching regulators here generate the voltage rails required for the SoC, along with LED drive.

Optical Path
Optical Path

Removing the board allows access to the optical components of the projector.

LCD & Lenses
LCD & Lenses

Here the LED module has been removed from the casing, better showing the optical arrangement. There’s a Fresnel lens, then a polariser, the LCD panel itself, another lens, then the final turning mirror to the objective lens.

Turning Mirror & Objective
Turning Mirror & Objective

Here the rest of the optical components have been removed, showing the objective with it’s helical focusing track, which moves the lens, and the turning mirror. Behind the mirror is the pitiful speaker.

Optical Components
Optical Components

Here the main components are laid out, with lenses either side of the LCD & polariser.

LED Module
LED Module

Now onto the light source of the projector – the LED module. This is buried inside the module with a conical reflector, and a small heatsink on the back.

Reflector Removed
Reflector Removed

Removing the reflector shows the LED itself, with a thermal fuse in series for protection. The LED is screwed to the aluminium heatsink for cooling – my guess is this is roughly a 6W LED, with 3 series pairs of dies in parallel.

Posted on — Leave a comment

Upp! Hydrogen Fuel Cell Teardown

Upp! Hydrogen Fuel Cell
Upp! Hydrogen Fuel Cell

After watching Mike’s Electric Stuff’s video on these a while back, I figured it was time to grab one from eBay & see for myself how pointless a tech these are. As far as I am aware, these units are no longer available, the domain name redirects to a company site with no mention of them, and getting cartridges refilled might not be possible without some DIY engineering. These are a small portable Hydrogen-powered PEM (Proton Exchange Membrane) Fuel Cell unit, with a USB output port for charging mobile devices. There’s quite a few vents on the sides of this device, as there has to be an airflow through the PEM Fuel Cell itself, and the only control interface is a single button on the front of the unit.

Gas Cartridge
Gas Cartridge

The Hydrogen gas is stored in a cartridge, filled with Hydralloy C5 metal hydride powder. These would be exchanged for a full one when all the gas has been used, at a cost of about £6. (Extra cartridges apparently cost about £50!).

Cartridge Valve
Cartridge Valve

The top of the cartridge holds the main valve, and some contacts. The gas is permitted to flow from the storage hydride by means of the two brass pins on either side of the seal – when these are both pushed down by pins moulded into the bottom of the main fuel cell unit, the internal valve is opened. The contacts connect to an internal PCB with a single EEPROM.

Cartridge Magnets
Cartridge Magnets

The cartridge is attached to the fuel cell with magnets – there are a pair of very powerful NdFeB magnets behind the main steel plate on the top, and a matching pair inside the bottom of the fuel cell assembly.

Cartridge EEPROM PCB
Cartridge EEPROM PCB

Removing a label allows access to 4 screws, which hold the top assembly onto the pressure vessel section of the gas cartridge. Here is the internal PCB with it’s EEPROM, and the large brass screw which may be for regulating the gas flow rate.

Gas Cartridge EEPROM
Gas Cartridge EEPROM

Removing the PCB allows us to see the EEPROM itself – a 2kBit part, which contains information like remaining gas charge, and serial number. When the cartridge reads empty according to this EEPROM, the cell will stop functioning. Luckily however, it is happy to operate without this PCB even being present – I expected the unit to spit & error & shut down if it couldn’t communicate over the I²C bus with this memory.

Pressure Relief Valve
Pressure Relief Valve

Removing a screw in the base of the casing (hidden under a label) allows the plastic shell to come off, revealing the aluminium pressure containment to be seen. There’s a pressure relief valve on the side here, and some warnings about what not to do with the thing.

Pressure Vessel Info
Pressure Vessel Info

Some more info on the other side, with the ISO standard this cell is rated to, and the 20 bar Rated Charging Pressure. There is also a stamp indicating how long the certification of the vessel lasts. This one is rather out of date…

Charging Valve
Charging Valve

The opposite side of the unit has another label covered in warnings, and a recessed charging valve. It’s an interesting one this – there are no threads, just a brass valve with a depressable pin in the centre to allow the gas to flow. Since this needs to be charged at 20 bar, a special jig would be required, to hold any charging adaptor in place while the gas is injected. There’s no chance of getting the official part for connecting to this, so I intend to machine a brass adaptor to connect here for charging.

USB End
USB End

The top end of the fuel cell unit has a single USB port, rated to 1A according to the rating plate:

Rating Plate
Rating Plate

Standard rating plate with some regulatory markings, and output power.

Gas Inlet
Gas Inlet

Here is the bottom of the fuel cell unit, which magnetically couples with the gas cartridge. The two pins either side of the gas port are visible, and it is these which open the valve on the cartridge. The 5 gold-plated contacts at the edge make contact with the spring terminals on the EEPROM PCB on the gas cartridge for communications. They are also used with a separate base for external charging of the LiPo cell contained inside. More on this later.

Internal Frame
Internal Frame

The main body of the cell is secured together with internal clips – and are not intended to ever be opened without damage, but here is the core of the unit. There’s a large Lithium Polymer cell on the top of the main board, which is required to actually get the unit going in the first place. I suspect this is also used to buffer the output from the PEM cell itself, and provide the maximum of 1A output current. (My unit would not charge a device even at 500mA when it arrived, until the internal cell was charged up – a red LED was lit just before the unit shut itself down).

USB Output
USB Output

The top of the board has the single user button & the USB port. This port is enabled for communications – there used to be an app for phones that would show some statistics about the unit to the user.

PEM Fuel Cell Connections
PEM Fuel Cell Connections

Turning the unit over shows the PEM Fuel Cell itself, a stack of 5 plates in series. There are 5 connections into the cell unit – main power output terminals, and a pair of terminals for a thermistor, which is buried right in the centre of the cell at the top, to measure operating temperature.

Cooling Fans
Cooling Fans

The other side of the frame holds two tiny fans, which waft some air through the channels in the fuel cell plates. This will both be for cooling, and to ensure that Oxygen can get into cell assembly to react with the incoming hydrogen.

Fuel Cell Frame
Fuel Cell Frame

The fuel cell unit clips off the top of the main frame, exposing the two gas control valves. The one on the left regulates the gas input from the cartridge, while the one of the right is regulating the gas outlet to atmosphere. There is also the port of a pressure sensor popping up to the left of this outlet valve.

Fuel Cell Gas Ports
Fuel Cell Gas Ports

Here’s the bottom of the fuel cell module, with a pair of rubber seals on the gas ports, which interface with the faces of the valves. The H² gas inlet port is on the left.

Bare PEM Cell
Bare PEM Cell

Some more unclipping of plastic frames allows the bare module to be removed. This is a really heavy-gauge piece of steel to clamp the module together, secured by spring clips.

PEM Cell Plates
PEM Cell Plates

Here’s the edge of the module, showing the individual plates. There are silicone seals between them to seal the gas ports, and a thin PCB material at the top & bottom as electrical contacts. The plates being stacked together means these are all in series, providing about a 4.6v output voltage.

Cartridge Adaptor Plate
Cartridge Adaptor Plate

Here’s the back of the cartridge adaptor, with the pair of magnets to match the ones on the gas cartridge.

Gas Inlet
Gas Inlet

This rubber grommet seals onto the metal plate in the adaptor, sealing the gas inside. The 5 contacts are visible here to communicate with the cartridge EEPROM.

PCB Bottom
PCB Bottom

A bit of de-soldering later, and the board is free from the frame. This is very densely packed board, covered in DC-DC converters of various types. The main microcontroller is a STM32F107 from ST Micro – a 72MHz part loaded with interfaces. There’s a small WinBond EEPROM here too, which from Mike’s video, seems to be used for log data. It would be nice to get access to this board through a serial interface, to see if there’s any engineering options left in the software for some tinkering. The large inductor is part of a synchronous DC-DC converter, the controller IC for such is on the other side of the PCB.
There’s a L324A Quad Op-Amp in the top right corner of the board, next to the USB port, along with a load of discreet transistors spread throughout the board. Some of these transistors will be used for switching the solenoid coils on the gas valves. The other major part on this side of the board is the gas pressure sensor, just to the right of the EEPROM.

PCB Top
PCB Top

The other side of the board has even more components, the Lithium cell protection MOSFETs are at bottom left, the Synchronous DC-DC converter controller, a TPD43000 from Texas Instruments is in the centre. There are more discreet transistors on this side, for driving the solenoids & fan power control.

Control Valve Cores
Control Valve Cores

Not much remains in the frame, other than the gas valves themselves.

This is an interesting piece of tech, but it’s definitely useless – especially in the era of high capacity power banks of up to roughly 40Ah. The gas cartridges that this unit eats through hold approx. 7Ah of capacity, and at £6 a pop, it is an expensive way to charge a mobile device. I will be coming up with a way of recharging the gas cartridge though, which will involve some sideways thinking & machining of brass. More to come on that!

Posted on — Leave a comment

24v DC Industrial Strobe Light Teardown

Industrial Strobe
Industrial Strobe

Here’s something anyone in the industrial sector will recognise – it’s a strobe beacon, which continually flashes with power applied to alert operators of a hazard. These older ones are Xenon tube based, instead of LED, so contain a bit more circuitry & some high voltages.

Xenon Flash Tube
Xenon Flash Tube

Unhooking the lens reveals the Xenon lamp itself, a horseshoe format tube. A high DC potential is applied across the electrodes of the tube, below the ionisation voltage of the Xenon gas inside. When a flash is called for, a very high voltage – several kV – is applied to a 3rd trigger electrode, applied to the outside of the glass. The high electric field generated is sufficient to ionise enough gas to initiate the main discharge between the electrodes. Since the lamp is across a large capacitor, a massive current flows, generating a high-intensity flash.

Insulator Removed
Insulator Removed

Removing the pair of screws which secure the insulator & PCB reveals the board itself, which is of cheap single-sided construction. There’s no isolation on this circuit, between the internal HV side & DC input.

Main PCB Top
Main PCB Top

Flipping the board shows all the components. The largest part here is the main flash capacitor in the middle, a plastic film type, 4.7µF 400v. This will be charged to around 350v before the tube is triggered. Charging of the capacitor is done by the transformer at bottom right, switched by the transistor next to it. There are no ICs in this unit to control any timing of the DC-DC converter, so this is probably based around a blocking oscillator. A smaller capacitor to the top right of the main flash cap is part of the trigger circuit, which is charged through a resistor from the main HV supply. When the voltage on this capacitor reaches a high enough level, the large SCR on the left side of the board switches on, dumping the charge on that capacitor through the trigger transformer, the small yellow device with the white wire. This small transformer generates the high voltage pulse to trigger the flash lamp.

Posted on — Leave a comment

8-Port BNC Video Distribution Amplifier

Front Panel
Front Panel

Time for another eBay special: this time it’s an 8-port video distribution amplifier, with BNC connections designed for commercial/industrial equipment. Not much on the front panel above, apart from the power switch & LED.

Rear Panel
Rear Panel

The rear panel has all the connectors, input is on the left, while the outputs are in the centre. Power is supplied through the barrel jack on the right, 9v DC in this case.

Data Label
Data Label

Not much in English on the data labels, there’s also an authenticity label on the left to make sure you don’t get a fake.

Amplifier Board
Amplifier Board

Taking the lid off reveals a very small PCB, taking up less than a third of the aluminium case! The input stage is on the right, composed of a pair of SOT-23 transistors to buffer the incoming signal. There’s an KST812M6 PNP & an S9014 NPN Epitaxial. The signal is then fed to the output stages, all individual S9014 NPN transistors to the output ports.
The power LED is just poking in the general direction of the hole in the front panel, so this isn’t likely to work very well – it’s going to illuminate the inside of the case more!

Posted on — 2 Comments

Eberspacher D5W ECU Constant Overheat Error

Eberspacher ECU 25 1599 50 00 00
Eberspacher ECU 25 1599 50 00 00

Here’s another Eberspacher control unit, this time from an ancient D5W 5kW water heater. The system in this case is just flaky – sometimes the heater will start without fault & run perfectly, then suddenly will stop working entirely.
The error codes are read on these very old units via an indicator lamp connected to a test terminal. In this case the code was the one for Overheat Shutdown.

Considering this fault occurs when the heater is stone cold, I figured it was either a fault with the sensor itself or the ECU.

Temperature Sensor
Temperature Sensor

The temperature sensor is located on the heat exchanger, right next to the hot water outlet fitting. I’m not sure what the spec is, but it reads exactly 1KΩ at room temperature.

ECU PCB
ECU PCB

The PCB is held into the aluminium can by means of crimps around the edge that lock into the plastic terminal cover. Inserting a screwdriver & expanding the crimps allows the PCB to be slid out.

Casing Crimps
Casing Crimps

The factory date stamp on the microcontroller dates this unit to March 1989 – considerably older than I expected!
Unlike the newer versions that use transistors, this ECU has a bunch of PCB relays to do the high current switching of the water pump motor, fan motor & glowplug.
Overall the board looks to be solidly constructed, with silicone around all the larger components.

ECU PCB Solder Side
ECU PCB Solder Side

Here’s the solder side of the PCB, which has a generous coating of sealant to keep moisture out.

Bad Joint Closeup
Bad Joint Closeup

Looking at the solder joints for the row of relays on the top side of the PCB, it looks like that there’s some dry joints here.
I suspect that years of vibration has taken it’s toll, as the relays are otherwise unsupported. It wouldn’t be possible to use silicone to secure these devices as they are completely open – any sealant would likely stop them from operating.

Resoldered Joints
Resoldered Joints

Using a very hot soldering iron I managed to get the joints to reflow properly, using lots of flux to make sure the conformal coating didn’t interfere with the reflow.

Posted on — Leave a comment

Sony Xperia Z3 50% Battery Problems

Recently my phone decided it was going to die a battery-related death, and having not found much useful information on the Great Google, (all the information I could find, was hinting at many issues from firmware to a faulty motherboard, nobody seems to have actually done any investigation into similar issues), I decided to dig into the phone to try & repair the problem.

Broken Flex
Broken Flex

The phone would work correctly for a while, then with the slightest movement or knock, would spontaneously switch off, and not turn back on without being whacked on a hard surface.
This symptom pointed me at a power connection problem. After removing the back of the phone (glass & heavily glued in place, so an awkward process), This was what I was presented with on the cell flex PCB.
In the above photo, the positive connection to the flex is fractured just after the solder joint with the BMS board.

Flex Repair
Flex Repair

I managed to scrape some of the insulation off the flex PCB & solder a jumper on to restore power. Unfortunately, this repair generated another fault, where the battery level was always shown at 50%, and plugging into a USB supply wouldn’t charge the phone. The other two pins on the cell are for communication & temperature sensing, clearly one of these traces was also broken in the flex.
The above photo has a pair of very small wire tails as well, for connecting an external charger.

50% Battery
50% Battery

Here’s a screenshot of the phone with the original cell, even though it’s at about 4.15v (virtually fully charged). The battery management is having trouble talking to the phone, so for safety reasons, the charging logic refuses point-blank to charge the thing up.

Flex Cable
Flex Cable

The connector on the cell & phone motherboard is absolutely tiny, so I didn’t fancy attempting to solder on any bridge wires to try & bypass the broken flex.

Battery BMS
Battery BMS

The cell BMS has some intelligence on board, besides the usual over-current, over-charge & under-charge protection. The very small IC on the right has a Microchip logo, and the marking FT442, but I was unable to dig up any datasheets. The current sense resistor is directly connected to this IC, along with the main power FET to the left.

BMS Reverse
BMS Reverse

On the other side of the BMS board is another IC, again unidentifiable, and what looks like a bare-die, or CSP IC.

20160625_233656

At this stage I figured the only way forward was to buy a new battery, eBay turned one up for less than £5. Above is the new battery fitted to the phone, datestamped 2014, so definitely old stock.

100% Battery
100% Battery

Booting the phone with the new battery quickly lets me know the fix worked, with a 100% reading & the ability to again charge properly!

Posted on — Leave a comment

Sony Xperia T Teardown

Back Cover Removed
Back Cover Removed

Since this phone has been in my drawer for some time, I figured it was time for a teardown. (It’s never going to see any more use).
The back cover on these phones is easily removed, as it’s just clipped on.

Motherboard
Motherboard

Once the back cover is removed, the Li-Polymer cell is exposed, along with the logic board. Pretty much all of the PCB is under RF shields.

Motherboard Removed
Motherboard Removed
Battery Management
Battery Management

Under the small RF can on the back of the board is the battery management circuitry & the charger. There’s an extra connection to the cell for temperature monitoring. Just under that circuitry is the eMMC flash storage.
Just to the left of the battery circuit is the NFC transceiver IC, from NXP.

Battery Flex
Battery Flex

The cell is connected to the main board with a FFC, with a very small SMT connector, although not as small as the more modern Xperia series phones.

RF Section
RF Section

The other side of the mainboard holds the large RF transceiver section, with a Qualcomm RTR8600 multiband transceiver IC. In the bottom corner is a Skyworks SKY77351-32 Quad-band power amplifier IC, along with 3 other power amplifier ICs, also from Skyworks.

Gyro & Audio Codec
Gyro & Audio Codec

The top corner of the board holds the various sensors, including an Invensense MPU-3050 3-axis gyro. To the right of that is the Audio Codec, a WCD9310 from Qualcomm.

Logic & CPU Section
Logic & CPU Section

Everything is controlled from the last section on the board, with the main CPU & RAM in a PoP (Package-On-Package) configuration. Under the main CPU is the main power management IC, also from Qualcomm. No datasheet for this one unfortunately, but it gives it’s purpose away by being surrounded by large inductors & capacitors.

Posted on — Leave a comment

eBay Airbrush & Compressor

For my latest project, I needed an easier way to paint without messing about with brushes, and the associated marks they leave in a paint job. eBay provided me with a cheap airbrush & compressor.

Airbrush Kit
Airbrush Kit

For less than £30, this kit doens’t look so bad. I’ve never used an airbrush before, but I’ve had no problems with this as yet spraying both water based paints & solvent based paints.

Compressor
Compressor

Here’s the compressor itself, this runs on 12v & has an output pressure of 1.5 Bar, which is supposed to be adjustable.

Compressor Internals
Compressor Internals

Removing a couple of screws reveals the internal components. Nothing much unusual here, a DC diaphragm pump, pressure switch & outlet fittings. There’s also a thermal cutout fitted next to the motor for protection.
The pressure switch attached to the manifold trips at 1.5Bar, keeping the pressure to the brush pretty much constant.

Air Block
Air Block

Next to the air outlet fitting is an adjustment knob, supposedly for varying the pressure. However it’s just a piss-poorly designed adjustable relief valve that vents to atmosphere. There’s not much of a control range.

Messy Wiring
Messy Wiring

The wiring gets a bit messy where the power LED is concerned, with no heatshrink over the solder joints, but it’s adequate.

Airbrush
Airbrush

The airbrush itself isn’t too bad. It’s solid Brass, with a very nice Chrome finish. I’m not expecting miracles from a very cheap tool, but it certainly seems to be reasonable.

Water Trap
Water Trap

A moisture trap is supplied for the brush, to prevent water drops being sprayed out with the paint. Very handy.

Posted on — Leave a comment

“SolarStorm” eBay 4x 18650 Battery Pack

Pack Top
Pack Top

Since the 4×18650 battery pack supplied with my Cree head torch is pretty shit, even by China’s standards, I figured something I could put my own cells into would be a better option. An eBay search turned up these battery boxes, not only with a direct battery output for my torch, but also a USB port for charging other devices when I’m low on charge.

LED Capacity Indicator
LED Capacity Indicator

The output to the lamp connector is directly connected to the battery, through the usual Lithium Ion protection, but the USB output is controlled from a single power button. Battery charge condition is displayed on 3 LEDs. Not sure why they used blue silicone for the seal & then used green LEDs… But it does work, even if a little dim.

Label
Label

Essential information. Does claim to be protected, and from the already existing electronics for the USB this would be expected in all but the cheapest crap.
An IP rating of IPX4 is claimed, yet just above that rating is a notice not to be used in water. Eh?
This is sealed with an O-Ring around the edge of the top cap & silicone seals around the cable & retaining screw. I did test by immersion in about 6″ of water, and it survived this test perfectly fine, no water ingress at all.

Interconnect Straps
Interconnect Straps

The casing holds a PCB at the bottom end with the cell straps.

Screw Post
Screw Post

Someone wasn’t that careful at getting the brass screw insert properly centred in the injection mould when they did this one. It’s mushed off centre, but i’s solidly embedded & doesn’t present any problems to usability.

Cell Springs
Cell Springs

The top cover holds the cell springs & the electronics.

Button & Cable Seal
Button & Cable Seal

Removing the pair of screws allows the top cap to open up. The cable, button & LEDs are robustly sealed off with this silicone moulding.

Top Removed
Top Removed

Here’s the PCB, not much on the top, other than the power button & battery indicator LEDs.

Electronics
Electronics

Desoldering the cell springs allows the PCB to pop out of the plastic moulding. There’s more than I expected here!

Bottom left is a DC-DC converter, generating the +5v rail for the USB port, this is driven with an XL1583 3A buck converter IC.

Bottom right is the protection IC & MOSFETs for the Lithium Ion cells. I wasn’t able to find a datasheet for the tiny VA7022 IC, but I did manage to make certain it was a 7.4v Li-Ion protection IC.

Top right is a completely unmarked IC, and a 3.3v SOT-23 voltage regulator. I’m assuming that the unmarked IC is a microcontroller of some sort, as it’s handling more than just the battery level LEDs.

A pretty decent 4-core cable finishes the job off. For once there’s actually some copper in this cable, not the usual Chineseuim thin-as-hair crap.

Posted on — 15 Comments

Dyson DC16 Handheld Teardown

DC16
DC16

The Dyson DC16 is one of the older handheld vacuums, before the introduction of the “Digital Motor”. (Marketing obviously didn’t think “Switched Reluctance Motor” sounded quite as good).

These vacuums have a very large DC brush motor driving the suction turbine instead, the same as would be found in a cordless power tool.

Control PCB
Control PCB

Popping the front cap off with the ID label, reveals the brains of the vacuum. The two large terminals at the right are for charging, which is only done at 550mA (0.5C). There are two PIC microcontrollers in here, along with a large choke, DC-DC converter for supplying the logic most likely. The larger of the MCUs, a PIC16HV785, is probably doing the soft-start PWM on the main motor, the smaller of the two, a PIC16F684 I’m sure is doing battery charging & power management. The motor has a PCB on it’s tail end, with a very large MOSFET, a pair of heavy leads connect directly from the battery connector to the motor.
Just out of sight on the bottom left edge of the board is a Hall Effect Sensor, this detects the presence of the filter by means of a small magnet, the vacuum will not start without a filter fitted.

Battery Pack
Battery Pack

The battery pack is a large custom job, obviously. 4 terminals mean there’s slightly more in here than just the cells.

Battery Cracked
Battery Cracked

Luckily, instead of ultrasonic or solvent welding the case, these Dyson batteries are just snapped together. Some mild attack with a pair of screwdrivers allows the end cap to be removed with minimal damage.

Cells
Cells

The cells were lightly hot-glued into the shell, but that can easily be solved with a drop of Isopropanol to dissolve the glue bond. The pack itself is made up of 6 Sony US18650VT High-Drain 18650 Li-Ion cells in series for 21.6v nominal. These are rated at a max of 20A discharge current, 10A charge current, and 1.3Ah capacity nominal.
There’s no intelligence in this battery pack, the extra pair of terminals are for a thermistor, so the PIC in the main body knows what temperature the pack is at – it certainly gets warm while in use due to the high current draw.

Motor
Motor

Hidden in the back side of the main body is the motor. Unfortunately I wasn’t able to get this out without doing some damage, as the wiring isn’t long enough to free the unit without some surgery.

Turbine
Turbine

The suction is generated by a smaller version of the centrifugal high-speed blowers used in full size vacuums. Not much to see here.

Unofficial Charger
Unofficial Charger

Since I got this without a charger, I had to improvise. The factory power supply is just a 28v power brick, all the charging logic is in the vacuum itself, so I didn’t have to worry about such nasties as over-charging. I have since fitted the battery pack with a standard Li-Po balance cable, so it can be used with my ProCell charger, which will charge the pack in 35 minutes, instead of the 3 hours of the original charger.

Posted on — Leave a comment

General Electric A735 Digital Camera Teardown

Front
Front

This camera has now been retired after many years of heavy use. Exposure to a 3-year old has caused severe damage to the lens mechanism, which no longer functions correctly.

Rear Panel
Rear Panel

Pretty much standard interface for a digital camera, with a nice large LCD for it’s time.

Front Cover Removed
Front Cover Removed

With the front cover removed, the lens assembly & battery compartment is exposed.

Rear Cover Removed
Rear Cover Removed

Removing the rear cover exposes the LCD module & the main PCB, the interface tactile switches are on the right under a protective layer of Kapton tape.

Main Chipset
Main Chipset

Flipping the LCD out of it’s mounting bracket reveals the main camera chipset. The CPU is a NovaTek NT96432BG, no doubt a SoC of some kind, but I couldn’t find any information. Firmware & inbuilt storage is on a Hynix HY27US08561A 256MBit NAND Flash, with a Hynix HY5DU561622FTP-D43 256Mbit DRAM for system memory.
I couldn’t find any info on the other two chips on this side of the board, but one is probably a motor driver for the lens, while the other must be the front end for the CCD sensor input to the SoC.

Main PCB Reverse
Main PCB Reverse

The other side of the PCB handles the SD card slot & power management. All the required DC rails are provided for by a RT9917 7-Channel DC-DC converter from RichTek, an IC designed specifically for digital camera applications.
Top left above the SD card slot is the trigger circuitry for the Xenon flash tube & the RTC backup battery.

Main PCB Removed
Main PCB Removed

Once the main PCB is out of the frame, the back of the lens module with the CCD is accessible. Just to the left is the high-voltage photoflash capacitor, 110µF 330v. These can give quite the kick when charged! Luckily this camera has been off long enough for the charge to bleed off.

Sensor
Sensor

Finally, here’s the 7-Megapixel CCD sensor removed from the lens assembly, with it’s built in IR cut filter over the top. I couldn’t find any make or model numbers on this part, as the Aluminium mounting bracket behind is bonded to the back of the sensor with epoxy, blocking access to any part information.

Die images of the chipset to come once I get round to decapping them!

Posted on — Leave a comment

No-Brand eBay Carbon Monoxide Detector

Chinese CO Alarm
Chinese CO Alarm

I was looking around eBay for decent deals on a branded CO alarm, and came across these for next to no money, so I thought I’d grab one just to see how bad they could be.

Alarm Opened
Alarm Opened

Popping the casing open shows the very small circuit board inside, with the CO sensor cell on the right. I can’t find any manufacturer information on this cell, nor can I find a photo of anything similar on the intertubes, so no specifications there. The other parts are pretty standard, a Piezo sounder & it’s associated step-up transformer to increase the loudness.

Sensor Closeup
Sensor Closeup

The sensor cell has the usual opening in the end to allow entry of gas.

Main PCB
Main PCB

The other side of the board doesn’t reveal much, just an LCD, a couple of LEDs, a pair of transistors, Op-Amp for the sensor & a main microcontroller.

MCU
MCU

The microcontroller isn’t marked unfortunately. It’s not had the number scrubbed off, it’s just never been laser marked with a part number. Above the micro is a SOT-23 LM321 low-power Op-Amp which does the signal conditioning for the CO sensor.

 

I tried to make this alarm trigger with the exhaust from the Eberspacher heater, which on a well-made branded alarm registered a reading of 154ppm after a few minutes. In the case of this alarm though, I couldn’t make it trigger at all, no matter how long I exposed it to hydrocarbon exhaust gases. I won’t be trusting this one then!

Nothing quite like a piece of safety equipment that doesn’t work correctly from new!

Posted on — Leave a comment

Huawei E160E USB HSDPA Modem

E160E Modem
Huawei E160E Modem

Here’s an old HDSPA 3G USB modem stick that I got with a mobile phone contact many years ago. As it’s now very old tech, and I have a faster modem, not to mention that I’m no longer with Orange (Robbing <expletive>), here’s a teardown of the device!

Cover Removed
Cover Removed

The top shell is just clipped into place, while a pair of very small screws hold down the orange piece at left to hold the PCB stack in the casing. Not much to see here, but it’s clear that there’s a lot crammed into a very small space.

PCB Assembly
PCB Assembly

Here’s the PCB stack removed from the outer casing. The main antenna is on the right, attached with another small screw. Every IC on the boards is covered with an RF can. No problems there, pliers to the rescue!

SD Card Slot
SD Card Slot

Here’s the top PCB, all the shields have been removed. On the left is a Qualcomm PM6658 Power Management IC with integrated USB transceiver. This is surrounded by many of the power management circuits.
The integrated SD Card slot is on the right side. with what looks to be a local switching regulator for supply voltage. This might also provide the SIM card with it’s power supply.

PSU & SIM Contacts
PSU & SIM Contacts

The other side of the top board reveals more power management, with another switching regulator, and a truly massive capacitor at the top edge. I’m guessing this is a solid Tantalum.

Main Chipset PCB
Main Chipset PCB

The other PCB holds the main chipset & RF circuits. On the left here is a Samsung MCP K5D1G13ACH IC. This one is a multiple chip package, having 1Gbit of NAND Flash & 512Mbit of mobile SDRAM.
To it’s right is a Qualcomm RTR6285 RF Transceiver. This IC supports multiband GSM/EDGE/UMTS frequencies & also has a GPS receive amplifier included.
At bottom right is an Avago ACPM7371 Wide-Band 4×4 CDMA Power Amplifier. The external antenna connector is top right.

Main Chipset PCB Reverse
Main Chipset PCB Reverse

On the other side of the main PCB is a Qualcomm MSM6246 Baseband processor. Not sure about this one as I can’t find anything resembling a datasheet. Another micro-coax connector is in the centre, probably for factory test purposes, as it’s not accessible from the outside.
Just above the coax connector is a Qorvo RF1450 SP4T (single-pole 4-throw) High Power (34.5dBm) GSM RF Switch.
Upper right is an Avago FEM-7780 UMTS2100 4×7 Front End Module.
Under that is an RFMD RF3163 Quad-Band RF Power Amplifier Module.

Posted on — Leave a comment

Portable Hearing Induction Loop

Induction Loop
Induction Loop

These units are used to broadcast local audio, such as from a public address system or local microphone. They accomplish this by producing a modulated magnetic field that a hearing aid is capable of picking up.

Back Panel
Back Panel

Not many controls on this bit of equipment. A bi-colour LED for status indications, a microphone, external audio input, charging input & a power switch.

Internals
Internals

Popping the cover off reveals a small lead-acid battery, 2.1Ah at 12v. This is used when the loop is unplugged.

Main PCB
Main PCB

Here’s the main PCB, which takes care of the audio & battery charging. The inductive loop itself is just visible as the tape-covered wire bundle around the edge of the casing.

Audio & Power Input
Audio & Power Input

Here’s the input section of the main PCB. The microphone input is handled by a SSM2166 front-end preamplifier from Analog Devices.

Power Amplifier
Power Amplifier

This audio is then fed into a TDA2003 10W Mono Power Amplifier IC, which directly drives the induction coil as if it were a speaker. Any suitable receiving coil & amplifier can then receive the signal & change it back into audio.

Posted on — Leave a comment

Nanoptix “Spill-Proof” Thermal Receipt Printer

Nanoptix Spill-Proof Thermal Printer
Nanoptix Spill-Proof Thermal Printer

I have yet another receipt printer, this one appears to be brand new. It’s possibly the smallest thermal 80mm printer I have at the moment, and has both USB & Serial interfaces.

Controller PCB
Controller PCB

There’s not much to these printers at all. Removing a single screw allows the case halves to separate, showing the guts. The controller is based around a Texas Instruments TMS320VC5509AFixed-Point DSP. It’s associated Flash ROM & RAM are to the right.
Power supply is dealt with in the top right of the PCB, with the interface ports further left.

Print Head
Print Head

Here’s the thermal mechanism itself, with the large print head. The stepper motor to drive the paper through the printer is just peeking out at top right. The paper present sensor is just under the left hand side of the print head.

Posted on — Leave a comment

Camping Gear – Optimus Nova Multifuel Stove

Stove
Stove

For as long as I can remember I’ve been using Trangia-type alcohol fuelled stoves when I go camping, even though these have served my needs well they’re very limited & tend to waste fuel. I did some looking around for Paraffin/Kerosene fuelled stoves instead, as I already have this fuel on site.
I found very good reviews on the Optimus Nova above, so I decided to go for this one.

This stove can run on many different fuel types, “white gas” (petrol without any vehicle additives) Diesel, Kerosene & Jet A.

Burner
Burner

Here’s the “hot end” of the device, the burner itself. This is made in two cast Brass sections, that are brazed together. The fuel jet can be just seen in the centre of the casting.

Fuel Pump
Fuel Pump

The fuel bottle is pressurised with a pump very similar to the ones used on Paraffin pressure lamps, so I’m used to this kind of setup. The fuel dip tube has a filter on the end to stop any munge gumming up the valves or the burner jet.

Pre-Heating
Pre-Heating

As with all liquid-fuelled vapour burners, it has to be preheated. There’s a fibreglass pad in the bottom of the burner for this, and can be soaked with any fuel of choice. The manual states to preheat with the fuel in the bottle, but as I’m using Paraffin, this would be very smoky indeed, so here it’s being preheated with a bit of Isopropanol.
The fuel bottle can be seen in the background as well, connected to the burner with a flexible hose. The main burner control valve is attached to the green handle bottom centre.

Simmer
Simmer

Once the preheating flame has burned down, the fuel valve can be opened, here’s the stove burning Paraffin on very low simmer. (An advantage over the older alcohol burners I’m used to – adjustable heat!)

Full Power!
Full Power!

Opening the control valve a couple of turns gives flamethrower mode. At full power, the burner is a little loud, but no louder than my usual Paraffin pressure lamps.

Flame Pattern
Flame Pattern

With a pan of water on the stove, the flame covers the entire base of the pan. Good for heat transfer. This stove was able to boil 1L of water from cold in 5 minutes. A little longer than the manual states, but that’s still much quicker than I’m used to!

Fuel Jet
Fuel Jet

The top of the burner opens for cleaning, here’s a look at the jet in the centre of the burner. The preheating pad can be seen below the brass casting.

Posted on — Leave a comment

Totally Wicked Forza / JoyeTech eVIC 60W Teardown

Display
Display

I’ve been a vaper now for many years, after giving up the evil weed that is tobacco. Here’s my latest acquisition in the vaping world, the JoyeTech eVIC 60W. This one is branded by Totally Wicked as the Forza VT60.

18650 Cell
18650 Cell

Powered by a single 18650 Li-Ion cell, this one is a Sony VTC4 series, 2100mAh.

Under the battery a pair of screws hold the electronics in the main cast alloy casing.

OLED Display
OLED Display

After removing the screws, the entire internal assembly comes out of the case, here’s the top of the PCB with the large OLED display in the centre.

USB Jack
USB Jack

On the right side of the board is the USB jack for charging & firmware updates. The adjustment buttons are also at this end.

Output
Output

On the left side of the board is the main output connector & the fire button. Unlike many eCigs I’ve torn down before, the wiring in this one is very beefy – it has to be to handle the high currents used with some atomizers – up to 10A.

PCB Reverse
PCB Reverse

Removing the board from the battery holder shows the main power circuitry & MCU. The aluminium heatsink is thermally bonded to the switching MOSFETs, a pair under each end. The switching inductor is under the gap in the centre of the heatsink.

DC-DC Converter
DC-DC Converter

A close up of the heatsink shows the very slim inductor under the heatsink.

Microcontroller
Microcontroller

The main MCU in this unit has a very strange part number, which I’ve been unable to find information on, but it’s probably 8081 based.

Posted on — Leave a comment

Duratool ZD-915 12v Conversion

Inkeeping with everything else in my shack being low voltage operated, I had planned from the outset to convert the desoldering station to 12v operation. It turns out this has been the easiest tool to convert in my shack so far.

PSU Outputs
PSU Outputs

The factory SMPS is a fairly straightforward 18v 12A unit, with only a single small oddity: the desoldering gun’s heating element is controlled from inside the supply.

Iron MOSFET
Iron MOSFET

Next to the output rectifier on the heatsink is a large MOSFET, in this case a STP60NF06 from ST Micro. This is a fairly beefy FET at 60v & 60A capacity, RDS On of <0.016Ω.
This is driven via an opto-isolator from the main logic board. I’ve not yet looked at the waveform on the scope, but I suspect this is also being PWM’d to control temperature better when close to the set point.

Iron Element Controller
Iron Element Controller

Rather than fire up the soldering iron & build a new element controller circuit (Lazy Mode™), I opted to take a saw to the original power supply. I cut the DC output section of the PCB off the rest of the supply & attached this piece back to the frame of the base unit. I also added a small heatsink to the MOSFET to make sure it stays cool.

12v Power Supply
12v Power Supply

Since the fan & vacuum pump are both already 12v rated, those are connected directly to the DC input socket, that I’ve installed in place of the original IEC mains socket. The 18v for the heating element is generated by a 10A DC-DC converter, again from eBay.

Oddly, the iron itself is rated at 24v 80W, but the factory supply is only rated to 18v. I’m not sure why they’ve derated the system, but as the station already draws up to 10A from a 13.8v supply, increasing the voltage any further would start giving my DC supplies a problem, so it can stay at 18v for now.

Posted on — 3 Comments

Duratool ZD-915 Vacuum Desoldering Station Teardown

For a long time I’ve needed a decent vacuum desoldering tool, as I do much stripping of old PCBs for random parts.
Solder wick works well for most things, but it’s expensive & can be fiddly. It also doesn’t keep very long as the copper braid oxidises & after that point it never seems to work particularly well, even when soaked in fresh flux.

Desoldering Station
Desoldering Station

As usual eBay to the rescue! I managed to pick this one up for £80.

Vacuum Pump
Vacuum Pump

Removing the lid reveals the internals. Front & centre is the vacuum pump, with the mains supply behind it. There’s also a very noisy cooling fan at the back. Not sure why since the unit never gets warm enough to actually warrant a fan.

PSU
PSU

On the other side is the PSU. This is an 18v 12A rated SMPS, with a bit of custom electronics for controlling the iron element. Mounted to the back case is a small black box, more to come on this bit.

PSU Board
PSU Board

Cracking the case of the PSU reveals a pretty bog-standard SMPS, with a surprising amount of mains filtering for a Chinese supply. The DC outputs are on the right.

20160101_111613

From the rail markings, this is clearly designed to output some more voltage rails – possibly for other models of unit. In this case though, a single 18v rail is present. The iron’s element connects directly to the supply, controlled via an opto-isolated MOSFET.

Chinese Voltage Regulation
Chinese Voltage Regulation

As both the fan & the vacuum pump motor are 12v devices, some provision had to be made to reduce the 18v from the power supply to a more reasonable value. Inside the black plastic box are a pair of 1Ω 5W power resistors, connected in series. The output from this connects to the fan & vacuum pump. Because cheap, obviously.

Controller
Controller

Finally, here’s the controller PCB, the main MCU is an 8081 derivative, with a Holtek HT1621B LCD controller for the front panel temperature readout. Iron temperature is achieved by a thermocouple embedded in the heater, I imagine the potentiometer on the left side of the PCB is for calibration.

Posted on — 2 Comments

Roku LT Teardown

 

Roku LT
Roku LT

Here’s another retired piece of tech that we used to route media from the NAS to the main TV. It was retired since it’s inability to support XBMC/Kodi & having some crashing issues.

Main PCB
Main PCB

After attacking the case with the screwdriver (Torx in this case), the main board comes out. The CPU in this looks *very* familiar, being a PoP device. There are unpopulated places for an ethernet interface & USB port here.

Flash & CPU
Flash & CPU

After a little digging is turns out the CPU in this device is a BCM2835, with 256MB of RAM stacked on top. It’s a Raspberry Pi! Even the unpopulated part for Ethernet is the same SMSC LAN9512!
There’s 32MB of Flash for the software below the CPU.
On the far right of the board is a Broadcom BCM59002IML Mobile Power Management IC.

WiFi Chipset
WiFi Chipset

On the bottom of the PCB is the WiFi chipset, a Broadcom BCM4336, this most likely communicates with the CPU via SDIO. There’s also a section below for a Bluetooth chipset.