Is there a way to disable the debugging interface on the FEZ Domino? I’ve jumpered the Mode pin, which switches the debug interface from USB to COM1, but is there a way to make it so I can have USB, COM1 and COM2 available for use?
Sorry I’m not fully grasping what you’re trying to say.
I’m using the USB client as a USB Mass Storage Controller and the way to do that is to move the debug interface from USB client to the COM1 serial port on the FEZ by jumping the Mode pins. Then the USB is free to be used as a mass storage controller since the debug interface isn’t using it anymore.
I need the use of COM1 and COM2, so I’m wondering if there’s a way to turn off the debug interface as a whole, instead of just relocating it to COM1, where I’m unable to use COM1.
I believe that if you set your target in Visual Studio to Emulator or do not run VS at all (because you are not going to debug the device), then tFez will not connect to any debugger and therefore USB and COM ports will be available for other purposes. If you do not connect a debugger, then the Fez won’t try to use any ports for debugging.
NETMF needs an interface, even if you are not debugging, to send out boot messages and other runtime info. Like your system is crashing and you have no idea why…you need the port to check for exceptions.
We could add a fake port to disable all this but with 4 COM ports, this is not extremely important. Those messages become really important at one point, even after you ship product.
I’m using all the AD pins and all the uext pins too. i’ll try a reshuffle.
What about being able to direct debug to a in internal memory stream that works like a fake com port? That way we can re-send it over Cdc, write it to mass storage or put it out on an lcd or ignore it completely.
I’ll try that - but this worked perfectly when I was using COM1 for the RFID reader before. It started happening after moving the RFID to COM2 and debugging on COM1.
Why would COM1 and COM2 even be related in any way? Surely debugging on COM1 cannot have an influence on COM2? The app isn’t hanging because my keypad thread still responds.
One thing I have noticed is that there seems to be some cross-talk. My wires aren’t shielded and the debug traffic seem to introduce “noise” on COM2. What I can’t understand is when there’s lots of traffic on COM1, COM2 suddenly works. When COM1 is quiet, COM2 doesn’t fire events.
Should I perhaps tie COM2 low through a weak pulldown or perhaps high? Is it electrically different to COM1?