Sensors forum - Recent Threads

IWRL6432AOPEVM: REX (request to Exit)

James Falbo — Fri, 13 Mar 2026 14:53:52 GMT

For a REX (request to exit) door sensor, and using the IWRL6432AoPEVM, what firmware and config files that come with the low power visualizer are recommended? Do you have any other firmware you can recommend as the best starting point? Same with config file, for ones that don't come with the visulizer? Also, do you have any specific config file parameter suggestions for request to exit door sensor? Thanks.

FDC1004EVM: FDC1004 EVM Sampling and Output Rate

Aykut Altuntop — Fri, 13 Mar 2026 14:25:47 GMT

Part Number: FDC1004EVM
Other Parts Discussed in Thread: FDC1004

Hello,

We are using FDC1004 EVM board with Sensing Solution GUI 1.10.0. We have 2 problems.

1) Data streaming does not work unless all 4 channels are enabled for reading(We are only using CIN3, other channels being enabled does not affect us but I think it is affecting the sampling speed

2) This is the main problem. The plotting speed is too slow. As you can see from the screenshot, it is around 7Hz and that is the EVM Output Rate as it is written. We tried selecting "Add sample to graph every x seconds" but it dose not change anything, plotting does not get faster than 7Hz. In configuration page, 400 S/s is selected.

We read the FDC1004 Datasheet and also GUI User guide(It is for an older version I guess but still useful information)

Our main purpose is to get a faster/smoother plot in GUI even 40-50Hz would work.

Thank You

TMAG5253: Highest displacement resolution

Christian de Graffenried — Fri, 13 Mar 2026 14:24:34 GMT

Part Number: TMAG5253

Hello,

I'm looking for a very small Hall sensor with the highest resolution. The Hall sensor TMAG5253 is very interesting regarding its very small outlines but I don't know what would be the best resolution I could get from it. Could you please share some exemples or use cases with this sensor?

Thanks a lot for your support

Regards

Christian de Graffenried

DRV425-Q1: DRV425-Q1 Product Life and Longevity

Nick Adams — Fri, 13 Mar 2026 13:46:27 GMT

Part Number: DRV425-Q1

Hello,

We are working on a critical design that includes TI's DRV425QWRTJRQ1 and our customer requested a technical contact to further discuss requirements that includes but not limited to MTBF and derating specific to our application. Who would be a good contact? Thank you.

Best regards,

Nick Adams

Sr. Development Engineer

AMC6821: I2C Communication Issues?

Alan Xia — Fri, 13 Mar 2026 09:26:32 GMT

Part Number: AMC6821

Hi team,

The customer was debugging I2C communication and discovered that the chip was unresponsive; however, measurements of the chip's pin states indicated that everything was normal.

There was no acknowledgment received for the very first byte transmitted—the address byte. The address was sent exactly as described in the datasheet, and the waveforms also appear to be correct.

IWR1843: Problem with UART-flash on self made iwr1843 PCB

Erwan Barzic — Fri, 13 Mar 2026 07:56:27 GMT

Part Number: IWR1843
Other Parts Discussed in Thread: UNIFLASH

Hello,

Im having a isssue flashing my chip with uniflash and I get these error messages:

[ERROR] Cortex_R4_0: XXXX Received unexpected data!!!XXXX

[ERROR] Cortex_R4_0: Not able to connect to serial port. Recheck COM port selected and/or permissions

I have checked that the COM port and permissions are correct but the UART never gets pulled low when flashing. The SOP also seems to be correct. I am wondering if the reason for my problem is because of the UART pins i have used. I use pin F14 and N5.

Is it ok to use these pins for flashing?

Thank you

DRV5057-Q1: hall sensor design consult

Jerry Liu — Fri, 13 Mar 2026 06:21:02 GMT

Part Number: DRV5057-Q1

Hi, we would like to use a hall sensor to measure the distance between two parts.

Current our space design is shown below.

The design gap between hall sensor and magnet is about 1.65mm.

Goal is to measure 1.65+/-1.5mm (0.15~3.15mm) and the accuracy is expected to be 0.1mm.

My question is DRV5057-Q1 can achieve that? or any other recommendation?

thanks a lot

Jerry

