John O'Hare

With the workaround for delayMicroseconds in place the problem with Serial.read remains. Character are corrupted or missed.

[SerialPrint.ino.hex.zip](https://github.com/SpenceKonde/ATTinyCore/files/11554347/SerialPrint.ino.hex.zip)

The active code is in /Arduino/hardware/ATTinyCore/avr/cores/tiny/TinySoftwareSerial.cpp although there is also a SoftwareSerial at Arduino/hardware/ATTinyCore/avr/libraries/SoftwareSerial/SoftwareSerial.cpp in the core. No suprises, the issue is in the interrupt code. The interrupt is happening...

I have not made any progress on this other than to use "No line ending" if using the Serial Monitor built into the Arduino package. When using other endings then...

I was looking at this yesterday. May I ask which T84 core you are using. Does your change have implications for the JeeMicro hardware?

You have been having fun. We did know about the active high on the RFM69 but never saw it as an issue on the T84 since we typically only use...

Sorry @dzach I missed this post. I try not to use Win as much as possible but I will try to set things up again and see if I can...

I have just updated my Win7 with latest patches and downloaded a fresh .exe file from: [here](https://github.com/dzach/nrfmon/blob/master/binaries/nrfmon.exe?raw=true) The program runs and grey scan lines scroll down the window. The red...

Running the .exe as an administrator has similar issues: > ● nRfMon v0.7.6 (C) 2013,D.Zachariadis Licensed under the GPLv3 ϟ Connect (//./COM5) . Connected ● JeeNode.v6 live . Listening error...

The JeeNode USB is operational as in can receive my background traffic when running rf12Demo.ino.