Overriding linker location for a single IDF routine?

[ESP_Sprite]

FWIW, theoretically at least, there's always the option of connecting the GPIO interrupt to a high-level interrupt and writing the handler in assembly... not sure if that's needed in your case, but it's there.

Also, forgive me for being curious, what bus is that? I'm not aware of that many 4-bit buses, and this doesn't sound like any of them.

[go4retro]

FWIW, theoretically at least, there's always the option of connecting the GPIO interrupt to a high-level interrupt and writing the handler in assembly... not sure if that's needed in your case, but it's there.

Well, if there's a way to code the entry and exit and the GPIO piece in ASM, and someone can help me with it (my ASM is so rusty on any platform), I'm game. At this point, I wonder how much the switch from C to ASM would shave off.

Also, forgive me for being curious, what bus is that? I'm not aware of that many 4-bit buses, and this doesn't sound like any of them.

Though I have a more prevalent bus support in mind, I didn't want to try the esp32 for work until I could prove out the timing. It turns out I have a personal itch to scratch with a bus that shares many of the same electrical characteristics (non serial, open collector lines, clock line carries additional signaling), so I thought I'd try the esp32 out in my personal time before introducing it to work.

The bus is called HEXBUS:

https://en.wikipedia.org/wiki/Hexbus

I guess it's called HEX Bus because there are 6 signal lines (HSK, BAV, DATA 0-3)

I thought about trying to use some of the peripherals on the esp32 to handle it, but nothing seemed to fit.

Jim