TDC1000-Q1: TDC1000 Short TOF Mode – Measurement Works Initially but Times Out After ~20 Seconds

Lovi Jain — Fri, 13 Mar 2026 04:38:54 GMT

Part Number: TDC1000-Q1

Hi Alicia,

Thank you for your suggestion regarding PGA bypass.

After updating TOF_1 to 0x80, I am now able to receive STOP pulses and I am measuring TOF values around 42–43 ticks, which is close to my expected TOF.

However, I am now facing a new issue where the measurement works correctly initially, but after approximately 20 seconds the device starts timing out and STOP is no longer generated.

My current register configuration is:

SPIWrite(CONFIG_0, 0x45);
SPIWrite(CONFIG_1, 0x41);
SPIWrite(CONFIG_2, 0x00);
SPIWrite(CONFIG_3, 0x03);
SPIWrite(CONFIG_4, 0x1F);
SPIWrite(TOF_1, 0x80);
SPIWrite(TOF_0, 0x00);
SPIWrite(TIMEOUT, 0x29);
SPIWrite(CLOCK_RATE, 0x00);

Could this behavior be related to:

Echo listen window being too short?
SHORT_TOF_BLANK_PERIOD being too long?
PGA gain needing further increase for stable echo detection in air?

Best Regards,
Lovi

AWRL6844EVM: CFAR DPU threshold scale

Ram — Thu, 12 Mar 2026 20:52:49 GMT

Part Number: AWRL6844EVM

Hi TI-Team,

In the Doppler and Range Cfar configuration file, is the threshold in 20*log10 format? That number gets multiplied by 100 and then gets sent to the hwa for cfar. Shouldn't there be the log base change because the range-doppler is in log2 format. Also, shouldn't there be some scaling applied to that? Could you please help us understand. By the way, this is with "MMWAVE_L_SDK_06_00_04_01"

PGA460: BOOSTXL-PGA460: Noise Locator - Solved

Syed Akhter — Thu, 12 Mar 2026 20:09:05 GMT

Part Number: PGA460

In my original post, I was looking for a way to detect the source/direction of ultrasonic noise at a specific frequency using the PGA460 board. This was needed because we have multiple valves and industrial equipment near an ultrasonic flowmeter that interfered with the flowmeter readings.

After field testing I have confirmed that it is possible to point the sensor in various directions and do a burst read at the frequency of interest (in my case this was ~47 khz). There were certain valves in the area that saturated the sensor above 90 dB and were able to add sound insulation prevent interference with the near by ultrasonic flowmeter.

IWR6843AOPEVM: Spectrum Data

Zai Mei Chen — Thu, 12 Mar 2026 19:56:13 GMT

Part Number: IWR6843AOPEVM

Please assist with following spectrum data.

TX Parameters needed (DD1494 Transmitter page block listed)
1. RF curves (-3, -20, -40, -60dB curves). We need at least 55dB of dynamic range, preferably 70dB (block 12a-d)
2. Harmonic levels (2^nd, 3^rd, and other), we need at least 55dB of dynamic range, preferably 70dB (block 21a-c)
3. Waveform parameters, pulse rise time, pulse fall time, pulse compression ratio (assumed 50-125) (block 18c-e)
4. Occupied Bandwidth (99% power bandwidth) (block 12e)

RX Parameters needed (DD1494 Receiver page block)
1. Spurious Rejection level (block 20)
2. Intermodulation rejection level (block 22)
3. Rx, RF selectivity e.g. passband curve (-3, 20, 60dB points) (block 11a-c)

General Information (DD1494 DOD or NTIA page block)
1. Number of units (DOD block 8)
2. Number of units in the same environment (DOD block 9)
3. Estimated cost (per unit or all units?) (NTIA page block 7)
4. POC information (DOD page 12)

AWR1843AOPEVM: CAN-FD Transceiver Integration

Marco Ancona — Thu, 12 Mar 2026 15:39:29 GMT

Part Number: AWR1843AOPEVM
Other Parts Discussed in Thread: AWR1843AOP

Dear TI,

