-
Notifications
You must be signed in to change notification settings - Fork 3.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
disable startup banner #3021
Comments
Why would you want to disable it? Feel free to create a PR. |
The ROM bootloader generates a lot of output at 74,880 baud which looks like 1.2 Kb of crap at 115,200 baud, followed by the ~350 bytes of the extended version message, plus info messages on whether the LFS region is loaded or not. The info message can be a little distracting, but given that the bootloader output is still going to be output to UART1, then suppressing it is only of minor benefit. The main advantage of keeping it is that we created this extended info because this information is really helpful for pinning down bugreps and bug reporters rarely included this before we had it. Perhaps could have a |
Wanted to write similar comment like @TerryE about bootloader output if the case is to keep silent boot because of some parsing on the other end of transmission. But maybe it's for an additional level of security? if so, it could be useful for production devices. Some |
Anyone is welcome to create a PR that makes the banner optional (with the default being |
@marcelstoer But why do you close this issue? |
@marcelstoer, I understand #1010, but still think it's odd to close it. This way no one will fix it. Do not treat it like a your responsibility. Think about it like a public todo list. It's not done, so should be unchecked (opened). |
Marcel, given that @532910 is offering to do the fix, I also think that it is a little premature to close this. @532910, what is your response to my point about there already being 1.2Kb of 'crap' sent to the UART, so what is really so bad about another ~350 bytes? You only see it when debugging anyway. I think that there should be a consensus on need before we consider changing the Lua core code. On some of my apps I connect to my ESPs using the UART instead of WiFi, and with these |
@TerryE, I'm sorry, I missed the note about 1.2Kb of 'crap' ): The real problem that I have is the serial screen. So I need a separate pin to enable it only after boot-up. It will be cool just to send no 'crap' to it. |
What do you mean? What are you using to read the TXD0 and TXD1 pins? As for TXD1, output comes from three sources: The ROM bootloader at 74880 baud
the SDK 3.0 before handover to NodeMCU, again at 74,880 baud
and then the NodeMCU startup at whatever you've configured the frequency to be (by default 115,200) I can't think a way of silencing all of this output short of 3.3V AND gate on GPIO1 and another spare GPIO. |
The Futaba 20x2 dot matrix VFD M202MD07HB is connected to TXD1. TXD0 is used for debug & development. |
Please add support for disable startup banner
Workarounds
comment out
print_version(L);
inapp/lua/lua.c
The text was updated successfully, but these errors were encountered: