Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Compiled Software Breakpoints #89

Open
cr1901 opened this issue Sep 25, 2019 · 1 comment
Open

Compiled Software Breakpoints #89

cr1901 opened this issue Sep 25, 2019 · 1 comment

Comments

@cr1901
Copy link
Contributor

cr1901 commented Sep 25, 2019

I'm willing to add (a limited version of1) this feature myself- it should be simple enough (famous last words), but the TI-provided debuggers allow you set an EEM trigger which triggers whenever the data lines see a specific opcode bit pattern.

This can be used to create software breakpoints by erasing the flash and storing the erased opcode in a table, but what I need is the ability to breakpoint on the NOP pattern 0x4343 when this pattern was precompiled for some software I'm debugging.

Does mspdebug allow you to create data triggers for the EEM? If so, how would you accomplish this? I have not found any documentation online for the EEM- even my family manual (slau208q.pdf) has barely anything on it.

  1. I would create an option to enable software breakpoints at the cost of one hw breakpoint/trigger. I just don't know the sequence of EEM writes that accomplishes this...
@smunaut
Copy link

smunaut commented Sep 25, 2019

The source code for the MSP-FET firmware is available and contains some register definition for the EEM. It's not a "doc" per-se but that's the best I found when I looked the last time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants