Dca1000 reports an error and the SPI port cannot be connected
Article catalog
Dca1000 reports an error and the SPI port cannot be connected. Problem Description: problem cause: solution:
Problem Description:
When using dca1000evm board and mmwave Studio software to measure AWR/IWR board data, SPI cannot be connected
Cause of problem:
The possible causes are problems with the 60 pin HD cable of the dca1000evm, or problems with the SPI pin of the FPGA on the board
resolvent:
- replace the 60 pin HD cable. At present, TI company not only provides additional 60 pin HD cable. Therefore, it is necessary to re purchase the board or find other 60 pin HD connection lines to replace it. At present, it is known that the 60 pin HD connection line of mmwave Devpack can be used with the 60 pin HD connection line of dca1000evm to replace the FPGA chip on the board, or check whether there is faulty soldering and additional connection at the pin (metal wire may be attached to the pin)
Read More:
- The connection pool of SSM project database cannot be connected. The project can run normally and the database cannot be connected
- The echots in Vue reports an error. After obtaining the DOM element, the chart can be displayed. The console still reports an error
- The remote port occupation of Linux startup jar package script reports an error
- Kafka opens JMX port and reports that the error port is occupied
- HBase hangs up immediately after startup. The port reports an error of 500 and hmaster aborted
- When xshell 6 is connected normally for the first time, it will prompt could not connect to ‘127.0.0.1’ (port 61708): connection failed
- The Tomcat connector configured to listen on port 8080 failed to start. The port may already be in u
- Oracle reports an error and lsnrctl listening cannot be started
- Android network request framework okhttputils reports an error (okhttp3 cannot be found)
- A new virtual machine cannot be connected to the network (error fetching interface information device not found),
- [OpenGL · error] visual studio 2019 reports an error. It is an external symbol gladloadglloader that cannot be parsed. This symbol is referenced in the function main
- Hadoop reports an error. Cannot access scala.serializable and python MapReduce reports an error
- HTML method IE8 reports an error, IE8 jQuery Ajax obtains static resources reports an error, typeerror denies access
- Error when accessing Oracle: connected to an idle instance
- When a system is deployed on weblogic12.2.1.3, it reports an error “IllegalStateException zip file closed”. When it is deployed on weblogic12.2.1.2, it does not report an error and can be accessed normally.
- The file server reports an error of 413, and the file uploaded by nginx reports an error of 413 request entity too large
- Random number random reports an error. Illegalargumentexception: bound must be positive
- Lamdba in the studio part reports an error. Observe lamdba reports an error but can run
- Putty encountered an error when logging into alicloud CentOS: dis connected:No supported authentication methods available
- Port 4200 is already in use.Use ‘-port’ to specify a different port error Reasons