Forum Replies Created
-
Posts
-
Sorry, I was still referring to flashing (http://stackoverflow.com/questions/23895253/how-to-erase-just-some-bytes-of-flash-memory).
If a device has a block size of, say, 1 KB, that would still permit flash editing at that granularity, so I’m not sure if that’s the problem.
Thanks, I’ll have to look more into linker scripting.
First it seemed odd there’s no simple way to selectively write memory regions but I guess that’s to do with the flash block-size grain limitation.
Other debuggers probably have a copy-modify-writeback function? Feature Request?
Hi,
this thread would benefit from clarification what’s a valid ISR vector placement.
The two methods mentioned here are simple loader script MEMORY FLASH ORIGIN editing or placing your function in a specific section.
How does that interplay with custom bootloaders (stmduino, etc…) which locate themselves at 0x8000000 and jump to e.g. 0x8005000 for non-bootloader mode?
