Ford Peprah

Hello, could you elaborate on what you're doing? Do you have a sample code that reproduces the issue, as well the target hardware you're using it with?

Not sure. If you configure the logger, it should print out with some informative messages.

Do you have the logs associated with this?

I believe so. Either allowing a specific version or using the latest version will require the same code changes; some way of mapping to versions, given that the naming conventions...

Would `flash_file()` address what you are trying to do here?

You might need to add support yourself. There is a documented process on [their wiki](https://wiki.segger.com/Open_Flashloader#Create_a_Flash_Loader) outlining how to add support for an un-supported chip. I've not tried it myself, but...

Sorry about the long response here. I am on BIG Sur and I am able to export the path. What are you seeing get output when you do?

Sorry for getting back to this late. Could you elaborate? Say you have a 32-bit integer stored at memory address `0x12345678`, and you dereference and store said value in `R0`...

There are two methods: `set_little_endian()`, and `set_big_endian()`; could you try calling `set_little_endian()` before your read?

It's possible that it's something lower-level than this package than, unfortunately (possibly a regression).