Blocking usb debug of USB Client DP

NETMF & Gadgeteer
1

Hello
I want to use USB Client DP just for powering on my FEZ Raptor. In other word, I want to block USB debugging. Is there anyway to do that?
(I’m assuming there is no need to for update firmware or my code on Raptor in future…)
Thanks

2

@ andre.m - I want no one of users can change the program of raptor through USB.
I don’t know about switching serial debug… What is it? Could you please tell me about it?
Thanks

3

@ Ehsan Ansari - See section 4.3 of the G400 SoM User Manual - which for some reason I can’t find a link to any more or Section 6 in the DataSheet.

[url]https://www.ghielectronics.com/downloads/man/G400S_and_G400D_Datasheet.pdf[/url]

Basically the debugger is using the serial port COM1 to debug and ignores the USB client port.

4

@ Ehsan Ansari -

You can also use class Configuration.DebugInterface if you don’t want to change hardware.
That class is available in 4.3.8.0.

take a look in C:\Program Files (x86)\GHI Electronics\NETMF v4.3 SDK\NETMF Libraries API Reference.chm for detail.

5

Another way to achieve this is to cut the cable.

You only need the 2x power cables and the 1x ground cable coming from the DP module to the mainboard. Take out the USB interface wires, and you’re done.

But lets be honest. All these things assumes the user doesn’t have access to the device to simply reverse whatever action you take - which by definition they do, because you want to protect them (or protect your device from them). It depends how hard you want to make it and how easily reversible you want to make it all

6

Thanks for replies
I think my question was not clear…As I understand you are suggesting me to change the interface from USB to serial (COMn). yes?
How it helps me? Changing interface blocks all data transfer between board and PC?
I want to use something like USB client DP or SP just as power supply to power the board on. I want no data can be transferred between board and PC

7

How about using a charge only usb cable?

[url]http://www.amazon.com/PortaPow-Micro-USB-Cable-Charging/dp/B0088HTYUE[/url]

8

@ Ehsan Ansari - so what communication do you want with the device? What features do you want to leverage and what don’t you want? With just painting part of the picture, you get partly complete answers; if you can state the full problem, what you’re trying to protect, and what you do and don’t want to be able to do, someone may suggest something that actually works for you.

I’ll say it again - anyone with access to the device can pretty much un-engineer anything you do. None of the solutions protect totally from any form of “attack”. The more value there is in the data/system (ie the more reason you have to want to block access) the more likely someone is to want to undo your protections - so what are you willing to spend?

9

@ Ehsan Ansari -

I think all solutions above just give more difficult to attack, if someone really want, then they still can, even re-solder if the lines were cut :D.

1 Like