IAR debugger - Difference between specifying STM32H750B-DK and just STM32H750IB chip.

[CChen.16]

We are using IAR embedded workbench for our compiler and debugger (I-jet). I am testing with a STM32H750B-DK board. Running the sample code of QSPI memory mapped. I realized that if I select board as STM32H750-DK, then everything works fine, but if I select STM32H750IB, then the flash reading was always 0x99. What is the difference between the two selections? Does the debugger load extra initialization code for DK board? The source code is exactly the same. 

Thanks for any help in advance.

[Andrew Neil]

---

@CChen.16 wrote:

We are using IAR embedded workbench for our compiler and debugger (I-jet) ... Does the debugger load extra initialization code for DK board? 

---

You really need to ask IAR about the specific behaviour of their product.

https://www.iar.com/support 

 

Anyhow, when you tell it the DK, then it will presumably have full details of the board and its memory configuration, etc.

If you just tell it the chip part number, it won't know anything but the chip - it will have no idea about any external connections. You will provide all that info - did you?

[CChen.16]

Thanks for your reply. We did have the QSPI initialization code, but it seems not working. I am also working with IAR tech support team. Thanks for your help.

[Pavel A.]

IAR has "board definition" files (*.board)  where you specify the "external memory loaders" script  (*.flash) and executable drivers (*.out).  Please look at these files for the DK board to understand how to change them for your custom board. 

[CChen.16]

OK, thank you for your help.