Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Tracking issue] Platform support/wishlist #92

Open
2 tasks
enderger opened this issue Dec 2, 2022 · 9 comments
Open
2 tasks

[Tracking issue] Platform support/wishlist #92

enderger opened this issue Dec 2, 2022 · 9 comments

Comments

@enderger
Copy link

enderger commented Dec 2, 2022

Currently, the number of supported platforms is rather minimal. If the owners are alright with it, I'd like to designate this issue as a tracking issue for boards/chips which are not yet implemented in here with the aim of getting a good selection supported.

To start off the list, here's a few chips I have come across:

  • ATMega644/A (chip)
  • ATTiny25/45/85 (chip)
@ikskuh
Copy link
Contributor

ikskuh commented Dec 3, 2022

Those two shouldn't be a problem to bring up, but i'd wait for the regz rewrite to complete, so we can easily generate just all ATtiny and ATmega descriptors/register files and ship them in a avr package for microzig

@ikskuh
Copy link
Contributor

ikskuh commented Dec 3, 2022

Ah but: We can make this issue a good tracking issue for platforms people want to see!

@ikskuh ikskuh changed the title [Tracking issue] Platform support [Tracking issue] Platform support/wishlist Dec 3, 2022
@ikskuh ikskuh pinned this issue Dec 3, 2022
@zwn
Copy link

zwn commented Mar 23, 2023

I'd like to see puya py32 series supported (we are using the 003 model):

SVD files are available in the downloadable zip file hidden at the far right after horizontally scrolling through the table, in a column named Datasheet at the manufacturer site.

If that is something I could help with, I am willing to try.

@sogwms
Copy link

sogwms commented May 14, 2023

please support vexpress-a9 (on qemu)

@Khitiara
Copy link

is the 6502 applicable to microzig or is that more suitable for general zig rather than here?

@ikskuh
Copy link
Contributor

ikskuh commented May 14, 2023

is the 6502 applicable to microzig or is that more suitable for general zig rather than here?

See ziglang/zig#6502. Right now, Zig cannot compile to the 6502, so we can't target it either. MicroZig is a framework and library for Zig, not another programming language. Also 6502 isn't an embedded target, more a regular "PC CPU" in that regard

mattnite pushed a commit that referenced this issue Feb 26, 2024
mattnite pushed a commit that referenced this issue Feb 26, 2024
mattnite pushed a commit that referenced this issue Mar 1, 2024
@GustavoSchip
Copy link

GustavoSchip commented Apr 20, 2024

Is there a way to support the Arduino Nano RP2040 Connect?
It does have loads of peripherals but the pinout of the board is different from the standard Pico.
If the correct pins and their features can be used that would be awesome!

@ikskuh
Copy link
Contributor

ikskuh commented Apr 21, 2024

Is there a way to support the Arduino Nano RP2040 Connect? It does have loads of peripherals but the pinout of the board is different from the standard Pico. If the correct pins and their features can be used that would be awesome!

You can always use a Pico as a base board, as long as the flash and clock does match. Apart from that, GPIOs are always numbered GPIO0 to GPIO30, so you can just look them up in the schematic :)

@GustavoSchip
Copy link

Is there a way to support the Arduino Nano RP2040 Connect? It does have loads of peripherals but the pinout of the board is different from the standard Pico. If the correct pins and their features can be used that would be awesome!

You can always use a Pico as a base board, as long as the flash and clock does match. Apart from that, GPIOs are always numbered GPIO0 to GPIO30, so you can just look them up in the schematic :)

I assume that the clock is the same, it would make sense from a compatibility perspective. Il look into it, thanks! 👍

Just labelling pins without restricting what it does is indeed the more versatile approach, that way a wide variety of RP2040 boards are supported! 🎉

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants