How to Figure Out Why your Demo3 Isn’t Working
Introduction
This document provides things to try when your Demo3 doesn’t work. It is assumed that the reader has working knowledge of Windows, but if you don’t recognize something in most cases a Web search of the term will provide guidance.
It is also assumed that the reader has reviewed “DevSuite Quick-Start Guide”; find it by running DevWareX (just enter “Continue” on the “Startup Choices” dialog), then “Documents”.
Some of the solutions presented here will reference solutions already presented in “DevSuite Quick-Start Guide”.
If you have any questions or comments, please contact john.medalen@onsemi.com.
Just a Little Bit of Background …
A common (and fair) question is “Why don’t you just fix these problems?”. Short answer; we would if we could.
The longer answer is that there are parts of the Demo3 FW and SW we have no ability to debug. Some parts are from the provider of the USB interface chip on the Demo3, and some from the Windows operating system (OS). We have tried our best, and yet the problems persist.
Another thing to keep in mind that not all USB3 ports are alike on a PC. On a desktop, those in front are connected to the motherboard via a cable, and those in back are direct-connect to the motherboard. That means those in back get slightly more power – try those if you’re having speed or connection issues. On a laptop, same sort of thing except it isn’t obvious which are connected via cable and which are direct connect – try them all.
The Issues and Possible Solutions
The following items are presented as the most common types of Demo3 failures, and possible solutions.
The first thing to try in any situation; unplug the USB cable, plug it back in, wait 5 seconds for the Demo3 to boot, and try DevWareX again. If that doesn’t work, try another USB3 port.
It does take 5 seconds for the Demo3 to “boot”, meaning loading all FW and FPGA code. On the back of the Demo3, top-right, is a Green LED. When the USB cable is attached, this LED will go on for 3 seconds, go off for 1 second, and then go back on - when it goes back on the Demo3 is ready.
And without further ado, here are we go.
Demo3 doesn’t appear in Device Manager
Especially if the PC is new, most likely you need to update its USB chipset FW.
Solution; See “Camera not found” section of the “DevSuite Quick-Start Guide” for update info.
Demo 3 appears in Device Manager, but not in DevWareX
We’re still trying to figure that one out; we suspect it is due to SW driver we have no ability to debug.
Solution; Unplug and plug back in the USB cable.
DevWareX warns that you’re attached to a USB2 port
Solution; most likely you need to update the USB chipset FW. Or maybe you are attached to a USB2 port.
Demo3 Enumerates as Demo2
This will be a warning from DevWareX on startup. Happens on newer PCs with USB3.1.
Solution; get a new Demo3 – HW revision 7.
Demo3 Streams for awhile, then stops
This is usually caused by a less than optimal USB3 port, due to either down-revision USB chipset FW or slightly less power.
Solutions
Update the USB chipset FW, if you haven’t already.
Try another USB3 port, to possibly increase power.
Get a powered USB3 hub.
If an ISP, apply dedicated 5v power supply to headboard.
Apply FPGA version 43; run “HardwareUpdate Tool” and select “Current FPGA code”, on the next dialog select “Let me choose a new file”. Note that future runs of DevWareX will produce a warning about down-revision FPGA – just select OK.
Try another PC/Laptop. Not joking – some PCs just don’t have the power.
Reset the Demo3 FPGA. This usually only fixes the problem temporarily, but sometimes will cause the Demo3 to run continuously.
a. Run DevWareX, open the Register Dialog, and from “Page:” select “Demo3”.
b. At address 0x0000 “Control Reg 1”, expand to show bitfields.
c. For bitfield 0x0001 “0:Reset”, set and then clear that bit.
AP parts have Sensor Discovery issues
This is just a wacky one; an AP plus sensor will work on some laptops/desktops but not others in the sense that “do_sensor_discovery” fails within the Python console.
Solution; could be related to board connections, so use screws to securely connect the sensor board to the AP baseboard.
0 Comments