Re: [OpenOCD-user] Flash Dialog parts?

[Paul F. <fer...@gm...>]

Hi,

On Mon, Dec 12, 2022 at 10:38:31AM -0800, Rafael Send wrote:
> They have told us specifically that they do NOT support any open source tools -
> which is a shame since we are using OpenOCD for the rest of our products.

It's a shame indeed!

> If I understand correctly, what is missing would be the memory layout for the
> Dialog flash, or is it something else that makes OpenOCD compatible with a
> particular chip?

Basically, you need to understand how to modify the flash on the
target. Usually the information is available in the datasheet to allow
self-programming usecases (such as bootloaders).

> How hard would it be to add support for a chip that is not supported by the
> vendor? Could this be reverse-engineered?

It shouldn't be too hard, no, especially if the datasheet has the
necessary details. If not, you can probably disassemble the DLL they
supply for Keil and learn the information you need from there.

Usually flash driver support constists of two parts: some small helper
running on the target that's reading data from ring buffer and writes
to flash, and the host part that detects flash capacity, prepares,
erases, locks/unlocks etc. Plenty of examples is src/flash/nor. After
you check the datasheet and have general idea of what the process
would look like for your particular target, we'll be able to find a
similar flash driver for your inspiration.

If anything's unclear I suggest you ask on the devel mailing list
and/or the IRC channel.

-- 
Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software!
mailto:fer...@gm...