Skip to content
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

Flipper crashes #1

Closed
yesterday4 opened this issue Feb 5, 2023 · 9 comments
Closed

Flipper crashes #1

yesterday4 opened this issue Feb 5, 2023 · 9 comments

Comments

@yesterday4
Copy link

The flipper crashes, sometimes when measuring, sometimes just after using the "run" function. I don't know if that's important but it crashed many times in a row when measuring 90hz at 1ms. Using it on the unleashed firmware. It is possible to use it, sometimes it doesn't crash for sometime. After rebooting, flipper shows: "MPU fault, possibly stack overflow". Anyway, thank you for making this cool application.

@anfractuosity
Copy link
Owner

Thanks, I just noticed that after I updated my flipper zero today, I'm not sure if it's something that I've changed in the code here today, or if something has changed in the firmware.

Am looking into it further now.

@yesterday4
Copy link
Author

Thank you.

@anfractuosity
Copy link
Owner

Are you able to try a new .fap executable?

scope.zip

I've been running for around ~10mins, switching between voltage/frequency mode.

I'm just going to push the changes I made now too, if you're able to compile this repo yourself.

@yesterday4
Copy link
Author

yesterday4 commented Feb 5, 2023

I'm going to try the new .fap executable right now. I didn't really understand what you said in your last sentence :). I'm trying to learn how to compile applications for flipper.

@yesterday4
Copy link
Author

yesterday4 commented Feb 5, 2023

The new .fap works great. The application never crashes now. Thank you for fixing the issue so quickly. Only the 0.1s and 1s time scales don't really work for me. They either show nothing at all or just one frame of a distorted wave.

@anfractuosity
Copy link
Owner

Cool, thanks for reporting back.

Regarding the 1s period, it means the analogue to digital converter takes a sample every 1 seconds in this application.

The buffer size is 128 samples though and currently you only see a change in the output when that is full, so after 128 seconds.

I'll investigate if I can make it so you don't need to wait for the whole buffer to be filled, before the display is updated.

@anfractuosity
Copy link
Owner

I've created a new issue regarding improving the displaying of waveforms (see #2)

Would it be ok to close this issue now?

@yesterday4
Copy link
Author

Understood. Yes, thank you.

@anfractuosity
Copy link
Owner

Thanks again for reporting. Feel free to create issues for feature requests/other improvements.

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

No branches or pull requests

2 participants