Step 7: Advanced troubleshooting
This is the final section of the troubleshooting guide. If you have completed all the previous sections and the problem persists this section contains some niche troubleshooting steps that may help you resolve the issue.
Prerequisites
Use this section if:
The problem persists throughout all previous troubleshooting steps. If you have checked all the sections above and the problem persists, but you are able to access the web interface and the applications.
Step-by-step advanced troubleshooting
The most likely cause is a more specific hardware or software issue. Please check the following in order:
Software and firmware checks
Updating from 1.04 or older OS. If you have updated from 1.04 (or older) to 2.00 OS or a higher version, check GitHub issues #250 and #254.
Nightly builds. Check the nightly builds changelog for any relevant updates.
Known software issues. Check the known software issues in the software section.
Hardware-specific checks
UART TX pin on E2 connector. For Original Gen board models, check if the UART TX pin on the E2 connector is driven high (3V3) before or during the boot sequence. The board will boot normally, but you will not be able to access the web interface or connect through SSH.
Known hardware issues. Check the known hardware issues for Original generation and Gen 2 boards.
System recovery checks
Kernel Panic. A kernel panic occurs when the operating system detects an unrecoverable error — typically caused by a program corrupting or accessing invalid memory, hardware issues, or conflicts between software components. Please reinstall the latest version of the official Red Pitaya OS and check if the problem persists. If it does, please contact us.
Next steps
We hope that you have found this troubleshooting guide helpful and that you were able to resolve the issue. If the problem persists, please contact us with all the relevant information regarding the problem, including the Downloaded system report if possible.