Initial P4 support tracking issue

[MabezDev]

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.

• [x] PAC support
  • We have a PAC already in esp-pacs, will require patching I'm sure but at least for now we can probably consider this subtask complete
• [x] Linker and required soc module features
• [ ] Tooling(?)
  • https://github.com/esp-rs/espflash/pull/686
  • https://github.com/probe-rs/probe-rs/pull/2047
• [ ] Uart driver
• [ ] HIL runner

[jessebraham]

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]

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

[jessebraham]

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.