Stuck at "No ack for packet opcode=0x2f" (CC3200 Toniebox) - Connection Verified

Toniebox Hardware CC3200 (V1, V2)
1

Step 1: Clearly Describe the Problem I am trying to extract certificates from a CC3200-based Toniebox using cc3200tool. I can successfully establish the initial connection (“Connected”), but the process fails immediately after when reading the version. Error Message: 2026-01-07 17:11:00,234 -- Connecting to target... 2026-01-07 17:11:01,374 -- Connected, reading version... 2026-01-07 17:11:06,382 -- timed out while waiting for ack 2026-01-07 17:11:06,382 -- Could not connect to target: No ack for packet opcode=0x2f

Step 2: Provide a Step-by-Step Description

  1. Setup: Hard-wired SOP2 to 3.3V. Connected FT232AZ UART adapter (TX, RX, GND, and DTR to RST).

  2. Command: cc3200tool -p COM3 --reset dtr list_filesystem.

  3. Action: The tool triggers the reset via DTR.

  4. Expected outcome: The tool connects and lists the files on the CC3200 flash.

  5. Actual outcome: The tool reports “Connected”, but then times out waiting for the ACK of the first command (Get Version).

Step 3: Include Technical Information

  • OS: Windows 10

  • FTDI Driver: 2.12.28.0 (installed to fix the “Serial Break” issue).

  • COM Settings: Latency Timer set to 1ms, Baud rate in Device Manager set to 115200, USB transfer sizes reduced.

  • Hardware: Toniebox CC3200 board, FT232AZ adapter (3.3V jumper verified).

Step 4: Attached Logs

Plaintext

2026-01-07 17:09:50,060 -- Connected, reading version...
2026-01-07 17:09:55,061 -- timed out while waiting for ack
2026-01-07 17:09:55,061 -- Could not connect to target: No ack for packet opcode=0x2f

Step 5: Screenshots (Hänge hier dein Foto vom Adapter/Jumper und den Screenshot der COM-Einstellungen an!)

Step 6: Steps I’ve Taken to Resolve the Issue

  1. Loopback Test: Performed a loopback test by bridging TX/RX directly on the Toniebox PCB pads. Typing in PuTTY worked perfectly, confirming the entire wiring chain and soldering is fine.

  2. Manual Break Test: Accidentally shorted GND to RX during a trial, which forced a “Connected” state, confirming the chip is responsive to break signals.

  3. Driver Downgrade: Successfully downgraded to the known working 2.12.28.0 version.

  4. Baud Rate: Corrected Windows default (9600) to 115200.

  5. Power: Tried both battery-only and charger-connected power.

Question: Since I am getting the “Connected” message, the handshake works. Why does the chip fail to ACK the very first opcode (0x2f)? Is there a known timing issue with this specific Toniebox board revision or the FT232AZ?