You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the RX_ERROR_HANDLER: routine (in /firmware/rosco_m68k_v1/base_servers/serial_isr.S), the arguments passed to the C function handleRxError are not correctly cleaned up (required since -mrtd is not used in this codebase). This will cause the registers to be 'restored' to incorrect value and probably lead to a crash.
Need to look in to the GCC M68K ABI to see how these (byte-sized) arguments should be properly passed (suspect as a uint32) and then make sure they're cleaned up properly after the function call.
The text was updated successfully, but these errors were encountered:
# This is the 1st commit message:
First cut SPI and SD libs|
# This is the commit message #2:
First steps reading FAT filesystem
# This is the commit message #3:
Additions and bugfixes
# This is the commit message #4:
Add FAT support
# This is the commit message #5:
Major speed and size improvements
# This is the commit message #6:
First cut working SD in ROM
# This is the commit message #7:
First cut working SD in ROM
# This is the commit message #8:
Make build automagical
# This is the commit message #9:
Remove ROMs from VC and ignore them
In the
RX_ERROR_HANDLER:
routine (in/firmware/rosco_m68k_v1/base_servers/serial_isr.S
), the arguments passed to the C functionhandleRxError
are not correctly cleaned up (required since -mrtd is not used in this codebase). This will cause the registers to be 'restored' to incorrect value and probably lead to a crash.Need to look in to the GCC M68K ABI to see how these (byte-sized) arguments should be properly passed (suspect as a uint32) and then make sure they're cleaned up properly after the function call.
The text was updated successfully, but these errors were encountered: