I’ve been using my STM32L053 DISCOVERY board for a few months. It worked until yesterday. I wrote a program to write a 4 char array to eeprom, under my lecturers supervision, and suddenly my and four of my student mates boards “crashed“ during debugging session. I am using KeilV22.214.171.124 version, toolchain is MDK-ARM Cortex-M0/M0+ 256K.
Those are the errors that we are getting:E310 : Debug access failed - cannot read address 0xF0000FE4 (accsize ‘4’, AP ‘0’)Error: Flash download failed - Target DLL has been cancelled
We tried reinstalling the drivers and restarting our computers. We also tried reflashing firmware with STM32CubePrg, changed debug connecting settings in project options - neither of the above works to solve our problem.
Anyone has any ideas how to solve this?
Adding a picture of the errors I am getting:
Aikuka said:under my lecturers supervision
So have you asked your lecturer to help you with this?
It is far easier for someone local to help you - as they know what you've been doing, can see exactly what you have, can see exactly what's happening, etc, etc, ...
My lecturers can't find the solution to that problem. I wouldn't be asking here, I think
Sadly, asking the lecturers seems to be the last thing most students posting here think of!
Have you tried using the STLink Utility ?
No, I've only tried reinstalling and runing STSW-LINK009. Let me try it
I managed to erase all of EEPROM memory and the board seems to be working like it used to. I still can't write to eeprom what I want, but at least it is working. Thank you!
Do you really mean the EEPROM (2K - for data storage) or the Flash (program storage)?
Either way, this suggests that there was something in your code that "blocks" the debugger; eg, disabling the pins used for the debug connection.
Or, perhaps, you had "accidentally" set some protection bits ?
Yes, I do really mean the EEPROM, I used flash to name it in my previous message because flash is a type of EEPROM, if I am not mistaken
And yes, something must have been in my code as it works now up to a point. Anyway, thank you!
And if talking about protection bits, I haven't learnt about those so I can't comment on that
Aikuka said:flash is a type of EEPROM, if I am not mistaken
That is true: EEPROM = Electrically-Eraseable, Programmable, Read-Only Memory
However, the term "EEPROM" is often used to mean specifically the type of EEPROM designed for data storage - as opposed to the "Flash" used for program storage.
ST make this distinction in their datasheets:
I suspect the reason for this is historical - "EEPROM" for non-volatile data storage probably predates the (common) use of Flash for program storage.
IIRC, we had "EEPROM" for non-volatile data storage in the days of UV-EPROMs for code storage ?
Yes, I'm going to grind on my knowledge of certain definitions regarding memory and other things that go into microprocessors as a whole package
You are probably right
It's idiomatic, rather than strict, literal meaning of the words.
Like "RAM" is always taken to mean "volatile, read/write memory" - even though Flash also has random access!
I have stm32mp157a and a similar error, it helped me:1. uncheck “Debug Description - Enable” on the Pack tab.After that, the device disappears from the SW Device list on the Debug tab - but this is not an error.2. uncheck “Update Target before Debugging” in Utilities tab
good information, it helps me.
How much do you usually charge for a web development? I found only MLSDev
This is not the place to find web developers!
View all questions in Keil forum