Test Environment (required)
You can use MEGA65INFO to retrieve this.
Platform: Mega65 R3a
Core Commit: development (9f62d25)
ROM Release: 920377
Describe the bug
When using the Ethernet I/O personality, the content of the RX ethernet buffer should be visible to the CPU at $d800, but this is actually not working, only colour RAM data is available there. Same if accessing ffd2800, which should always provide the ethernet personality (not using the special $d02f knock sequence).
To Reproduce
Steps to reproduce the behavior:
Fill colour RAM with some known pattern
Enable Ethernet I/O personality
Check data at $d800 or $ffd2800, it still shows colour RAM data instead of the RX eth buffer
Additional context
@gardners confirmed that the development branch seems to lack the needed mapping code in the core. It needs to be checked whether this is a regression or was like that already for older bitstreams.
Test Environment (required) You can use MEGA65INFO to retrieve this.
Describe the bug When using the Ethernet I/O personality, the content of the RX ethernet buffer should be visible to the CPU at $d800, but this is actually not working, only colour RAM data is available there. Same if accessing ffd2800, which should always provide the ethernet personality (not using the special $d02f knock sequence).
To Reproduce Steps to reproduce the behavior:
Expected behavior Ethernet RX buffer visible instead
Additional context @gardners confirmed that the development branch seems to lack the needed mapping code in the core. It needs to be checked whether this is a regression or was like that already for older bitstreams.