Do you use names or IP addresses for the server name?
I think that error 53 has something to do with name resolution, I had similar problems a long time ago.
Maybe you can use some tool like Wireshark for debugging.
Posts by fs-support_DB
-
-
You can use standard USB hub chip. We use Microchip (former SMSC) if we need a hub.
-
You can use any protection device which is suited for USB2.0.
For USB2.0 you should use a device with as little capacictance as possible (usually under 1pF). -
-
Since you have the debug output enabled, NDCUCFG can't open the COM port. This is normal.
You can disable the debug output with 'O' in EBoot. -
DCUTerm works on Windows 7 64bit, I use it every day. Do you have a real serial port or a USB->Serial converter? Some converters are too slow to get the 's' recognized, or the repeat rate of the keyboard is too slow
You can also use Tera Term for the download (File->Send File) -
Please remove all the resistors and diodes connected to the USB lines.
USB lines need to be routed according to the USB routing guidlines (differential, 90R impedance, no stubs, etc.).
All protection diodes must be suited for USB2.0 (low capacitance). -
On our new website we changed the address for the bugtracker.
I have corrected the link in my previous post. -
It seems that there is no bootloader installed. Please send the board back for repair with RMA.
-
In version 12 of NBoot the debug port has changed, please try the other serial ports.
-
Did you install EBoot or NBoot? Which version was installed (filename)?
-
There are no ESD protection diodes on the NetDCU.
The ESD protection must be close to the USB connector on the base board. -
the NetDCUA5 analog-in is compatible with the NetDCU8 and NetDCU10 and there the range always was 0-3.3V.
-
How is USB connected to the NetDCU? D+ and D- must be directly connected to the pins on the NetDCU, only EMC and ESD components qualified for USB2.0 are allowed. 5V from USB must be connected to pin 25 on the NetDCU. PCB must be routed according to the “High Speed USB Platform Design Guidelines“.
-
What base board do you use for the download? Is it the our startinterface?
If you designed the base board then is it USB2.0 compatible?
Does USB device work (device recognized by Windows)?
Is VBUS from the USB device connector connected to the PicoCOM? -
NetDCU14 mounting holes are not connected.
What EMC issues do you have?
Do you use the DigitalRGB display interface? You can set the driver strength in the display driver with
where val is 0 (low) to 3 (high).
This reduces the peaks from the display frequency and multiples. -
Please see
http://tracker.fs-net.de/chang…w.php?project=NetDCU14_HW
for the HW changelog. -
The maximum current for the USB ports is 500mA
-
Which pins of J3 do you use?
If you use a NetDCU8 without contrast voltage -Vee, +Vee and Vadj (pins 26, 27, 29) have no function, only Veek (pin 18) outputs 0-3.3V.
On NetDCU8 with contrast voltage pins 26, 27 and 29 can carry up to +-30V and the Veek signal is used to adjust these voltages.
So if you use Veek for your backlight there is some influence to this signal from the voltage regulator. -
Which reset generator do you use? Is it TLC7733 or TL7733? You must use TLC7733.
There was an error in early SKIT schematics where the reset generator was labeled TL7733.
On SKIT hardware there was always used TLC7733.
