Cm Update Tool No Device Found

[Ellington Walford]

I am a newbie and I have an iMx 6 series Quad board and connected the board to my Windows 7 machine. After installing the drivers it successfully shows as new 'HID- compliant device' but while running the MFG tool (v2) it is not detecting my board and shows 'No device connected'.

Please check that the DIP switches are set for "Serial Downloader" and then connect the board via USB to the MfgTool computer. After flashing, change the DIP back out of "Serial Download" mode to boot the board. Please note I am both turning on "Serial Downloader" as well as turning off "Internal Development" for flashing, then reversing to boot.

Secondly, Please note I had to manually cycle the dip switches more than half a dozen times before they properly registered the correct setting. I thought this a fluke until I went to flash the other 8 boards -- all of which had the same problem. Namely, the DIP switches were never washed by FSL, or they sat around too long and developed corrosion -- either way, all 9 of the SABRE-AI boards I've recently setup needed to have the DIP switches cycled repeatedly before working -- this was on CPU1 and CPU2 versions of the cpu module board.

Is it possible I might have somehow bricked my device? I have JTAG access on it as well, though according to the datasheet it's "not for production". Still, is there any other way I can communicate with the IC despite it being unable to communicate via PMBus?

I could not detect it with ROM mode, the UCD90xxx GUI couldn't find it at all. As I said, even after manually pulling it up to 3.3V we still couldn't find it. RESET is not being asserted, and the 3.3V all looks good. I wasn't able to probe BPCAP yet (it's quite inaccessible). It's supposed to be 1.8V right?

So update: I removed the pullups that were on my board, so that the only thing pulling up DATA and CLK is the dongle's internal pullups (which I set to 2.2k). I removed a buffer that was on the line. when the dongle is connected, I'm seeing that the signals are pulled up to around 1.65V, but the supply voltage remains at 3.3V At this point I suspect that the problem is on the sequencer's internal drivers.

I normally would've dismissed this as a one-off freak accident, but as of yesterday I observed the same inability to communicate on another unit of the same PCBA. No modifications were done, it simply stopped working inexplicably. What could damage the PMBus like this?

We figured out that the rail was being pulled lower due to being backpowered by an alternate path via the pullups on our board. I removed the pull-ups and when the dongle is connected, the pull-up voltage now correctly shows as 3.3V. However, I am still unable to communicate with the sequencer, so is it possible that its I2C drivers might've been damaged?

We still haven't resolved the problem, but with the use of the BSDL file I found on another E2E post and a JTAG tool we were able to peek and poke at the pins. We managed to toggle some pins on and off manually, including the PMBUS_DATA signal. However, it looks like SYNC_CLK isn't switching (we tried this on the EVM and we saw it rapidly toggling on the tool). It seems like the chip is either stuck in reset and/or simply not booting.

We could manually toggle the enables to regulators. As I said before, perhaps it's stuck in reset or otherwise simply not booting?

Our workaround for the short term is to script the aforementioned tool to manually turn on our board. However, this is unsustainable as we have seen this part fail on four boards so far, so clearly there is some systemic issue at play here. So, to reiterate, is there anything we can do over JTAG to recover the chip?

Our script isn't accessing the internal register, our script just uses the EXTEST mode to set the pins high/low and subsequently sequence the enables in the intended order. The device can't be detected in ROM mode. Assuming we did have access to the internal register over JTAG, what could we do?

Thank you, we will give this a go. Before we try it, would it be possible to connect the UCD90320U to Code Composer Studio and read/write registers as well as dump the flash/EEPROM? We're using a SEGGER J-Link as our JTAG probe, by the way.

This guide is a collection of issues related to AXIS Camera Station 5 and how to troubleshoot them. We have put the issues into a related topic to make it easier to find what you are looking for; a topic can be for example audio or live view. For every issue there is a solution described.

Change the NAT or security system if a NAT or security system separates the client and the server. Make sure to allow the HTTP port, TCP (Transmission Control Protocol) port, and streaming port specified in AXIS Camera Station service control to pass through the security system or NAT. To view the full port list, see Port list in AXIS Camera Station 5 user manual.

In the server task manager, confirm if the system uses one of the hardware resources more than normal. If the disk shows signs of overuse, add more disks and move several cameras to record to the new disks.

Reduce the amount of data written on the disk (Video settings, ZIP stream, FPS, resolution). Keep in mind the throughput estimated by AXIS Site Designer, see axis.com/support/tools/axis-site-designer.

The trigger period is an interval time between two successive triggers, use this setting to reduce the number of successive recordings. The recording continues if an additional trigger occurs within this interval. If an additional trigger occurs, the trigger period starts over from that point in time.

This section describes login and connection problems that occur when connected to a single server. When logged in to multiple servers the client starts, and you can see the connection status in the status bar. For more information about the connection status, see Connection status in AXIS Camera Station 5 user manual.

If you know the reason, click Repair. If you suspect unauthorized access, investigate the issue before you restore the certificate. Click Advanced to view the certificate details. Possible reasons for removing the certificate:

AXIS Secure Remote Access does not support proxy that requires authentication. A workaround could be to allow cameras (AXIS Companion) and AXIS Camera Station server (AXIS Camera Station) to bypass authentication.

Each time a client or a camera makes an outbound connection through the router, the router will give that connection a random external port which is used for hole punching. It is not possible to predict which port will be used.

cdn.appdynamics.com:443 should be trusted in the firewall. AppDynamics is used to gain insights into our application's performance. AppDynamics is an Application Performance Monitoring (APM). It helps us monitor, analyze, and optimize our applications, allowing us to proactively identify and address any performance bottlenecks or issues.

Note, this only sets debug level logging on the server logs, not on the client logs. If debug level logging is required also on the client, the below steps using the log4net.config file is needed to be performed on the client machine.

If the device fails in some streaming tests but not all of them, the device could still be used in AXIS Camera Station as long as the stream profile setting is using the ones that pass the tests. For example, if H.264 fails the test but M-JPEG passes, simply change the stream profile in AXIS Camera Station from H.264 (the default setting) to M-JPEG in Devices -> Streaming profiles.

Make sure the time on the device is synced with a NTP server or the computer where Axis Camera Station server is installed on. If not, some cameras may reject any connection requests due to replay attack protection. ONVIF device manager can be used to do this.

If the device passes all tests i.e. is fully compatible according to the AXIS Camera Station Device Compatibility Tool but doesn't work in AXIS Camera Station, follow this: What information is required when contacting Axis support about third-party device compatibility in AXIS Camera Station?

If the device passes all tests i.e. is fully compatible according to the AXIS Camera Station Device Compatibility Tool but doesn't work in AXIS Camera Station you should contact Axis support. Please do the following:

Rerun the tests with AXIS Camera Station Device Compatibility Tool. v The tool will collect detailed information needed for troubleshooting including a Wireshare trace. NOTE! No need to generate an extra trace through Wireshare.

The compatibility test report, if available. Please attach the complete *.zip archive when submitting the support question. By default, the archive is located at "C:\Users\xxx\Documents\CompatibilityResult.zip".

If the tests cannot finish successfully and the full compatibility test report is not available, please locate this log file: "C:\ProgramData\Axis Communications\AcsCompatibilityTestTool\Application.log" and attach it when submitting the support question.

If the network AXIS Camera Station server or client use a proxy server to connect to the Internet, you must configure the proxy settings on the server or client before enabling AXIS Secure Remote Access.

Besides this troubleshooting guide and the user manual, you can visit the YouTube channel for AXIS Camera Station There you can find technical support and feature videos. The videos are available on youtube.com.

3a8082e126