Forum : ARM
Original Post
| Post Information | Post |
|---|---|
|
August 5, 2020 - 8:34pm
|
Have using this for years. I had to buy a new unit and re-install the ride software but keep getting this error WRONG DEVICE ID 0x20036410 What could be causing this ? Thanks |
Hello,
This message usually means that the device selected in the software options is different from the device physically connected on the board.
Could you please check that?
If they match and you still get the error, please tell us which device you are using and which version of the software (Ride & RKit-ARM) you are using.
Best Regards,
Vincent
Still getting the same message. I am using the Rlink Standard
Ride 7 ver 7.70.19.0218 Enterprise version
Rkit-ARM for Ride 7 1.72.19.0253 Lite Suite
Although I am not 100% sure I know what you mean in the first sentence
Hello,
There are many variants of STM32. (STM32F103xE, STM32G070xB, etc.)
You need to tell the software which variant of STM32 you are using. This is done in the options/configuration.
The message that you see usually comes if you select a variant in the options but you connect another variant on the board.
See the GettingStarted doc for more details. (it depends if you are using Ride, RFlasher; or Cortex_pgm)
Best Regards,
Vincent
Good morning.
We have a RLink Standard with ARM Enterprise Dongle that worked correctly the last days with the following packages installed:
- Ride7_7.70.19.0218
- RKit-ARM_1.72.19.0253
But it has stopped starting debugging, staying blocked and the RUN LED On.
We have verified that it is able to read the voltage from the board correctly
and deletes and writes the Flash in the range of addresses indicated on the screen.
Please, we need a solution, thank you.
Best regards.
Hello,
If you can measure VCC and program the flash, then the RLink hardware and USB drivers are OK.
This looks like a problem in the application firmware, probably in the startup code, vectors, option bytes, ... did you change anything in your source code or Ride project?
It could also be related to the hardware, probably boot pins or reset... did you change anything?
I recommend trying the Count example provided with Ride, if possible on a commercial demonstration board (REva, ST-Eval, etc.) just to determine if the issue is in the RLink or PC software. Please tell us the results.
Best Regards,
Vincent
PS: please post new questions in new posts, rather than posting them as answers to other questions in old posts. ;)
Hello,
Thanks for your fast answer.
Following your recommendations we were able to fix the problem by enabling the LD Linker Script in the project properties.
Best regards.