Help troubleshooting stm32g431 board

[aks1]

Hi. I designed a stm32 board an am trying to program it with a stm32 development board. i am having issues with programming it. This is my board design and my programming setup. I have connected the stm32f4 to my laptop to program it and the Integrated Circuit I'm using on my board is the stm32 g431. I know i have not pulled boot0 to low which is a problem i tried to resolve using option bytes where i set the nBoot1 byte to 0. But i have my boards boot up and then after clearing flash storage, they are usually stable. The board isn't dead since current is being drawn but the stm32 status LED is blank and when i try to connect to it with the stm32 programmer, i get ' Unable to detect Core ID. No stm32 target found. If your product uses debug authentication, please enable debug authentication. Please help me figure out what is wrong. This is the second board that has gone this way. I only have 3 more left.

[aks1]

Sorry, I misunderstood your solution. I got the board working. I replaced the discovery board and it seems to have worked now. However, i am still trying to get the code ive written to work on it. I can connect the board right now and i can see the register values. They aren't changing though. 

Do you have any suggestions to this or need any more information to help debug this ?

[aks1]

yep. Sorry, i misunderstood

[aks1]

I am using it in the lab right now and i have gotten it running. I can read the memory and the values there. However, the registers dont have any data written into them and it doesnt seem like the data from the sensors is being written into them either which is a problem. Do you have any suggestions to this or need any more information to help debug this ?

[Andrew Neil]

---

@aks1 wrote:

I am using it in the lab right now and i have gotten it running. 

---

Excellent - so please mark the solution.

Please start a new thread for the new question.

[LCE]

> Do you have any suggestions to this or need any more information to help debug this ?

No info needed, our crystal balls already show the solution to your problem... NOT.

As Andrew said, start a new thread.

But before that, check the following:

- compare your working Discovery board firmware to your new board sources

- clocks set correctly? source: HSE / HSE bypass / HSI, frequency ? ...

- GPIOs ported correctly ?

- put something simple ...

      - before your main loop, some simple IO toggling at certain points and check with a scope 

      - into your main loop, like a simple u32++

And once more, try to get some LEDs and UART on your board, at least for development that helps so much. 
Unless you are really good and happy with the IDE debugging.

[Andrew Neil]

---

@LCE wrote:

Unless you are really good and happy with the IDE debugging.

---

@aks1  Even when you like IDE debugging (as I do), it's not always the right tool for the job.

In particular, halting debug can't show you real-time behaviour.

So it's always important to provide stuff like UART and GPIOs to aid in development & debug...

An important question from the very start  of your design must always be, "How will I debug this thing?".

You need to Design For Debug.

See also this thread.

#DesignForDebug

[Andrew Neil]

---

@Andrew Neil wrote:

The thing about using the [ST-Link] from a Dev Board is that you need to be sure that the Dev Board's target processor is completely disconnected - so as not to interfere with the connection.

---

An example of exactly that just now:

https://community.st.com/t5/stm32-mcus-embedded-software/stm32c031-reseting-after-receiving-data-on-uart/m-p/853653/highlight/true#M69803

#StandaloneSTLink #StandaloneDebugger