Hey Danilo,

thanks for replying.

I've got the 'real' debugger. I know it works because I have tried
programming another device with JTAG and it worked fine.

At this point all I'm doing is trying to connect to target with the ST-Link
utility on windows.

Yes the SWIO and SWCLK pins are correctly connected. I double-checked as I
was writing this just to make sure.

I tried your idea connecting the TVCC pins to 3.3V vias on the board but I
sent the board to some ring of death, so I hooked a seperate power supply,
set it to 3.3V, and connected the TVCC pins to that. I even connected the
NRST pin to the ST-Link's TRST pin.

Still nothing. I was begging for a JTAG connection to just appear on the
board after all this! :D

At this point having to connect the board like this just isn't feasible so
I'm back to just programming the board with DFSU.

Thanks anyway,



On Fri, Aug 3, 2018 at 2:13 PM Danilo Beuche <danilo.beu...@gmx.net> wrote:

> Hi Jacob,
>
> if you own a "real" ST Link, you have to connect the target voltage pin on
> the debugger (or to some other source of 3.3V). For a cheap ST-Link V2
> clone you typically need to connect  SWDIO, SWCLK and GND only. Sometimes
> you may need to connect NRST as well, but usually not.
>
> The most common mistake I do is to swap CLK and DIO cables. Next is the
> software, I did not check, but the pins can be configured to be used as
> GPIO. In this case debugging works only if coming from reset.
>
> For testing if the connection works I often use the STM32 Link Utility on
> windows (Target->Connect). Then I get my debugger configuration to work
> after knowing the basic cabling works.
>
> However, I since I don't own a SM1000 I never used a debugger on this
> specific target.
>
> Regards,
> Danilo
>
>
>
> On 03.08.2018 13:58, Jacob Falzon wrote:
>
> Hey there,
> recently been trying to debug an SM1000-D with an ST-link/V2 ICD.
>
> I connected the SW and GND pins, tried in both flash and system memory yet
> can't seem to connect to target.
>
> Any ideas?
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>
>
>
> _______________________________________________
> Freetel-codec2 mailing 
> listFreetel-codec2@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/freetel-codec2
>
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Freetel-codec2 mailing list
> Freetel-codec2@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freetel-codec2
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Freetel-codec2 mailing list
Freetel-codec2@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freetel-codec2

Reply via email to