[intector]

Hello,

Thank you for the fast answer.

The reason for that behavior was the linker file. I compared the linker file with one generated by STM32CubeMX and found that some spaces in the wrong places caused this problem. I don’t understand how this could cause such issues, but it’s working now. I’ll probably have to learn more about the linked script syntax.

 

Again, thank you

Kai

[intector]

Hello,

I encountered many boulders on my way, but my project is finally ported to the STM32H7R3L8H6H MCY and compiles without errors. The download to the external memory is also working, and the debugger stops on the breakpoints. The only issue is that I can see any values on any variables. Some variables have random values, and others have standard initial values, but no changes are shown during debugging.

I had this issue earlier and followed the instructions you guys gave me in my earlier post about it, after which it worked. The issue came back for some reason, and I can’t see any values. The program runs and stops on the breakpoints, but that is it pretty much.

I’ve attached the log file for your information.

Thank you

Kai

Attachments:

You must be logged in to view attached files.

[intector]

Hey,

Thank you very much for the fast answer. This is what I already thought. I’ve found the entry in the CSP.XML, but I wasn’t sure if that was the correct location.

 

thank you

Kai

[intector]

Hello,

Thank you for the excellent support. It works like a charm.

[intector]

Hello,

Thank you for the fast reply to my question.

Here are some more details on my issue:

1. I used a board with a STM32H7R3L8H6H MCU
2. To create the test project, I used STM32H7S78-DK –> Template_XSIP –> Boot
3. It places the __disable_irq() function, calling the Error_Handler function. This gets red underlined because it can’t find the declaration. In STM32CubeIDE it uses the declartion in cmsis_gcc.h. In VisualGDB, it doesn’t offer this file as a solution. The screenshot __disable_irq_error.jpg shows the location in the main.c file where this function is called. The screenshot cmsis_selection.png shows the files that VisualGDB offers.
4. The screenshot no_values01.jpg shows the variables without values during debugging.

Please check the attached files for more information.

 

I tried a test with the USB-CDC example for the NUCLEO-STM32H7S3L8, which you used in your tutorial, and this doesn’t have this issue. The variables have values in that case.

 

 

 

Attachments:

You must be logged in to view attached files.

[intector]

Hello Support,

I upgraded my VisualGDB to custom to follow your tutorials. I’m trying to get my board running by following your tutorials. Unfortunately, I can’t see any values when I stop on breakpoints. I also tested a NUCLEO-STM32H7S3L8 board but ran into the same problems. What could be the problem?

 

[intector]

Hey Guys,

Thank you for this great tutorial. I finally can get away from that awful STM32CubeIDE with its annoying STM32CubeMX code generation.

I’m working on a project for which I designed the PCB. It uses the STM32H7R3L8H6H MCU, an 8GByte EMMC08G-MV28, a 32MByte MX25UW25645GXDI00, and a 32MByte APS256XXN-OBR, among other peripherals. I’ve attached some pictures of it.

I have the memory working at 200 MHz, but it was a project. The STM32Cube_FW_H7RS_V1.1.0 package contains several errors regarding the XSPI drivers, and the documentation isn’t updated either.

 

Again, thank you for your support, and keep in mind:

“Always be yourself. Unless you can be a pirate. Then always be a pirate.”

• This reply was modified 1 week, 4 days ago by intector.

Attachments:

You must be logged in to view attached files.

[intector]

Hey,
That’s excellent news. Just in time, I finished my new board with an STM32H7R3L8H6H. I’m looking forward to your tutorial.

 

Great job, guys, and never forget:

“Always be yourself.
Unless you can be a pirate.
Then always be a pirate.”

 

[intector]

Hey,

Did you have a chance to test the STM32H7S/R series MCU?

[intector]

Hey Guys,

That works just fine, thanks.

[intector]

Hi,

Thank you for the fast answer. I’ve done this before, and I was just wondering if I could change the definitions myself.

[intector]

Hello,

I’ll try this and let you know the results.

[Author]

Posts