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

Run fails out of the box? #1

Open
microbuilder opened this issue Jan 2, 2013 · 6 comments
Open

Run fails out of the box? #1

microbuilder opened this issue Jan 2, 2013 · 6 comments

Comments

@microbuilder
Copy link

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.

@pfalcon
Copy link
Owner

pfalcon commented Jan 5, 2013

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.

@microbuilder
Copy link
Author

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.

@greg1985
Copy link

greg1985 commented Apr 7, 2013

Hello,
I'm having the same issue as microbuilder. Does somebody solved this error ? Analysing the source files I have found that propably Bluelab 4.1 was used for compilation by pfalcon. I'm using the same version but I get the same error as microbuilder. I do not have as much knowledge about this stack and free time to find what is causing this. Hope somebody, maybe you microbuilder found how to get this work.
pfalcon is there any chance to get app+stack combined files via email?
Thanks in advance!
Best regards,
Gregory

@pfalcon
Copy link
Owner

pfalcon commented Apr 10, 2013

Sorry, I don't have access to that build environment (and results) right now.

@Denages
Copy link

Denages commented Feb 15, 2014

I have "VM has panicked! error" too. At the same time my own programs (turning led on/off) work.

@Heavy-Horses
Copy link

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.

tiger12506 added a commit to tiger12506/blutunode that referenced this issue Mar 3, 2018
…le BT2.1 Secure Simple Pairing. Also (maybe?) Fixes pfalcon#1
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