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

Initial P4 support tracking issue #2285

Open
2 of 5 tasks
MabezDev opened this issue Oct 7, 2024 · 4 comments
Open
2 of 5 tasks

Initial P4 support tracking issue #2285

MabezDev opened this issue Oct 7, 2024 · 4 comments
Assignees
Labels
chip:esp32p4 Issue related to ESP32-P4 chip
Milestone

Comments

@MabezDev
Copy link
Member

MabezDev commented Oct 7, 2024

Whilst we don't intend to do a full chip bring-up until the mass production version is released, we would like to get a minimal chip bring-up to aid future developments.

@MabezDev MabezDev added this to the 0.22.0 milestone Oct 7, 2024
@MabezDev MabezDev added the chip:esp32p4 Issue related to ESP32-P4 chip label Oct 7, 2024
@jessebraham
Copy link
Member

I again have a very basic application running on device, calling only esp_println::println!().

There is a caveat to this, in that the application works on the v1.0 devkit but neither the v1.1 not v1.2 version; I have some ideas with regards to this, but will require more experimentation. At least for the time being, I'm able to move forward using the old devkit.

Unfortunately I think getting a UART example running will take a bit more time than expected, as there is quite tight coupling between the interrupt support and various drivers. Given that the ESP32-P4 uses yet another interrupt controller (CLIC) this will take some time to sort out. Hoping to have a hacky PoC by end of week or early next week, though.

I will continue to update this issue as I make progress.

@bjoernQ
Copy link
Contributor

bjoernQ commented Oct 9, 2024

I remember we had interrupts and gpio working in January or February already

@jessebraham
Copy link
Member

I remember we had interrupts and gpio working in January or February already

Yes but there have been a number of changes to the HAL since January, and it's not as simple as copy-pasting the previous code in unfortunately. I do not think this will take a ton of time to be clear, but it will take some time to understand the changes which have been made and adapt the previous implementation to match.

@playfulFence playfulFence self-assigned this Oct 30, 2024
@playfulFence
Copy link
Contributor

playfulFence commented Oct 30, 2024

Working on this right now. I'm not sure how far I'll get, but at least I want to adapt all the changes to the current state of a driver.

PS: Civilized people call it "rebase" directly actually 😅

@jessebraham jessebraham modified the milestones: 0.22.0, 0.23.0 Nov 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
chip:esp32p4 Issue related to ESP32-P4 chip
Projects
Status: Todo
Development

No branches or pull requests

4 participants