I have AWR1843AOP EVM board. I'd like to send out data on the CAN-FD transceiver. I set the S2.1 switch to ON but no data is output on the CAN transceiver. It looks like the "out_of_the_box_1843_mss" project (which is currently flashed on the AWR1843AOP EVM) doesn't implement the CAN communication. Is there any demo project for the AWR1843AOP EVM which has the CAN communication active (like the "can_integration_example_6843" for the 6843 sensor family) which I can use as starting point for my development? If not can you provide step by step instructions to activate the CAN communication on the AWR1843AOP EVM board?

Marco

TDC1000-Q1: TDC1000 Short TOF mode – STOP pulse not generated after changing TOF window configuration

Lovi Jain — Thu, 12 Mar 2026 12:27:48 GMT

Part Number: TDC1000-Q1
Other Parts Discussed in Thread: TDC1000

Hello,

I am working with the TDC1000 ultrasonic analog front-end in Short TOF mode with an external MCU via SPI. Earlier in the previous thread, I received guidance about configuring the Transmit + Mask + Echo listening window.

Based on the suggestion, I modified the configuration to increase the mask window and adjust the listening period. However, after applying the new configuration, the STOP pulse is not generated anymore.

My setup details are:

CLKIN = 8 MHz
CLOCKIN_DIV = 1
T0 = 0.125 µs
T1 = 1 µs
Expected TOF ≈ 47 µs
Transducer resonant frequency ≈ 700 ±100 kHz
Distance between transducer and reflector ≈ 35 mm

Current register configuration:

SPIWrite(CONFIG_0, 0x45);
SPIWrite(CONFIG_1, 0x41);
SPIWrite(CONFIG_2, 0x00);
SPIWrite(CONFIG_3, 0x03);
SPIWrite(CONFIG_4, 0x1F);

SPIWrite(TOF_1, 0x50);   // 12 dB gain
SPIWrite(TOF_0, 0x00);

SPIWrite(TIMEOUT, 0x29);
SPIWrite(CLOCK_RATE, 0x00);

With this configuration:

The transmit pulse is generated correctly.
However, the STOP pulse is never generated, and the measurement times out.

Previously (with my older configuration), I was able to receive STOP pulses and measured around 22–23 ticks, but after modifying the window settings as suggested, the STOP pulse is no longer generated.

Could you please help verify if my configuration for:

SHORT_TOF_BLANK_PERIOD
TOF_TIMEOUT_CTRL
NUM_TX pulses

is correct for an expected TOF around 47 µs?

Also, is there any other register setting that might prevent the STOP pulse from being generated in Short TOF mode?

Thank you.

Lovi Jain

IWR6843ISK: Azimuth/Elevation Static Heatmap

Marvn Arcangel — Thu, 12 Mar 2026 10:32:08 GMT

Part Number: IWR6843ISK

Hi Experts,

Is it possible to extract the azimuth and elevation data from the IWR6843ISK demo bin? This is possible on the ODS model, but only azimuth/range seems to be available for the IWR6843ISK.

I am aware the ISK model has relatively poor elevation resolution, but I would still like to use it if possible.

Thanks!

Marvin

AWR1843AOPEVM: Debugging AWR1843AOPEVM

Marco Ancona — Thu, 12 Mar 2026 10:26:45 GMT

Part Number: AWR1843AOPEVM
Other Parts Discussed in Thread: UNIFLASH, MMWAVEICBOOST

Dear TI,

I have AWR1843AOPEVM board. I'm able to compile demo code with CCS and flash the .bin demo example with Uniflash to the board. I also would like to debug code. At this point it is not clear to me if I can debug the AWR1843OPEVM board in standalone mode or if MMWAVEICBOOST is needed additionally. I suppose MMWAVEICBOOST is need since AWR1843AOPEVM hasn't XDS110 debug probe on it. Would it be possible to directly debug the AWR1843AOPEVM with an external debug probe ARM cortex compatible like Segger J-link?

Thanks

Marco

TPS38: TPS38

William Lai(CFAE) — Thu, 12 Mar 2026 10:00:53 GMT

Part Number: TPS38

Hi team,

Our customer have the question described below.

We got MPN TPS38A909066DYYRQ1 from custom,

From datasheet, We can match the corresponding code, but Our procurement has confirmed with TI that this MPN didn’t be found.

Please help to clarify it or also provide similar parts.

Thanks.

Best Regards,
William Lai

