pert
January 5, 2021, 6:12pm
2
dsouleles:
That's correct.
dsouleles:
It seems as if this is intentional. You can see here an 8 year old report of the same issue as it occurs on the Arduino Leonardo:
opened 07:02PM - 15 Nov 12 UTC
closed 09:09AM - 17 Sep 19 UTC
This is [Issue 1031](http://code.google.com/p/arduino/issues/detail?id=1031) mov… ed from a Google Code project.
Added by 2012-09-03T19:30:50.000Z by [pilot...@gmail.com](http://code.google.com/u/107526621707702953137/).
Please review that bug for more context and additional comments, but update this bug.
Original labels: Type-Defect, Priority-High, Component-ATmega32U4
### Original description
**What steps will reproduce the problem?**
1. Load Examples ... 04. Communcations... SerialEvent example
2. Add while (!Serial) ; after Serial.begin() in setup
3. Upload to a Leonardo board, type stuff in the serial monitor
**What is the expected output? What do you see instead?**
Expected: Get back what I typed
Actual: Got nothing back
**What version of the Arduino software are you using? On what operating**
**system? Which Arduino board are you using?**
Arduino 1.0.1 on MacOS X 10.7.4 with a Leonardo R3 board
**Please provide any additional information below.**
I believe serialEvent is never called. I tried renaming it to serialEvent1 and serialEvent2 without any effect.
The issue was closed by Arduino's lead firmware developer with this comment:
Anyway, serialEvent is due to deprecation, so no fixes will be applied to code not working today.
What is indisputably a bug is that this fact is not documented. I have a plan to correct this lack of documentation:
opened 07:02PM - 15 Nov 12 UTC
closed 09:09AM - 17 Sep 19 UTC
This is [Issue 1031](http://code.google.com/p/arduino/issues/detail?id=1031) mov… ed from a Google Code project.
Added by 2012-09-03T19:30:50.000Z by [pilot...@gmail.com](http://code.google.com/u/107526621707702953137/).
Please review that bug for more context and additional comments, but update this bug.
Original labels: Type-Defect, Priority-High, Component-ATmega32U4
### Original description
**What steps will reproduce the problem?**
1. Load Examples ... 04. Communcations... SerialEvent example
2. Add while (!Serial) ; after Serial.begin() in setup
3. Upload to a Leonardo board, type stuff in the serial monitor
**What is the expected output? What do you see instead?**
Expected: Get back what I typed
Actual: Got nothing back
**What version of the Arduino software are you using? On what operating**
**system? Which Arduino board are you using?**
Arduino 1.0.1 on MacOS X 10.7.4 with a Leonardo R3 board
**Please provide any additional information below.**
I believe serialEvent is never called. I tried renaming it to serialEvent1 and serialEvent2 without any effect.
I did a survey of the situation and decided that the best approach is to completely document serialEvent() support for all official boards in a single place, then link to that from the tutorial. This will make it easier/more likely to keep the information updated.
As the first step, I have submitted a PR to fully document the situation on the Arduino Language Reference's serialEvent() page:Fully document serialEvent() support for all Arduino boards by per1234 · Pull Request #800 · arduino/reference-en · GitHub