I’m getting this ‘not in an initialized state’ error when I try to debug this project on a Fez Cerbuino Bee: https://cc3100.codeplex.com
According to this, https://www.ghielectronics.com/community/forum/topic?id=9183
it may have to do with a Framework mismatch, however I don’t find any ‘gadgeteer’ reference in the source files so I can’t apply the fix mentioned on that thread.
In the project properties, if I try to set the Target framework to anything other than 4.3, the debugger complains,
“Cannot deploy the base assembly ‘mscorlib’, or any of his satellite assemblies, to device - USB:Gadgeteer twice. Assembly ‘mscorlib’ on the device has version 4.3.1.0, while the program is trying to deploy version 4.2.0.0” Which makes sense since the FEZ Config program show my board to be running 4.3.7.10.
Has anyone tried running this project or suggestions how to fix the debugger issue?
Can you get the firmware check report from Fez Config for your device ?
Can you also try this debug step and when it says rebooting, you manually press the reset on the device and see if that allows it to finish?
Can you also tell us about how you generated the project - did you create your own new project and include the code from the CC3100 project into that, or did you open a CC3100 supplied project?
Thanks, the FEZ Config program show my board to be running 4.3.7.10.
I didn’t notice any change when pressing the reset before/during starting to debug.
I’m using the CC3100 project without any source change, and it compiles fine (MS Community 2013 V12.0.31101.00 Update 4). The only thing I did was to set the Project properties to Framework 4.3 and the debugger to use the USB transport and Cerb-Family (non-commerical use)_Gadgeteer under ‘Device’.
This project looks appears to links with a CC3100 dll… something I didn’t build since the dll was included in the project. Is it possible I would need to build an updated 4.3 version of that dll?
reload the firmware and then try to deploy a simple hello world application.
if this works, then there was something wrong with the software you were trying to debug, and it was crashing or going into a loop, which is stopping the debugge r from attaching.