This is the workspace for the nxp-pac crate and supporting utilities.
If you want to regenerate the pac, you need to clone with --recursive.
If you forgot this, you can use git submodule update --checkout --init to fetch the submodules.
This crate is in transition from generating the PAC from the NXP provided SVD files, to a metapac approach where the SVD is only used to extract general peripheral definition files. A metapac definition file then specifies which peripherals are included in the chip. This is very useful when a vendor has used similar peripheral IPs across their portfolio. This allows HAL authors to write drivers for these peripheral IPs, instead of having to copy-paste them for each supported chipset.
Because the crate is in transition, some of them use the PAC method, and some of them are part of the metapac.
| Chip | Type |
|---|---|
| MIMXRT1011 | PAC |
| MIMXRT1062 | PAC |
| MIMXRT1064 | PAC |
| MIMXRT685S | PAC |
| LPC55S16 | PAC |
| LPC55S69 | PAC |
| MCXN947 | PAC |
| MCXA256 | MetaPAC |
| MCXA577 | MetaPAC |
The data directory contains the SVD files, board metadata, and chiptool transformations needed to
generate the nxp-pac crate. This data is used by the code generation tool.
The generator directory contains the code generation tool for generating the code in the nxp-pac crate.
If you want change the way the nxp-pac crate is generated please see this directory.
The nxp-pac directory contains the nxp-pac crate. If you are looking for a peripheral access crate for
an NXP microcontroller, please see this directory. You should never need to manually edit the source
code in this directory. The metadata will need to be updated to support new microcontrollers.
The contents of this crate are auto-generated and licensed under the same terms as the underlying SVD file, which is licensed by NXP under a BSD-3-Clause license.