What is in the address space where the true vectors would normally be found?
This is what I'm finding with some AI help... While the '816 is a general-purpose CPU, the '265 includes built-in peripherals like UARTs, timers, and twin sets of bus interfaces (ABUS, XBUS). To manage these without ...

I tracked down the issue. I was using an incorrect interrupt vector for COP. I was using $FFE4, but that's for the 65816. The 65265 uses $FFB4 instead!

Thank you for all of that! I'll need to do more debugging. I moved the COP call to bank $00 to simplify testing (with no luck). I also need to do more research on the 65265 and COP, in case there's something special that needs to be configured on the '265.

In my W65C265S build (internally a 65816), I am looking at COP to call operating system routines from a secondary ROM. My secondary ROM starts at bank $40, with my operating system and interrupt vectors in bank $00. From my secondary ROM, I call cop 1 . From my OS ROM, I have:

cop_handler ...

I was able to get interrupt shadow vectors working. It came down to writing vectors at $00:0100. If you're interested, I posted more details to https://www.rehsdonline.com/post/w65c26 ... ow-vectors.

I have PIB working! Below is what I ended up with for connections to connect two '265 boards. For the most part, connect port 4 to port 4 and port 5 to port 5 (minus the NMI and IRQ lines of port 4).

connections_working.png
In case anyone is interested, I posted additional details, including code ...

Here's where I'm currently at with connectivity between two '265s. Thanks to handyandy for suggestions on this design. I'll be ordering a first attempt of a PCB for this later this month. I'll post an update when I can validate the design. Thanks!

Quick question: is the parallel interface bus a '265 specific thing or is it just a pair of '265s on the same parallel bus?
It's a specific feature of the '265. WDC describes it as "The Parallel Interface Bus (PIB) is used to communicate instructions and data to and from task oriented processors ...

Would anyone happen to have resources to help me better understand hardware and software implementation of PIB (parallel interface bus) on a pair of W65C265S MCUs? I'm very interested in a sample schematic of a PIB implementation, and any code samples would also be quite helpful. I have been ...

Here's the code I have with interrupts working (but not shadow interrupt vectors): https://github.com/rehsd/microcontollers/blob/main/W65C265S/1602_LCD_PS2KBD.asm .

I posted a video with the progress I have made so far. If you're interested... https://youtu.be/4PiMg2al97U.

There are still a lot of ...

I have interrupts working now using an external flash (keeping with the $FFxx vectors). I still haven't been able to get shadow vectors working. If anyone has an example of shadow vectors on the W65C265S or SXB board, please let me know. I'll post an update on interrupts in the coming days with more ...

Thank you, Dr Jefyll!

To help with debugging, I do toggle an LED (PD72) in the ISR. Additionally, I am writing to $2F00 some markers to help me track progress as it runs. I initialize this space with 55s and then progressively fill in values just to track progress. The markers I try to write during ...

Hi, everyone. I am trying to get interrupts to work on a W65C265SXB board and not having any luck. Is anyone aware of sample project code that includes processing interrupts, such as an edge interrupt on one of the supported pins?

I am uploading my assembled program with easysxb and jumping to the ...

One other quick update... I did find a self-activation email in my new email account's spam folder. So, you don't need to have an admin help re-activate your account. Just check your spam folder.

I switched my forum account over to a different email address with a different provider. I am now using Gmail, and I am receiving notifications!