Skip to main content
Graduate
May 7, 2021
Question

10-pin debug connector and STLINK-V3-ISOL - not reliable?

  • May 7, 2021
  • 2 replies
  • 1597 views

I am using STLINK V3 with the ISOL board, and using the supplied 10-core cable, going to this connector in my 32F417 target

https://peter-ftp.co.uk/screenshots/202105072011602908.jpg

On the target connector, I have pins 3,5,7,9 grounded.

Pins 2,4,6,10 go to CPU pins PA13,PA14,PB3,PB4.

It works, but reliably only for code download. If I try to run SWV ITM data console, that also works but very soon I get a loss of comms. I am running at 8MHz; the ISOL debugger can go up to about 15MHz before it fails. I tried it at 1MHz but the same happened.

The wires to the CPU are pretty short - 5cm max.

I would be grateful for any ideas.

Console output:

------ Switching context -----

Target connection mode: Default

Reading ROM table for AP 0 @0xe00fffd0

Hardware watchpoint supported by the target

Failed to set com freq, status 0

COM frequency = 8000 kHz

ST-LINK Firmware version : V3J7M2B4S1

Device ID: 0x413

PC: 0x8025688

ST-LINK detects target voltage = 3.25 V

ST-LINK device status: HALT_MODE

ST-LINK device initialization OK

SWV_SetStatus(true): stop_reply_pending == 0

handle_vCont_c, continue thread

ST-LINK device status: RUN_MODE

ST-LINK device status: HALT_MODE

SWV_SetStatus(false): stop_reply_pending == 1

TraceCaptureStart and SWV event set to APP_FALSE (0)

NVIC_DFSR_REG = 0x0000000A

SWV_SetStatus(true): stop_reply_pending == 0

handle_vCont_c, continue thread

ST-LINK device status: RUN_MODE

ST-LINK device status: Failed to get status, Target not responding, retrying... 19

Target is not responding, retrying...

ST-LINK device status: Failed to get status, Target not responding, retrying... 19

Target is not responding, retrying...

ST-LINK device status: Failed to get status, Target not responding, retrying... 19

Target is not responding, retrying...

    This topic has been closed for replies.

    2 replies

    PHolt.1Author
    Graduate
    May 7, 2021

    As usual, nobody answers.

    Anyway, I solved it. There seems to be a fault on the MB1440B board, when stacked on top of the MB1599B board (the ISOL board). The 20-way connector works but the 14-way (CN1, which is used for the 10-way cable) does not. Well, it works but with a lot of intermittent faults. The solution is to not use MB1440B and plug the 10-way cable into the MB1599B board instead (CN1 also).

    Technical Moderator
    May 28, 2021

    Hi @PHolt.1​ ,

    I added this thread to your post as contains the same topic, and this will help other users find that discussion faster.

    Imen