Unknown chip id! 0x421

[Odega]

Hello, so I am completely new to working with STM boards in general. 

I just got a brand new stm32f446re board, and I tried to upload some code to it through Linux. And I do mean brand new, I haven't uploaded or downloaded any code to it before this attempt. However, when I attempted to do so, I got an error message:

"WARN common.c: unknown chip id! 0x421"

So, I looked around for a bit and tried a simple command: st-info --probe to see some internal stuff on it. But I was told this:

"No such file or directory

version:V2J33S25

serial: 066DFF534871754867255336

flash: 0 (pagesize: 0)

sram: 0

chipid: 0x421"

 

After spending roughly about two weeks trying to find stuff online, I couldn't figure out anything on what to do. So, I am very much open to suggestions if anybody knows anything about this error.

Thank you very much in advance for any help.

[Andrew Neil]

---

@Odega wrote:

 I am completely new to working with STM boards in general. .

---

Do you have experience with any other microcontroller(s)? With programming in general? Electronics?

 

---

@Odega wrote:

I just got a brand new stm32f446re board

---

What board, exactly - ST? 3rd-party? custom?

What, exactly, are you using to do the downloading?

https://community.st.com/t5/community-guidelines/how-to-write-your-question-to-maximize-your-chances-to-find-a/ta-p/575228

 

[Odega]

I am an electrical engineering student, so I have some basic experience with Stm32 boards, but nothing overly expansive. I've used keil to program one before, and know some C and Python programming languages. 

I'm just working with an stm32 nucleo f446re. And I am just using a USB cord. I have been told that for this specific code that I am working with, I was told that using a USB has worked in the past and to just do that. 

Thank you for that link btw. I'm completely new to writing on message boards like this so I didn't know any of that.

[Odega]

And for the record, I am just compiling the code on Linux (I don't know the specifics of the version of Linux or anything). I'm uploading a compiled set of code that was pre-written before I ever joined this project. But from what I have been told, the overall code portion shouldn't matter.

I got this new board because a previous one was having connection issues with the laptop I am working on, so I was hoping that the new board would work right off the bat. Should have known it is never just that easy.

[mƎALLEm]

Hello @Odega  and welcome to the community,

---

@Odega wrote:

I just got a brand new stm32f446re board, and I tried to upload some code to it through Linux. And I do mean brand new, I haven't uploaded or downloaded any code to it before this attempt. .

---

What tool are you using to connect to the board?

What board are you using? NUCLEO-F446RE?

[Odega]

Thank you for the welcome to the community.

I am using a Nucleo-F446RE.

And to connect to the board I am just using a USB cord to connect to said board. Beyond that, I am just using the Terminal that came with the laptop I was given. 

[Andrew Neil]

So what software tools are you using to download the code to the board?

And what code are you trying to download?

 

You didn't answer about your background/experience - that would help in knowing how to pitch replies...

[Tesla DeLorean]

Some old/broken tools..

 

case 0x421 : printf("STM32F446\n"); break; // Been known here for a while..

[waclawek.jan]

This is a different error message than you've posted in the initial post. It appears, that your installation of these tools is incorrect (that's why the "no such file or directory" when the tools apparently try to find the chips database which should've been installed together with the tools) and/or obsolete.

https://github.com/stlink-org/stlink

Those tools most probably output version upon --version command-line switch, try and tell us of result.You also might want to update the tools using whatever Debian's default packaging/updating tool (apt-get? I am not into Linux/Debian.)

As these are not official ST tools, ST won't support them directly. Also, there are only a few users using Linux, most users are using Windows, as do probably all the regulars here. You may be better off trying to get help through that gihub project.

JW

 

[waclawek.jan]

@Andrew Neil,

While this is an interesting information, I don't think the error messages we've seen from the st-link-project's utilities are related to the mbed tools used to compile/generate .bin.

I maintain that those utilities are of an obsolete version and/or incorrectly installed.

JW

[Andrew Neil]

---

@waclawek.jan wrote:

I don't think the error messages we've seen from the st-link-project's utilities are related to the mbed tools used to compile/generate .bin.

---

Indeed. 

It looks like the st-link-project's utilities are communicating successfully with the ST-Link, but the ST-Link is not communicating with the Target MCU.

 

---

@waclawek.jan wrote:

I maintain that those utilities are of an obsolete version and/or incorrectly installed.

---

Plausible - and that was also @Tesla DeLorean's feeling, I think.

@Odega Where did the "WARN common.c: unknown chip id! 0x421" message (mentioned in the OP) come from?

 

[Odega]

That has disappeared on its own. A professor I talked to tried to use St-link GUI to get around the chip ID unknown problem. So perhaps that got rid of that particular issue. But now we have this one. 

Side note, I didn't know that the unknown chip id error stopped showing up until you mentioned it XD.