Cannot connect DK1 board via ST-LINK with Keil-MDK

[jgome.1]

New board STM32MP157A-DK1 bought, trying to connect. First, ST-LINK drivers were updated, then on-board ST-LINK version was updated to last available V2J26M36. MDK cannot connect ("No target connected"), st-link utility cannot see board ("Detection fail"). Through some experiments, by the moment, assume this:

- Oscilloscope shows signals on SWDIO, SWCLK, NRST.

- Tried all available firmware versions (V32...V36) from the site.

- Wires were soldered to TP3, TP5, etc. to got connection to external ST-link. Initially, external ST-LINK/V2 had version M28 and MDK has read ident from the device! But MDK cannot flashing board ("invalid ROM table"), and firmware in external ST-LINK were updated. Since this, it came to the situation "No target connected" which was with the on-board st-Link. Another firmware versions were tried with the same result.

ST-LINK/V2 and ST-LINK/V2 Isol were tried.

In MDK dialog, internal st-link version shows as V2x36x26, but there NO such format in RN0093 doc. Only J36M26 or S7 but no "x". External ST-link version shows correctly, e.g. V2J34S7. What may be wrong?

[PatrickF]

Hello,

please have a look to this post: https://community.st.com/s/question/0D50X0000AqqwFQSQY/stm32mp157cdk2-onboard-stlink-issue

Regards

[Olivier GALLIEN]

​Hi @jgome.1​ 

I understand you are not fully aware that STM32MP1 is really different from STM32 MCU product you may have known.

Dual Core / External DDR / No flash etc...

What you are trying to do with Keil-MDK may work only for programing the M4 coprocessor,  using specific engineering boot mode.

The Linux/A7 or the M4 coprocessor in "Production" mode can not be program with ST-LINK.

I invite you to visit the Wiki User Manual and especially proceed to the Getting Started section.

https://wiki.st.com/stm32mpu

Hope it help,

Olivier

[jgome.1]

Hi,

Thank you for answers, but, before reading your links...

I understand that I may programming the M4 coprocessor. "Blinky example" from DFPack was loaded as elf-file, started, stopped, as described here https://visualgdb.com/tutorials/arm/stm32/stm32mp1/ in paragraph 15, this is ok.

Now I tried to load and debug M4 with Keil-MDK (and tried to turn Engineering mode on as described in paragraph 7, if it is right, and tried other BOOT jumpers combinations anyway), and click-watch this video https://www.youtube.com/watch?v=Ih6A2EPiT8c&feature=youtu.be with MDK target setup dialog connected to board (14:39). I just needed to quick-test this board as many other boards for possibility of connection and debugging.

[Olivier GALLIEN]

Hi @jgome.1​ 

Fine, both link you sent looks to provide correct introduction about STM32MP1.

Boot switch position in paragraph 7 are correct for Engineering boot mode as you may double check here :

https://wiki.st.com/stm32mpu/wiki/STM32MP157X-DKX_-_hardware_description

I'm not expert in Keil-MDK but Video tutorial looks very complete.

I noticed that the "Cortex-M Target Driver Setup" windows does not look the same at your end and in Video.

Not the same version ?

Video address Eval board while you are using DK1.

Did you find and select correct MP1 device ( 7:48 in video)

I can only provide hints. If this does not help maybe worth to contact Keil support.

Hope it help,

Olivier

[Olivier GALLIEN]

Hi @jgome.1​ 

In order to better reflect you problem and reach potentially member facing the same or with solution I complete the heading of your post

Olivier

[jgome.1]

Hi OlivierG (ST Employee),

Possibly the case is solved.

Previous Keil MDK version not contained "AP" field in setup dialog, but, it seems to be necessary to have this field in settings (page 5):

http://www.keil.com/appnotes/files/apnt_319_v1.1.pdf

After updating, ID appeared in SW Device field.

And second issue was - I used "Load" item in MDK (that causes ROM table error) but have to use "Debug" item.

Now "Blinky example" loaded and controlled by Keil MDK.

[Olivier GALLIEN]

Good to read this.

Thanks for feedback !

Olivier