PEmicro | Experts in Embedded tools for Flash Programming and Development

Thursday, May 28, 2020

Connect Multilink Universal to NUCLEO-F207ZG
Andy P. May 28, 2020 at 01:49 PM (13:49 hours)
Staff: Steve M.

10 comments

Hello,

I am starting work on a STM32F207 based project and whilst we wait for the custom hardware (which will have a connector to directly match one of the standard headers in the Multilink Universal FX) I want to start software development using the NUCLEO-F207ZG reference board.

The NUCLEO board only appears to have a 6 pin debug connector (single inline 0.1" pitch) labelled SWD.  I can't work out whether I can use this with the Multilink Universal FX and how I disable the onboard USB ST-Link parts.

-Andy.

Comment #1 Andy P. - May 28, 2020 - 01:49 PM (13:49 hours)

Comments

Hi Andy,

I would suggest looking at the Nucleo Board User Manual just to get verify what I am telling you is true (can find it fairly easy on ST's website). The way we usually connect to Nucleo boards are by soldering on a debug connector to CN11 large enough to reach pin PA14(at least 2x8). Then connect female-female wires connecting from the corresponding pins to PORT B (20-pin) of the Multilink FX. As well as connecting a male-female wire going from CN8 pin 7 (3.3V) to the corresponding pin on the Multilink.

The following are the necessary connections you will need to make.

CN11 Pin            Multilink Debug Header
Pin 8 (GND)    ->   Pin 2 (GND)
Pin 13 (SWDIO) ->   Pin 7 (SWDIO)
Pin 15 (SWCLK) ->   Pin 9 (SWCLK)
Pin 14 (NRST)  ->   Pin 15 (RESET)

CN8 Pin
Pin 7 (3.3V)   ->   Pin 1 (VCC)

This can be reviewed in the user manual as well.

Steve

Comment #1.1 Steve M. (PEmicro Staff) - May 28, 2020 - 03:46 PM (15:46 hours)

```
Thanks,

I'll take a look at this today and see if I can get it working.

-Andy.
```
Comment #1.1.1 Andy P. - June 1, 2020 - 03:43 AM (03:43 hours)

I have wired this up and it makes some effort to start the debugging process but it always throws up the "P&E Connection Assistant" dialog box.

Is there some specific setting I need for the BDM_SPEED value?

-Andy.

Comment #2 Andy P. - June 1, 2020 - 06:48 AM (06:48 hours)

Hi Andy,

I would try at least option 5 as the BDM speed option. How are you providing power? Through the Cyclone or through an external source? I would double check to make sure at least 3.3V is being provided to the Nucleo board (there is an option to display target voltage/current on the Cyclone using the Cyclone settings).

If the issue persists, I would suggest setting up a Support Request so we can obtain screenshots of connection settings/hardware setup to assist you further.

Steve

Comment #2.1 Steve M. (PEmicro Staff) - June 1, 2020 - 09:21 AM (09:21 hours)

Hi Steve,

I have been attempting to supply the power to the Nucleo board using the Multilink Universal FX.  I have added some external power to the board and I now see the debugger connecting  but I don't see it trying to write the code writing to the flash.

-Andy.

Comment #2.1.1 Andy P. - June 1, 2020 - 09:29 AM (09:29 hours)

Hi Andy,

What tool are you using to trying to write the flash memory. Could you elaborate further on your set up and attempts to flash the device?

Steve

Comment #2.1.1.1 Steve M. (PEmicro Staff) - June 4, 2020 - 11:41 AM (11:41 hours)

Hi Steve,

I am using Eclipse as my IDE. The code I am compiling is using the gcc compiler that comes along with the GNU MCU Eclipse plugins (https://gnu-mcu-eclipse.github.io/). Eclipse also has the P&E plugins installed for programming/debugging the device.

I have the Multilink Universal FX connected to the NUCLEO-F207ZG board using the wiring information you provided previously and also have a USB cable connected to the USB-PWR connector (CN1) on the NUCLEO board to provide 5V to the board.

When I try to run the debug session the "GDB PEMicro Interface Debugging" console shows the following:

Connection from "127.0.0.1" via 127.0.0.1. Connection from port "62894" to 6224
Connection from "127.0.0.1" via 127.0.0.1. Connection from port "62898" to 7224
Telnet server running on 127.0.0.1:51794
Searching for FreeRTOS Kernel Symbols...
rsp_qC - qSymbol: 707843757272656E74544342
Symbol pxCurrentTCB found. (0x2000016C)
rsp_qC - qSymbol: 707852656164795461736B734C69737473
Symbol pxReadyTasksLists found. (0x20000178)
rsp_qC - qSymbol: 7844656C617965645461736B4C69737431
Symbol xDelayedTaskList1 found. (0x200001F0)
rsp_qC - qSymbol: 7844656C617965645461736B4C69737432
Symbol xDelayedTaskList2 found. (0x20000204)
rsp_qC - qSymbol: 7850656E64696E6752656164794C697374
Symbol xPendingReadyList found. (0x20000228)
rsp_qC - qSymbol: 757843757272656E744E756D6265724F665461736B73
Symbol uxCurrentNumberOfTasks found. (0x200001DC)
rsp_qC - qSymbol: 757844656C657465645461736B7357616974696E67436C65616E5570
Symbol uxDeletedTasksWaitingCleanUp found. (0x200001E0)
rsp_qC - qSymbol: 7853757370656E6465645461736B4C697374
Symbol xSuspendedTaskList found. (0x20000240)
rsp_qC - qSymbol: 785363686564756C657252756E6E696E67
Symbol xSchedulerRunning found. (0x2000023C)
Successfully initialized kernel symbols. FreeRTOS analysis enabled.
MemManage: The processor attempted an instruction fetch from a location that does not permit execution.
HardFault: A fault has been escalated to a hard fault.

If you have an email address I can send you a screen capture of the debug configuration in Eclipse.

When I have used the Multilink Universal FX with LPC1768 devices in the past it has always included a check of the internal flash, a determination of the contents being different and reprogramming it prior to starting the debug session.

-Andy.

Comment #2.1.1.1.1 Andy P. - June 4, 2020 - 11:57 AM (11:57 hours)

I am assuming that the application pre-programmed into the NUCLEO board is FreeRTOS based.  My firmware is also FreeRTOS based but that isn't what is starting up as it isn't being programmed.

-Andy.

Comment #2.1.1.1.1.1 Andy P. - June 4, 2020 - 11:59 AM (11:59 hours)

Hi Andy,

This issue may require some more in depth debugging than anticipated including some screenshots that you mentioned. I would suggest either email technical-info@pemicro.com, or creating a Support Request on our website so we can look at this issue further.

Thanks

Steve

Comment #2.1.1.1.1.2 Steve M. (PEmicro Staff) - June 5, 2020 - 03:36 PM (15:36 hours)

Add comment

Want to comment? Please login or create a new PEmicro account.