BOOSTXL-PGA460: Regarding the issues of GUI parameter settings and echo curves for PGA460

yf Gong — Thu, 12 Mar 2026 08:59:08 GMT

Part Number: BOOSTXL-PGA460
Other Parts Discussed in Thread: PGA460

I have just started using BOOSTXL-PGA460 for development. I followed the user manual and used the LP-USB power mode, along with the muRata MA58MF14-7N transducer for short-distance measurement. The GUI settings interface is shown in the figure below.

The time-varying gain and threshold settings are shown in the figure.

The above are the default short-distance preset values provided by the GUI.

The measured echo dump graph is shown in the figure. There are significant problems with the waveform, and the ranging value remains at the maximum value all the time.

I noticed an error in the system diagnosis at the bottom right corner. So I went to the diagnostics page and get system diagnostics. The result is shown in the picture.

I'm not sure whether it's due to a problem with the transducer frequency or voltage, or if it's an issue with my gain and threshold settings that led to the incorrect measurement results. Could you please advise on how to proceed with the adjustments?

TI-MAGNETIC-SENSE-SIMULATOR: Turn off noise

Robin Strack van Schijndel — Thu, 12 Mar 2026 07:44:56 GMT

Part Number: TI-MAGNETIC-SENSE-SIMULATOR
Other Parts Discussed in Thread: TMAG5273

Hi,

Can I turn off the generated noise in the simulator? (im using TMAG5273)

Thank you!

Robin

AWR1843AOP: Request for awr1843aop antenna radiation pattern data

Do-hyun Kim — Thu, 12 Mar 2026 06:33:24 GMT

Part Number: AWR1843AOP

Hello.

I'd like to request the AWR1843AOP antenna radiation pattern graph data (.stp, .isg, .CATPart, .CATProduct).

This is for 3D simulation purposes, to preemptively examine factors that could interfere with radio waves around the chip in the FOV during mechanical design.

Please note that I'm not requesting the gain graphs from the datasheet and EVM User's Guide. I'm requesting data that visualizes the antenna radiation pattern generated by the actual chip.

Request Priority
1. Data (.stp, .isg, .CATPart, .CATProduct)
2. Reference Documents

DRV5055: Is the DRV5055 correct

QING DENG — Thu, 12 Mar 2026 02:57:00 GMT

Part Number: DRV5055

Does the DRV5055 meet the technical requirements in the attached document

LM234: Feedback on the Ideal Current Source that Engineers Demand

Scott Turpin — Wed, 11 Mar 2026 20:37:38 GMT

Part Number: LM234

Hello To Whom It May Concern,

I'm an engineer designing a constant current source and if an engineer who does device under test, load under test, etc. that can give advice on the following questions? We are designing a small constant current source.

What types of devices under test (DUTs) require the most stable current sources?

What current ranges are most difficult to control precisely?

What load impedance ranges cause problems in your current sources?

Do you struggle more with low current (µA–mA) or high current stability?

What current accuracy do you require?

What temperature drift is acceptable?

What ppm stability do your current sources need?

What current noise levels interfere with DUT measurements?

What bandwidth do you care about for noise measurements?

What load regulation do your current sources typically achieve?

At what load resistance range do they fail?

What compliance voltage range do your testers require?

Do you require fast settling current sources?

What is the acceptable settling time after a load change?

How much do you currently pay for precision current sources?

If you could design the perfect current source for DUT testing, what specifications would it have?

We will try to achieve multiple times improvement in lower drift, higher load regulation accuracy, lower noise, and at a lower cost.

Thank you,

Scott Turpin

DCA1000EVM: Possible defective device

Marvn Arcangel — Wed, 11 Mar 2026 16:56:59 GMT

Part Number: DCA1000EVM
Other Parts Discussed in Thread: IWR6843ISK

Hi Experts,

I am troubleshooting a DCA1000EVM that a customer is using. Can you help confirm my conclusion?

Summary of the Issue.

Firs time boot of DCA1000EVM Immediately shows error. Refer to Led status below:

5V_LED - Green (OK)
FPGA_DONE_LED - OFF

