Skip to content

this adds new Microchip AVR-Dx series microcontrollers

tukadadev requested to merge (removed):master into master

This adds couple AVR-Dx series devices. But not all of them. Second attempt. I could not add commit to started merge request, so I am creating new merge request. Previous merge request numbers were !3302 (closed) !3303 (closed)

I plan add more AVR-Dx devices of them in future.

Screenshot_2021-08-29_104907

Screenshot_2021-08-29_104931

Screenshot_2021-08-29_104946

Screenshot_2021-08-29_105007

Screenshot_2021-08-29_105025

Screenshot_2021-08-29_105041

Screenshot_2021-08-29_105054

Screenshot_2021-08-29_105112

datasheets: https://ww1.microchip.com/downloads/en/DeviceDoc/40002183A.pdf https://ww1.microchip.com/downloads/en/DeviceDoc/AVR128DB28-32-48-64-DataSheet-DS40002247A.pdf

Have a nice day.

Required Settings:

Please configure your personal fork of the KiCad project with the following settings:

  1. Settings->General->Visibility->Pipelines should be enabled and set to "Everyone with access".
  2. Settings->CI/CD->General Pipelines timeout should be set to >3h .

Configure the merge request as follows:

  1. The "Allow commits from members who can merge to the target branch." option check box at the bottom of your merge request must be checked.
  • This can later be enabled via the edit button found at the top right (in case you forgot to do it when creating the merge request).

#General Guidelines: All contributions to the kicad library must follow the KiCad library convention

Thanks for creating a pull request to contribute to the KiCad libraries! To speed up integration of your PR, please check the following items:

  • Provide a URL to a datasheet for the symbol(s) you are contributing
  • An example screenshot image is very helpful
  • Ensure that the associated footprints match the official footprint library
    • A new fitting footprint must be submitted if the library does not yet contain one.
  • If there are matching footprint PRs, provide link(s) as appropriate
  • Check the output of the automated check scripts - fix any errors as required
  • Give a reason behind any intentional library convention rule violation.
Edited by tukadadev

Merge request reports