-
Notifications
You must be signed in to change notification settings - Fork 1.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
Device restart #1424
Comments
First of all, this is an interesting functionality, feel free to clean up the code and propose a PR, this could be something useful to have in the firmware. The nRF51 does hold the reset pin at each Crazyflie start and has the ability to reset the stm32, so yes, either you have some electronic noise triggering the reset (we have never seen that). So the most likely is that the nRF is somehow reseting your stm. |
I have another question. If we do not consider the impact of nRF51 on the pin reset of stm32, when using CF2.1, the motor sometimes restarts after the self-test sound is connected to cfclient. The "check the reason for the restart" mechanism I wrote will prompt me to "software reset". What is the reason? Or do you have the situation of restarting after connecting to cfclient in normal use? |
Just to clarify, are you saying that after the Crazyflie completes its self-test (with the startup sound), and you connect to cfclient, the entire system restarts due to a software reset? |
Yes, thank you very much |
That is odd! Are you seeing the same behavior with stock firmware? Has this all been on the same drone? Maybe you can copy the console printout for this problem just like you did in the original post, that would help me debug. |
I encountered a restart problem. I added a function to record the restart reason in the source code. Sometimes the software restart or pin restart will occur.
What is the cause? NRF's P0.20 is connected to STM32's NRST pin. Is the cause of the restart controlled by NRF or by cfclient? Thank you very much.
The text was updated successfully, but these errors were encountered: