Posted by gshera on 2017-01-06 19:26

Hi Lauent,

I updated the software no change in function.
The pins are connected as you describe.

I’ll try to be more clear. With 2 different custom boards (STM32F405) I have project A and project B. Each in thier own Eclipse instance and workspace.
Project A is my main project.
Project B is a simple project with a while loop in the main.

Open Eclipse with project A, start a debug session, debug normally, then terminate. If I start another debug session with the same Eclipse instance, same project A, the debugger connects successfully, but the device runs to a bad location immediatly after the first instruction after Reset_Handler: I then terminate this debug session.

Open a second Eclipse instance with project B. I can start a debug session and run normally. If I terminate that session then start the project B debug session again it will fail in the same way as project A. I then terminate this debug session.

Change to the project A eclipse instance and start the project A debug session, it operates normally. Terminate project A debug session. Change to project B eclipse instance, start the project B debug session, it operates normally. Terminate project B session. Change to the project A eclipse instance and start the project A debug session, it operates normally.etc..

So
Start A, (ok), terminate A. Start A (bad) terminate A. Start A (bad) terminate A. \
Start B, (ok), terminate B. Start B (bad) terminate B Start B (bad) terminate B \
Start A, (ok), terminate A, Start B (ok), terminate B. Start A (ok), terminate A...

On the nucleo STM32F411. (change the STLInk jumper of course). I can start and stop a debug session normally.
It’s really strange. I never had this issue with a previous SMT32F401 custom board project either.

Thanks
Geoff