This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Hi everyone,
I have troubles bringing up the DCA1000EVM ethernet capture example using the lua script together with the AWR1843BOOST EVM.
As far as I can tell I have followed all guides. I installed the current mmwave studio 2.01.01.00 and also see the serial devices. I can get as far as the SPI connect but run into timeouts when the script wants to connect to the FPGA. It can not even query the version, when I use the DCA1000 Gui-Util on the side manually to connect to the FPGA.
I run mmwave as recommended as admin and I also disabled WiFi, any company VPN and the Windows (Defender) firewall just to be sure.
Here the failing part fom the lua script.
17:46:24] [RadarAPI]: ar1.CaptureCardConfig_EthInit("192.168.33.30", "192.168.33.180", "c:22:38:4e:5a:c", 4096, 4098) [17:46:24] [RadarAPI]: Sending fpga command to DCA1000 [17:46:24] [RadarAPI]: [17:46:24] Invalid lvdsMode value (0). [error -4016] [17:46:24] [RadarAPI]: Sending fpga_version command to DCA1000 [17:46:34] [RadarAPI]: [17:46:34] [17:46:34] Unable to read FPGA Version. [error -5] [17:46:34] [17:46:34] CaptureCardConfig_EthInit Success [17:46:34] [RadarAPI]: ar1.CaptureCardConfig_Mode(1, 2, 1, 2, 3, 30) [17:46:34] [RadarAPI]: Sending fpga command to DCA1000 [17:46:44] [RadarAPI]: [17:46:44] FPGA Configuration : [17:46:44] Timeout Error! System disconnected
With Wireshark I can see that at least the DVM respons as I see some packets originating from 192.168.33.180 .Everything else seems to be working fine (AWR1843 is in SPI-Mode and SOP0 ON, SOP1, ON, SOP2 OFF) Also I tested powering it from a two supplies (switched DCA1000 to DC_JACK supply) and one supply connected to the radar board only (RADAR 5V IN), but it does not make any difference. I also tried HW_CONFIG instead of SW_CONFIG, but does not make any difference.
Anything that I am missing? Have I interpreted some setting wrong?
Best regards,
Hi,
Were you able to check the DCA1000 FAQ:
[FAQ] DCA1000EVM: DCA1000EVM Debug Resources - Sensors forum - Sensors - TI E2E support forums
Thank you
Cesar
I resolved it already. It seems the network was for some reaseon classified as public and due to lacking rights I could not change that profile. I could not chnage that part of the firewall (company notebook). And when I deactivated the firewall it was only for private networks.
Seems to be able to communicate now.