Tommy Murphy

As I said before when you end up in the trap handler with `$mcause == 0x2` (illegal instruction) then `$mepc` gives the address of the instruction that caused the exception....

If the illegal instruction exception is happening on the `fscsr` instruction at 0x08000030 in the second disassembly listing, then it suggests to me that the target hart doesn't support floating...

Seems that, regardless of what code you're using, the problem is always an illegal instruction exception. That being the case I doubt that any code that runs before your program...

Your screenshot is difficult to read and posting screenshots isn't really a good way to provide info in any case. You would be better off posting a verbose -d OpenOCD...

You didn't attach a verbose OpenOCD log generated using `-d`.

What is your command line for invoking OpenOCD? The following suggests that you're not passing any script(s) from the command line so it falls back to openocd.cfg (in the current...

> Error: invalid subcommand "driver ftdi" That's a different error to your earlier post and suggests some problem with your script that needs to be fixed according to the OpenOCD...

I don't think that that would fit the OpenOCD way of doing things which should allow for examine() with no reset - e.g. when one wants to debug by connecting...

> init is the TCL command that ends up calling examine(). You can only run init once. The code enforces this explicitly. I'm confused by this. I'm not aware of...

Thanks Tim - missed that. But it's odd because none of the scripts that I have ever used for RISC-V or Cortex-M explicitly call `init` and yet `examine()` does get...