Skip to content
This repository has been archived by the owner on Apr 28, 2022. It is now read-only.

Does not go into AP mode / No Debug Output #21

Closed
ZeeZeeEff opened this issue May 21, 2017 · 6 comments
Closed

Does not go into AP mode / No Debug Output #21

ZeeZeeEff opened this issue May 21, 2017 · 6 comments
Assignees

Comments

@ZeeZeeEff
Copy link

Hey,

I do have a problem with your software. When I flash the sketch, the LED's start in rainbow mode but there is no debug output in the serial monitor and the esp does not open an AP. What could be wrong?

Arduino IDE: 1.8.2
all other Libraries are on the same version that you've posted

@ZeeZeeEff
Copy link
Author

Okay, the issue can be closed!
I solved it by erasing the flash of the esp via esptool

@ZeeZeeEff
Copy link
Author

I got it to work now, but there is still no Debug output, strange
it is just outputting single blank's

@toblum toblum self-assigned this May 26, 2017
@toblum
Copy link
Owner

toblum commented May 26, 2017

Good to hear that it works now. I see from the Gitter chat that debug also works now after erasing flash.

@toblum toblum closed this as completed May 26, 2017
@dimiepp
Copy link

dimiepp commented Nov 1, 2017

Hi @ZeeZeeEff , have you figured out what to do about the Serial output? I have the same problem - everything works (ap point, connecting to Wifi, uploading the html file and the webinterface) but I don't get sierial Output.

I tried different baud rates too.

when I add this to the setupt loop:
DBG_OUTPUT_PORT.begin(115200); DBG_OUTPUT_PORT.println("115200");
I get this serial output every time I restart: "o⸮�1152�" (so it only prints the "1152" and stops the serial output).
Everything after EEPROM.begin(512); is not printed

I also flashed it with the esptool but then it's just empty and still no serial output.

Thanks,
dimi

@mogyoros
Copy link

@dimiHH
For me commenting out the line in McLightning.ino solved the no serial debug issue.
// pinMode(BUILTIN_LED, OUTPUT);
Cheers,
Tamas

@toblum
Copy link
Owner

toblum commented Dec 31, 2017

Thanks @mogyoros,
yes, that would explain the problem. I wasn't aware of that conflict described here:
esp8266/Arduino#2192

Regards
Tobias

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants