atsam-rs / atsam-pac Goto Github PK

SVD files can be found https://www.keil.com/dd2/pack/ under Microchip SAM4 Series Device Support and Examples.

• Make sure svd2rust generates correctly
• Add each target to top-level Cargo.toml
• Ensure doc.rs link is valid for each target mcu
• Publish to crates.io
• Ensure README.md and Cargo.toml have the correct target mcu

Found some more issues with the svd files. Seems like some interrupts are missing.

SUPC (Supply Controller) - 0
RSTC (Reset Controller) - 1
RTC (Real Time Clock) - 2
RTT (Real Time Timer) - 3
WDT (Watchdog Timer) - 4

      ...
   <peripheral>
      <name>EFC0</name>
      <version>6450M</version>
      <description>Embedded Flash Controller 0</description>
      <groupName>EFC</groupName>
      <prependToName>EFC0_</prependToName>
      <baseAddress>0x400E0A00</baseAddress>
      <addressBlock>
        <offset>0</offset>
        <size>0x200</size>
        <usage>registers</usage>
      </addressBlock>
      <interrupt>
        <name>EFC0</name>
        <value>6</value>
      </interrupt>
      <registers>
     ...

vs.

      ...
    <peripheral>
      <name>RTT</name>
      <version>6081J</version>
      <description>Real-time Timer</description>
      <groupName>SYSC</groupName>
      <prependToName>RTT_</prependToName>
      <baseAddress>0x400E1430</baseAddress>
      <addressBlock>
        <offset>0</offset>
        <size>0x200</size>
        <usage>registers</usage>
      </addressBlock>
      <registers>
      ...

Currently they indicate the SVDs were sourced from the Atmel download site instead of

https://developer.arm.com/tools-and-software/embedded/cmsis/cmsis-search

The svd2rust pactool.sh installs is a custom one using a bleeding edge svdparser (which is required for our SVDs). This should be resolved once mainline svd2rust catches up.

Since the merge of this commit the Peripheral::take() function requiered the critical-section crate and the critcal-section feature enabled. Currently this is not possible via this crate.

May I ask why you compete with atsams-rs in publishing PAC crates for ATSAME70 series? We have matching HAL implementations from all SAMS70, SAME70, SAMV70 & SAMV71 and we publish PACs quite regularly.

Wouldn't be better to join us in efforts to maintain them?

Hi, I've ATSAM4L8 Xplained Pro board and I wanted to get started on embedded rust with this board. I've recently started working on embedded rust and I was wondering if I could get some help getting started. The slack workspace seemed like it would be a good start but I'm unable to join. Can you help me out here? Thanks!

SVD files can be found https://www.keil.com/dd2/pack/ under Microchip SAM4 Series Device Support and Examples.

• Make sure svd2rust generates correctly
• Add each target to top-level Cargo.toml
• Ensure doc.rs link is valid for each target mcu
• Publish to crates.io
• Ensure README.md and Cargo.toml have the correct target mcu

SVD files can be found https://www.keil.com/dd2/pack/ under Microchip SAM4 Series Device Support and Examples.

• Make sure svd2rust generates correctly
• Add each target to top-level Cargo.toml
• Ensure doc.rs link is valid for each target mcu
• Publish to crates.io
• Ensure README.md and Cargo.toml have the correct target mcu

ATSAM4E8C, ATSAM4E16C -> ATSAM4E_C
ATSAM4E8E, ATSAM4E16E -> ATSAM4E_E
ATSAM4LC* -> ATSAM4LC
ATSAM4LS* -> ATSAM4LS

SVD files can be found https://www.keil.com/dd2/pack/ under Microchip SAM4 Series Device Support and Examples.

• Make sure svd2rust generates correctly
• Add each target to top-level Cargo.toml
• Ensure doc.rs link is valid for each target mcu
• Publish to crates.io
• Ensure README.md and Cargo.toml have the correct target mcu