Closed hanetzer closed 2 years ago
Did I understand right?
You've used svdtools convert
to convert SVD to YAML, but backward conversion doesn't work?
Backwards conversion of the rp2040.yaml to rp2040.svd works, but my hand written hi3521a.yaml will not convert.
address_block
is an array of AddressBlock
s:
https://docs.rs/svd-rs/0.13.1/svd_rs/peripheral/struct.PeripheralInfo.html#structfield.address_block
ah derp. got tunnel vision because of the line/column and didn't notice the actual error.
Actually, I found a conversion issue. When converting a yaml to svd, the resultant svd file does not contain the schema information some svd tools (in my case, SVD-Loader-Ghidra) require for operation. Converted SVD:
<device schemaVersion="" xmlns:xs="" xs:noNamespaceSchemaLocation="">
'real' SVD:
<device schemaVersion="1.1" xmlns:xs="http://www.w3.org/2001/XMLSchema-instance" xs:noNamespaceSchemaLocation="CMSIS-SVD.xsd">
reinstall with cargo install svdtools --force
Yep, that fixed that. Thanks for the info.
Ello. I'm using the rust svdtools program to build an svd for a chip without one. I started by converting the rp2040.svd to rp2040.yaml as a reference, and began writing the yaml for my chip, to convert to svd later for use with gdb and such. Some of the data is dummied out (for instance, its not a traditional mcu, but is a cortex-a7 proc). Attempting to convert with what I currently have (below) results in the following error:
[2022-04-11T13:49:24Z ERROR svdtools::cli] peripherals[0]: invalid type: map, expected a sequence at line 20 column 9
Line 20 column 9 translates to the:
before BOOT_ADDR; this seems correct, as the rp2040.yaml file has the same kind of setup:Am I missing something or is this a legit bug?