NUCLEO-C071RB - IAR "Non-recognized options in project file" during debugging

[curiocity]

Hi,

Can you please help me for below  

I am using NUCLEO-C071RB development board ,I am generating the code using CUBE MX software(V6.14.1) following steps I have followed 

Step 1:Selected the board as NUCLEO-C071RB

Step 2:From project manager I have selected the Toolchain/IDE as EWARM and other configuration as below 

Step 3:Clicked on generate code 

Step 4:a .eww file is generated and I opened the file using IAR software the code builds completly without erros but, I am getting the following notification during opening of file 

Step 5:The code builds ok with no error so now I have tried to debug that code it will not 

Step 6:I have right click on project and tried to look the core or device but it is not detected as below (the core should be Cortex MO+and there should be Device name 

My question is: Could there be an issue with the CubeMX IDE that's preventing it from detecting the STM32C071RBT6 microcontroller?

Step 7: I navigated to the ST folder in the IAR system, but I couldn't find any files related to the STM32C071RBT6. Why weren’t the files generated

Observation 2:

This issue never occurred when I was using the STM32F411RE with the NUCLEO-F411 development board.

Could you please help me to solve the issue 

[Andrew Neil]

What EWARM version are you using?

On what host platform?

---

@curiocity wrote:

Step 4: a .eww file is generated and I opened the file using IAR software the code builds completely without errors but, I am getting the following notification during opening of file  

---

What do you mean by, "opening the file" here ?

[curiocity]

Hi Andrew,

Thanks for your reply

1.I am using IAR Embedded Workbench IDE-Arm 9.10.2 

2.Opening the file means that the generated .eww file is launched using IAR Embedded Workbench.

[Andrew Neil]

Thanks, but you didn't say what host - windows, linux, etc ?

---

@curiocity wrote:

2.Opening the file means that the generated .eww file is launched using IAR Embedded Workbench.

---

Your title says, "during debugging" - but that sounds like just initially opening the project file?

PS:

What did the log window say?

[curiocity]

Hi Andrew,

I am working with Windows system 

[curiocity]

Hi Andrew

Sorry for confusion,

Not during debugging I want to say during launching i.e at initial state. 

The problem itself is I am not able to do debugging because device is not detected .

[Ozone]

IAR WB was Windows-only when I dealt with it. I'm not aware that ever changed.

Did you check what option IAR complains about ?
I suspect you are using an older version that Cube expects.

Try enabling all possible console output options in the WB, you should see an error message.

[Andrew Neil]

---

@curiocity wrote:

The problem itself is I am not able to do debugging because device is not detected .

---

if it's already told you on opening the Project that the Project is bad, then it's not a surprise that things don't work properly with that Project!

Are you sure that your version of IAR actually supports this chip?

You'd need to check that with IAR.

Also:

What did the log window say?

[curiocity]

Are you sure that your version of IAR actually supports this chip?

ans: I'm not certain, but assuming it works with the STM32F411RE, it might also work with the STM32C071CBT6

You'd need to check that with IAR.

ans:Yes, but is this issue actually related to IAR or CubeMX?

Not able to understand from this log 

[Andrew Neil]

---

@curiocity wrote:

Are you sure that your version of IAR actually supports this chip?

ans: I'm not certain

---

Then you need to check with IAR.

---

@curiocity wrote:

but assuming it works with the STM32F411RE, it might also work with the STM32C071CBT6

---

If your IAR doesn't recognise the chip, then it's not going to work!

"Non-recognized options" sounds exactly like what'd happen with a chip that's not recognised!

---

@curiocity wrote:

Not able to understand from this log 

---

It's IAR's log - so you'd have to ask them about it.