I was trying to connect my Domino to a Belkin USB/Ethernet hub and all went fine until I tried to debug a simple program
The Belkin device manager reports a device deconnection each time I begin the debugging session. Of course, I canât debug. But the code is still properly written to the board.
The âautomatic reconnectionâ of the Belkin is not fast enough to fool VS2010 (or VS2010 doesnât wait long enough ), so no solution here.
Is there any reason for this behaviour or any mean to change it ? That is : how to not disconnect the board from the USB before sending the program to it ?
Hi
Is there an external power supply for the hub? I had similar problems when I used my hub without the external power supply connected. The USB from your computer might not have enough current to drive the FEZ if you have other devices attached.
(my experience only - I donât know the real underpinning mechanisms)
Code gets deployed; then the device is rebooted. Then the debugger attaches to the running app.
If you deploy code, youâll always get a reboot. Makes no sense not to, to me. And if youâre attaching a debugger, you always want to start program execution âfreshâ so a reboot also makes sense to me.
The probelm as you say is that the reconnection via the hub isnât fast enough. Mmmm, so whereâs the problem - connect the Fez somewhere other than the hub
[quote]If you deploy code, youâll always get a reboot. Makes no sense not to, to me. And if youâre attaching a debugger, you always want to start program execution âfreshâ so a reboot also makes sense to me.
The probelm as you say is that the reconnection via the hub isnât fast enough. Mmmm, so whereâs the problem - connect the Fez somewhere other than the hub [/quote]
Yes, clearly itâs the hub. The device gets disconnected because it gets reset to deploy code.
I donât think itâs only the hub⌠Of course it doesnât reconnect the device fast enough but I was wondering why a deconnection happened, much like when you unplug physically the device.
I can live with that, but I was thinking to use my USB/Ethernet hub to debug each and every board I (will) have across the network. Which now seems impossible
I am I missing something here?
On any NETMF device, the whole system restarts including the USB service to start the debugging session. This is normal.
1.You press F5 in VC#,
2. VC# deploy the new application.
3. The board restarts ( you hear the USB unplug/Plug notification in windows)
4. The debugger attaches to the system and starts the debugging session.
[quote]am I missing something here?
On any NETMF device, the whole system restarts including the USB service to start the debugging session. This is normal.
1.You press F5 in VC#,
2. VC# deploy the new application.
3. The board restarts ( you hear the USB unplug/Plug notification in windows)
4. The debugger attaches to the system and starts the debugging session.[/quote]
Thatâs what I said. Disconnection is a normal procedure for deploying. I still do not get whatâs the error
[quote]Can you post a link to the product page so we can get more info about the device?[/quote] Itâs in my first post here
If this is normal, then thereâs no problem ! I only didnât know it was normal, thatâs all. Iâve never come across this until I use the hub. Also, I have sounds desactivated on my PC, thus not hearing plug/unplug sounds :-[
Josef explanation was helpful to understand whatâs going on. Thanks a lot !
@ Foekie : the âproblemâ (maybe another term should be used now) is that I canât debug over ethernet with the Belkin hub. Nothing more. It could have been useful, but it wonât :â( Thatâs not a vital thing, anyway, so the answers Iâve got here are enough for me.
), so no solution here.
