I translated this as follows:
!! Recently doing a bcm920736 development, using WICED-Smart-SDK-2.2.0-IDE development package , found the machine down a time or continuously on mains failure , HCI UART port found no data out , suspected blue not up , I wonder if you have not encountered shrimp , what is the reason , thank you.
What development board are you connecting to your PC, TAG3 or WICED Sense?
Have you installed the USB to Serial drivers for either board?
The WICED Smart Quick Start Guide (SDK 2.x and TAG3 Board) has some examples that will help you get the TAG3 board up and running. The WICED Sense Table of Contents contains links to help you get the WICED Sense board up and running.
If a custom board, then there is another path for t-shooting we need to take.
So on a custom board, the HCI UART is not responding to the download process when the part is in programming mode as indicated by the state of the HCI UART Rx line? Have you read through all the threads here on this site on the same subject? Could you formulate a specific question based on some of the advice given in those threads.
the board is not in download process,, the rx line of HCI UART is disconnected. I have read the threads here on this site, but did not find related subject. do you have met this issue beofre or could you list the same subject here.
I'm confused. What does "HCI UART Port not found" mean in your initial post.
The HCI UART is only used for programming.
It has two states, programming and app mode.
At a high level, which mode is determined by the state of the HCI Rx line on reset.
Go here: Re: BCM2073XS Boot Sequence: Can't download to board (device not found) and you will find more detail in my post on July 31. The HCI UART issue on custom boards is a very common issue.
Sorry, Let me explain more.
the device can work after programing with HCI UART. but it need to disconnct RX line to Run into App mode, right? after continuously power on and power off, sometimes the device can not run. check debug trace from HCI UART port, because the Tx line is good, it can send debug trace into UART, so that we could know the App run or not run.
the issue usually happens on powering off devices for a while then power on again or continuously power on and power off, but it is not easy to reproduce. just found in our devolpment several times.
Here are some things to check:
1. Are you using Write-Protect for your NV?
2. Have you looked at any voltage irregularities?
3. Are there any voltage spikes
4. Are your GPIO's working?
we have check some sigals, the WP is high, the voltage of power supplier for SOC is right. but we do not check GPIO, which pin should be check?
and I found a strange things, when the issue happens, if place it for a long time with nothing to do just power off, sometimes it can work after power on next time. any suggestions? thanks.
1. Try to move the chip to another board to see if the problem is following the chip.
2. Is this happening on all boards?
Not only one board. now we are still testing, it is not reproduced everytime. any suggenstions when it happen?