-
-
Notifications
You must be signed in to change notification settings - Fork 4
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
Insight shows no TCA0 registers for the AVR128DA32 #111
Comments
Hi @GeorgPerthil, Thanks for reporting this. Ah yes, this appears to be due to the fact that the TCA module contains nested register groups, which Bloom doesn't support ATM. Those register groups are being ignored, and so the peripheral is considered to have no registers, which is why it's not appearing in the Insight GUI. This issue should be fixed in the next release, as I have since refactored Bloom's TDF parser to accommodate nested register groups. Both the SINGLE and SPLIT registers from the TCA module will appear in the Insight GUI, as nested groups. I still have a lot of work to do before the next release is ready, so I'm afraid you'll have to go without this fix for some time. In the meantime, you could use GDB to inspect the register. Something like:
That should print the contents of the Here's a list of the other registers for that peripheral:
|
To inspect all registers in that peripheral:
That will print all 61 bytes from the |
I have Bloom 1.0.0 installed on an Ubuntu 22.04.4 LTS. I can connect to the AVR (using mEDBG), but as mentioned in the title, there is no TCA0 shown in the target registers. I also tried an ATtiny1626, there is no TCA0 too. Maybe, it is because the TCA0 can be run in single and split mode? MPLAB-X shows both modes.
The text was updated successfully, but these errors were encountered: