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

"Assertion Failed!" #28

Open
jack-bliss opened this issue Apr 16, 2014 · 5 comments
Open

"Assertion Failed!" #28

jack-bliss opened this issue Apr 16, 2014 · 5 comments

Comments

@jack-bliss
Copy link

First of all, thank you so much for providing this completely free! It's great, miles better than the default firmware. I do have one issue, though. Sometimes (namely when i switch on the device and when i set the ADC values), it comes up with a file path to something like settings.cpp and says "assertion failed!" additionally, i can't get it to connect to my PC (which im running on a mac through virtualbox, do you think this is a problem?) to reinstall the firmware. any thoughts?

@beattiea
Copy link

beattiea commented Sep 9, 2014

I'm having this same issue... And it refuses to save settings. Other than this one (rather serious) problem it is an awesome firmware though!

@HorstBaerbel
Copy link

I have this error too. Occurs quite often, and reliably every time I save settings. I have hardware v2.70, System v1.62, DFU V3.11C. Firmware version is 1.0 from Feb 20 2015 17:52:56. The error message reads:
"334
../Source/Core/Settings.cpp
Assertion failed!"
I'm available for further investigation and beta testing if need be...

@HorstBaerbel
Copy link

This is really bad, as you can not even save calibration data... The problem occurs when using a SYS above Sys_1.52. I tried it with SYS_B160, SYS_B161 and SYS_B162. None of those work, so I rolled back to Sys_152.
I took a look at the source and even compiled it successfully, but the official BIOS source and the sources here differ so much, that I got no idea where to even start looking...

@cho45
Copy link

cho45 commented Nov 8, 2016

Same issue. This is produced with just connected to OS X. It means calibration data is lost with just connected to OS X. It is really bad.

@Palmstroemen
Copy link

Same issue here.

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

5 participants