ARM
Re: ARM
Based on what the chip give you access to ![Smile :-)](./images/smilies/icon_e_smile.gif)
Usually, every MCU with own Flash is ment to be erased and programmed only. This is because normally there is no need to read back it's contents, as a developer can always reprogram it.
Most Chipvendors (STM also) have debug-adapters and software to do all those stuff.
And also every MCU has so called "fuses" which may prevent a readback by protocol, even if it exist.
So if the chip is read-protected, there is no way of getting the content in an usual way (even JTAG). You need some security holes to do so. Maybe in hardware maybe in the running program. One could be that you are able to store an own program in the MCUs SRAM which then reads the Flash contents and send it byte by byte out to some common interface (USB, serial, JTAG, an IO-Port, whatever).
To answer you question as short as you wrote it: "NO, there is no easy way to do".
![Smile :-)](./images/smilies/icon_e_smile.gif)
Usually, every MCU with own Flash is ment to be erased and programmed only. This is because normally there is no need to read back it's contents, as a developer can always reprogram it.
Most Chipvendors (STM also) have debug-adapters and software to do all those stuff.
And also every MCU has so called "fuses" which may prevent a readback by protocol, even if it exist.
So if the chip is read-protected, there is no way of getting the content in an usual way (even JTAG). You need some security holes to do so. Maybe in hardware maybe in the running program. One could be that you are able to store an own program in the MCUs SRAM which then reads the Flash contents and send it byte by byte out to some common interface (USB, serial, JTAG, an IO-Port, whatever).
To answer you question as short as you wrote it: "NO, there is no easy way to do".
-
- Pro
- Posts: 364
- Joined: 04 Aug 2019, 22:47
Re: ARM
I've broken 2 UC DS clones tring to read their firmware
![Very Happy :D](./images/smilies/icon_e_biggrin.gif)
What I have started doing is developing my own code to have that STM behave like an UC DS - well at least be recognised by Windows drivers as one.
Next step is making them comunicate with the clone version of software. I can get data to them, but didn't manage to send something back.
If I'm following examples of STM to make it work as a USB to COM adapter it works.
I'm trying to makke UC DS think that I have something real and use its firmware update procedure to get the needed code
![Rolling Eyes :roll:](./images/smilies/icon_rolleyes.gif)