AWR1243 RF Powered-up RF enable failure (Dev mode) processing

Jacktang

AWR1243 RF Powered-up RF enable failure (Dev mode) processing [Copy link]

1. RF Powered-up radio frequency enablement failed (Dev mode)
[error]:

Cause: The firmware file burned into AWR1243 is loaded incorrectly

Solution: Correct firmware program file path:

The DFP installation file also has the firmware version in the following path, which is used to burn the AWR1243 in functional mode. In development mode, use the firmware in the path above. If the wrong firmware is loaded, an error will be reported in the RF Powered-up step.

2. RF Powered-up radio frequency enable failure (Functional mode)
[errror]: [RadarAPI]: ar1.RfEnable()

[RadarAPI]: Status: Failed, Error Type: RESP TIMEOUT

Solution:

(1) The BSS version does not match the ES2.0/3.0 version of the development board (note whether the EVM version and firmware version match).

(2) Three files are required for Uniflash firmware burning: (xwr12xx_xwr14xx_radarss.bin, xwr12xx_masterss.bin, xwr12xx_memswap.bin)

(3) Development board power supply: TSW1400: 5V, 4A or more, AWR1243: 5V, 2.5A or more.

(4) Before SPI control, use NRST reset, mainly to keep IRQ high after reset, so that the radar can start in a better state.

3. RS232 serial port connection failed
[Error]: Connection failed: Calling_ConnectTarget returned 3

Solution:

(1) Ensure that the interface connection is normal: disconnect the USB serial port cables of the EVM and DevPack, and disconnect the power supply; ensure that the pins of the DevPack are fully in contact with the pins of the EVM; ensure that the LVDS interface high-speed cable is correctly connected.

(2) Make sure the two USB serial cables are connected to separate USB ports. If you are using a passive USB hub, this will cause problems. If you are using a USB multi-port hub, it must be an active hub (check the device manager to see if the Devpack and 1243 interfaces are all recognized).

(3) The EVM power supply is preferably 5V/2.5A;