Main Site Documentation

"Attempting to connect to device 'USB:Gadgeteer'" error since high speed SPI code deployed?!?


#1

Hi,
I’ve been doing some development on a cerb40-ii interfacing to an SSD1306 screen. Everything was going fine…
Then I decided to try and see how high I could crank the SPI clock speed to see if I could get a faster refresh rate.

The last speed I set was (I think) 10,000khz. It deployed fine and run.

But since then, I have not been able to deploy anything else to the cerb.
I just get this all the time:

Looking for a device on transport 'USB’
Found device port ‘USB’ with ID ‘51ac45bd-7d7a-4b51-99b6-b901f983e026’ for transport 'Usb’
Starting device deployment…
Attempting to connect to device ‘USB:Gadgeteer’ Iteration 0
Attempting to connect to device ‘USB:Gadgeteer’ Iteration 1
Attempting to connect to device ‘USB:Gadgeteer’ Iteration 2
Attempting to connect to device ‘USB:Gadgeteer’ Iteration 3
Attempting to connect to device ‘USB:Gadgeteer’ Iteration 4
Attempting to connect to device ‘USB:Gadgeteer’ Iteration 5
Attempting to connect to device ‘USB:Gadgeteer’ Iteration 6
Attempting to connect to device ‘USB:Gadgeteer’ Iteration 7
Attempting to connect to device ‘USB:Gadgeteer’ Iteration 8
Attempting to connect to device ‘USB:Gadgeteer’ Iteration 9
Attempting to connect to device ‘USB:Gadgeteer’ Iteration 10
Attempting to connect to device ‘USB:Gadgeteer’ Iteration 11
Attempting to connect to device ‘USB:Gadgeteer’ Iteration 12
Attempting to connect to device ‘USB:Gadgeteer’ Iteration 13
Attempting to connect to device ‘USB:Gadgeteer’ Iteration 14
Attempting to connect to device ‘USB:Gadgeteer’ Iteration 15

I have tried restarting visual, rebooting, etc.

Could they be related?
Is the best idea to go to the Fez Config and blank the device?

(I also don’t have the latest boot loader on the cobra… Fez config won’t let me update it.
And the link on updating the firmware seems broken on the old site, any one know how to do it?)

Thanks a lot!
Guy


#2

Put your device in loader mode then use mfdeploy to erase your application.


#3

Ok. I’ll give that a go.

Does it seem possible the SPI speed could have caused this??


#4

I do not see how but maybe.


#5

Actually this happens to me quite often, and I have to remember not to implement the code in the same thread as the entry point. Putting a thread.sleep 1000 at the start may have helped you out there


#6

Ah ha!
Yes, I took the thread.sleep out to try squeezing out every last drop of speed… :slight_smile:

So do you restore in the same way Gus said with MFDeploy?
I just haven’t done that before. I run it. click erase and then have to restore the bootloader?


#7

I assume Gus, you meant do something like this:

(on the cerb40 I would need to contect the loader pin to the Vcc supply for it to work)


#8

Hi, just got home and tried all of the above and none of that worked…

But I found this, and this did.
https://www.ghielectronics.com/docs/46/fez-cerb-family-developers-guide

using the STMicroelectronics STDFU tool and reapplying the boot loader.

:slight_smile:


#9

You should use the new documentation http://docs.ghielectronics.com/hardware/legacy_products/gadgeteer/fez_cerberus.html


#10

Argh, thanks Gus,
I hadn’t seen any of those pages