DATA_TRANS_PROG_LED1 - Green
SD_DETECT_LED5 - Green
SD_FULL_LED0 - Red
SPARE_LED8 - Green
DDR_FULL_LED7 - Red
FPGA_ERR_LED2 - Red
LVDS_PATH_ERR_LED3 - Red
HEADER_ERR_LED4 - Red
EEPROM_RD_FAIL_LED6 - Red

I love to include a screen shot but the E2E shows error when uploading.

The device manager does not show DCA1000EVM. When Ethernet is connected, the port LEDs flash briefly during power-up and then turn off, and 192.168.33.180 does not respond to ping.

I am leaning to the conclusion that the board is faulty. Is there a way to recover this? Does re-programming the FPGA work?

Regards,

Marvin

PGA900: Understanding Failure Modes of the PGA900

D. Ryan — Wed, 11 Mar 2026 13:55:04 GMT

Part Number: PGA900

We are currently undergoing at certification effort for placing our design into production, and experienced a failure of the PGA900 IC that was not expected. The IC was in a 250F enviroment and failed to operate after about 40 hours of operation (presented with faulted output and up to 7.6mA draw. (3.5mA is nominal) The test continued in this enviroment and the failure progressed to a 0V output and 60mA draw (max current limited by resistance at 10V source).

We were able to diagnose that the VDD input is acting with low resistance (1-2 ohms). It is responding like a fixed resistance across voltages from 0-12V, so it does not seem like the internal regulators are turning on. Access to the IC is difficult, since it is inside of a hard potted assembly and inside a sealed housing.

We are trying to isolate failures, however not enough is known about the IC simulate the failure on a more accessable CCA. We have try several theories, however we were wondering if you are able to provide a list or matrix of known methods which might lead to internal failure of the IC.

In general the IC has shown to be robust, however we are trying to root cause this failure to prevent issues in production.

Do you know of failures which would lead to IC failure and/or excessive current draw?

Thank you,

IWRL6432AOPEVM: Quick Evaluation and Custom Config Don't Work Properly, Visualizer 5.5.4.1 with SDK 5.5.4.2

Pat Broughton — Wed, 11 Mar 2026 13:46:01 GMT

Part Number: IWRL6432AOPEVM

I am using the IWRL6432AOPEVM evaluation board with Visualizer 5.5.4.1 which is the version packaged with my download of the MMWAVE_L_SDK_05_05_04_02. I can flash the device with the "Presence and Motion and Tracking" image using the Visualizer and load the "Low Power Presence Detection" configuration in the Configuration Dashboard, and the device seems to function properly and shows data in the plot windows. However, I am unable to load a custom configuration; the Visualizer becomes non-responsive when trying to do so. Also, I am unable to do the "Quick Evaluation"; when I try this the Visualizer says it is unable to connect.

AWRL6844EVM: [AWRL6844EVM] SPI based streaming of Raw ADC Data

환희 박 — Wed, 11 Mar 2026 12:18:32 GMT

Part Number: AWRL6844EVM
Other Parts Discussed in Thread: AWRL6844

Hello TI Support Team,

I am working on implementing SPI-based ADC data logging on the AWR6844EVM following the guide in the mmWave SDK documentation (mmwave_l_sdk_06_00_05_01/docs/api_guide_xwrL684x/MMWAVE_DEMO.html - "SPI based streaming of Raw ADC Data").
I have successfully configured the software according to the guide, but I am experiencing issues with the GPIO handshake signal and would like clarification on the correct SPI hardware connections. Unfortunately, I cannot attach photos due to our company's security policy.

Hardware Setup and Configuration:
I followed the SDK guide and made the following configurations:
(1) Set ADC_DATA_LOGGING_VIA_SPI macro to 1 in "mmwave_demo.h",
(2) Configured ADC_DATA_BUFF_MAX_SIZE in "mmwave_demo.h" and flashed the firmware,
(3) Changed "lowPowerCfg 1" to "lowPowerCfg 0" to disable low power mode,
(4) Changed "adcLogging 0" to "adcLogging 2" to enable SPI logging,
(5) Used FCCSP to attempt ADC data logging. My configuration uses 256 samples, 48 chirps, and 4 Rx channels, which results in a buffer size smaller than the default maximum.

Hardware Connection Issue:
Since the AWR6844 SDK documentation does not include a specific SPI connection table, I referred to the xWRL6432 SDK's "Connection Table of SPI Interface of xWRL6432 with C232HM-DDHSL-0 Cable" and the AWR6844's PROC182A(01_AWR)_Sch.PDF schematic document to make the cable connections.
However, I am uncertain if my connections are correct.
Could you please provide the exact SPI pin mapping for AWR6844EVM?
Specifically, I need to know which physical pins on the EVM correspond to SPI0_CLK, SPI0_MOSI, SPI0_MISO, SPI0_CS, and GPIO Pin 5.

Software Issue - GPIO Signal Toggle:
I have identified a problem in the GPIO signaling mechanism in dpc.c. The code attempts to signal the FTDI device (FT2232H) using R5F GPIO Pin 5 connected to FTDI ADBUS4 (Bit 4) to indicate data transfer start and completion. The relevant code section is:

[dpc.c]

#if (ADC_DATA_LOGGING_VIA_SPI == 1)
if(gMmwMssMCB.adcLogging.enable == 2)
{
// ... SPI transaction setup ...

GPIO_pinWriteLow(gSPIHostIntrBaseAddrLed, gSPIHostIntrPinNumLed);
// ARM Cortex-R5F → FTDI signal transmission: R5F GPIO Pin 5 LOW → FTDI Bit 4 LOW

transferOK = MCSPI_transfer(gMcspiHandle[CONFIG_MCSPI0], &spiTransaction);
// MCSPI_transfer: Transfer radar data to FTDI via SPI

GPIO_pinWriteHigh(gSPIHostIntrBaseAddrLed, gSPIHostIntrPinNumLed);
// Data transfer complete (toggle): R5F GPIO Pin 5 HIGH → FTDI Bit 4 HIGH

// ...
}
#endif

[mmwave_demo.c]
// Configure the FTDI HOST INTR PIN
gSPIHostIntrBaseAddrLed = (uint32_t) AddrTranslateP_getLocalAddr(SPI_HOST_INTR_BASE_ADDR);
gSPIHostIntrPinNumLed = SPI_HOST_INTR_PIN;

[ti_drivers_config.h (R5F GPIO Pin 5)]
/* GPIO PIN Macros */
#define SPI_HOST_INTR_BASE_ADDR (CSL_APP_GIO_U_BASE)
#define SPI_HOST_INTR_PIN (5U)
#define SPI_HOST_INTR_DIR (GPIO_DIRECTION_OUTPUT)

Current Issues: When R5F executes GPIO_pinWriteLow(), FTDI Bit 4 does not change to LOW

Problem Description:
When the R5F executes GPIO_pinWriteLow() to signal transfer start, the FTDI ADBUS4 (Bit 4) does not change to LOW.
My Python script reads the FTDI GPIO state, and value & 0x10 always returns 0x10 (HIGH), never 0x00 (LOW).
The expected behavior is: Before SPI transfer → FTDI reads 0xFC (Bit 4 = HIGH), During SPI transfer (after GPIO_pinWriteLow) → FTDI reads 0xEC (Bit 4 = LOW), After SPI transfer (after GPIO_pinWriteHigh) → FTDI reads 0xFC (Bit 4 = HIGH).
However, the actual behavior is that FTDI always reads 0xFC (Bit 4 = HIGH), causing my Python script to hang in an infinite loop waiting for the LOW signal.
I have verified using GPIO_pinRead() that GPIO Pin 5 toggles correctly (0 → 1 → 0 → 1) on the R5F side, so the software appears to be functioning correctly, but the signal is not reaching the FTDI device.

Questions:

SPI Connection:

Could you please provide the Connection Table of SPI Interface of AWRL6844 with the C232HM‑DDHSL‑0 cable?
I would like to confirm the exact physical pins for SPI0 (CLK, MOSI, MISO, CS) and the GPIO handshake pin on the AWR6844EVM.
GPIO Issue:

The R5F confirms GPIO Pin 5 toggles correctly (LOW/HIGH) using GPIO_pinRead(), but the FTDI device always reads Bit 4 as HIGH. What could be causing this issue?
ADC Data Acquisition: How can I resolve the GPIO signal toggle issue to successfully acquire ADC data via SPI? Are there any recommended hardware connections or software configurations I should check?

Thank you for your support.