You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
See platformio/platform-atmelavr#238 for the SVD files that this occurrs with. Tested with the Arduino Uno json file as described. platformio.ini and code as per this. If this is resolved, we would have a peripheral views for the Atmel chips, and therefore getting closer to what Atmel Studio offers.
On a sidenote, when loading the SVD files in CLion (in the "Peripherals" tab for a "PlatformIO Debug" target), it doesn't complain
And can read out some registers / addresses (but the wrong value?! They don't make sense as 32-bit values), but fails to read out the I/O registers. Probably becauase AVR memory spaces are weird and it's using the wrong commands to read them from the SRAM space (and not the Flash space) or avr-gdb has a bug or avr-stub has a bug.
The text was updated successfully, but these errors were encountered:
It was obvious it is missing some element when parsing the XML of the SVD. By trial-and-error in comparison with a working SVD I've found that the error disappears when something like
If it helps, I have been hacking on that minified extension.js and narrowed the problem to strange indexing in loadSVD and parse* in PeripheralTreeProvider. It looks to be taking the first character of the input strings rather than the strings themselves. Is it expecting an array? Also, the function that parses integers depending on prefix needs validation on the input.
See platformio/platform-atmelavr#238 for the SVD files that this occurrs with. Tested with the Arduino Uno json file as described.
platformio.ini
and code as per this. If this is resolved, we would have a peripheral views for the Atmel chips, and therefore getting closer to what Atmel Studio offers.On a sidenote, when loading the SVD files in CLion (in the "Peripherals" tab for a "PlatformIO Debug" target), it doesn't complain
And can read out some registers / addresses (but the wrong value?! They don't make sense as 32-bit values), but fails to read out the I/O registers. Probably becauase AVR memory spaces are weird and it's using the wrong commands to read them from the SRAM space (and not the Flash space) or
avr-gdb
has a bug oravr-stub
has a bug.The text was updated successfully, but these errors were encountered: