I forgot to remove the default eventhandlers from some of the HardwareSerial files as such the ones in the serialEventX files was not used and why my flags were not set properly.

Could have done simple fix, but decide to make it more consistent with what I did in T3.x/LC code and not look through all the NULLS, but simply have list of active ones and count of active.

Appears to fix the issue so far.

Found a way that appears to work to detect if a sketch has our default serialEvantX functions, and that the users code has not implemented their own.  Before on SerialX.begin() I would add that serial ports code to table of function calls to do the if SerialX.available() call serialEvernt..

But I now have a hacked up version where each of the event functions are in their own source file, along with a variable that is defined.  Elsewhere I have those same variables defined with an attribute of ((weak)), so if our default implemention is pulled in it is defined with a value of 1, if the weak version is used because the user has their own implemention, then  it is defined as a 0... So I can detect this at the begin method and only add the code to do the checks in yield if the user implemented it.

WARNING this also brought in changes for using XBar pins for CTS and RX pins... As I did not wish to split back out and have you maybe have to manually merge.

A couple of minimalist changes.

systick_isr - By default it does nothing with the event responder.
Only if the user calls the attachInterrupt member of EventResponder will it install the version of the ISR that checks the list for any active ISR event Responders.

T4 Yield - try to keep bitfields for things yield should test
Make it such that yield hopefully can test to see there is nothing to do and returns quickly.

There are some interesting limitations, that is that the serialEvent
handling code. Both for USB and hardware Serial can only remove it self
if the default eventHandler is called once, as I don't know anyway to
detect if the default code (weak linkage) is included or if it is a user
version.  So waits until called to remove it self from active list.
Sketches can force this by simply calling the event method right after
calling begin on the serial port.

Later, we should check if we can reduce the bias, also (For me, it works with minimal bias -but I think should should keep it for now, as it is).

fixes #464

It never came up much with T4 as there were not really alternative pins...

But fixed and tested with simple sketch on T4.1 and simple jumper to TX and RX pins on memory chip locations

A few of the T4 and now T4.1 Serial ports support a CTS pin.  One was previous fixed, added the others to tables.

Also T4.1 has Some Serial port pins in the area that the optional memory chips could be installed

https://forum.pjrc.com/threads/60174-Understanding-The-USB-Specification

The actual objects were not created like they were on the T3.x side, so just copied it over from there.

usb.c did not include the usb_rawhid.h so it would give a compiler warning about having to create a ...

Decided to go ahead and move the TX Buffer there as well
Did a quick check in earlier test program to echo the contents back.

The other test program was already setup to receive data on the HID and does hex dump of buffer which looks correct.  So far so good.

Testing against issues of hang from thread:
https://forum.pjrc.com/threads/59881-RawHID-recv()-hangs-after-updating-to-Teensyduino-1-4-9-or-higher-for-Teensy-4-0/page2

F_CPU -> F_CPU_ACTUAL

- trap unused memory regions
- trap nullptr
- trap stack overflow

This answers a long standing question :-)

https://github.com/PaulStoffregen/cores/issues/424#issue-555760117

see RM V2 Page 3221

https://forum.pjrc.com/threads/59815-teensy-4-0-XBAR-questions?p=231803&viewfull=1#post231803

https://forum.pjrc.com/threads/59815-teensy-4-0-XBAR-questions