Looks like the macro was defined with a space instead of an underscore, breaking the intended macro name.

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