-
Notifications
You must be signed in to change notification settings - Fork 29
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
Run fails out of the box? #1
Comments
No, I never faced such error. As you can see, it's system error happening in system files. One suggestion I may have is to try standard BlueLab examples first and see if they work ok for you. |
I have the standard examples working as well as some custom firmware I wrote for a UART pass-through,but I'll dig into this a bit more this weekend since I'm interested in getting back to these modules. Which version of BlueLab are you using (the latest is 4.1.2), since I assumed it might be a conflict between different version of the SDK/API, etc. |
Hello, |
Sorry, I don't have access to that build environment (and results) right now. |
I have "VM has panicked! error" too. At the same time my own programs (turning led on/off) work. |
I resolved this issue by deleting the persistent storage data at "User configuration data 42" trough 49 witch stores the data for the paired device list. it appears the firmware that shipped on my hc-05 used a different format than the firmware that is deployed with Bluelab 4.1. |
…le BT2.1 Secure Simple Pairing. Also (maybe?) Fixes pfalcon#1
I was trying this project out with the CSR tools on a BC417-based module, but the code as is doesn't seem to run out of the box (opening the project file directly in BlueLab 4.1.2), and it panics:
VM has panicked! Reason:
Application panic (Context: 0x0)
VM has panicked! Reason:
Application panic (Context: 0x0)
It gets hung up in common.c at 'uint8_t connectionConvertLinkKeyType_t(cl_sm_link_key_type link_key_type)' and throws the following error message:
Unrecognised link key type 4096
I'll dig into it since I might be missing something obvious (I haven't used the toolset in a while), but I was curious if this is something you can reproduce yourself just opening, compiling and then running the project with the debugger (USB-SPI bridge)? It does compile fine, of course.
Update: Any chance you could let me know what version of the toolset, etc., you used developing this? Perhaps it's related to different versions of the tools or underlying libraries.
The text was updated successfully, but these errors were encountered: