Adding warning about serial IRQ timing

This commit is contained in:
Rodrigo Alfonso
2024-01-19 02:25:06 -03:00
parent 0779535b2c
commit 0ee48ab24d
2 changed files with 17 additions and 6 deletions

View File

@@ -27,9 +27,14 @@
// // ...
// }
// --------------------------------------------------------------------------
// (*) libtonc's interrupt handler sometimes ignores interrupts due to a bug.
// That causes packet loss. You REALLY want to use libugba's instead.
// (see examples)
// (*1) libtonc's interrupt handler sometimes ignores interrupts due to a bug.
// That causes packet loss. You REALLY want to use libugba's instead.
// (see examples)
// --------------------------------------------------------------------------
// (*2) The hardware is very sensitive to timing. Make sure your interrupt
// handlers are short, so `LINK_CABLE_ISR_SERIAL()` is called on time.
// Another option would be activating nested interrupts by setting
// `REG_IME=1` at the start of your interrupt handler.
// --------------------------------------------------------------------------
// `send(...)` restrictions:
// - 0xFFFF and 0x0 are reserved values, so don't send them!

View File

@@ -29,9 +29,15 @@
// // ...
// }
// --------------------------------------------------------------------------
// (*) libtonc's interrupt handler sometimes ignores interrupts due to a bug.
// That causes packet loss. You REALLY want to use libugba's instead.
// (see examples)
// (*1) libtonc's interrupt handler sometimes ignores interrupts due to a bug.
// That causes packet loss. You REALLY want to use libugba's instead.
// (see examples)
// --------------------------------------------------------------------------
// (*2) For CABLE mode:
// The hardware is very sensitive to timing. Make sure your interrupt
// handlers are short, so `LINK_UNIVERSAL_ISR_SERIAL()` is called on time.
// Another option would be activating nested interrupts by setting
// `REG_IME=1` at the start of your interrupt handler.
// --------------------------------------------------------------------------
// `send(...)` restrictions:
// - 0xFFFF and 0x0 are reserved values, so don't use them!