In theory, the
device_id = ldc1000_read_byte( &ldc1000, LDC1000_CMD_FREQCTRMSB);
with a jumper should return 0x25...
LDC1000 sensor values
Re: LDC1000 sensor values
I’ll try this as wellAntiMember wrote: ↑30 Nov 2022 17:22In theory, the
device_id = ldc1000_read_byte( &ldc1000, LDC1000_CMD_FREQCTRMSB);
with a jumper should return 0x25...
-
- Posts: 96
- Joined: 09 Apr 2021 20:37
Re: LDC1000 sensor values
Good point !
It's good to give this a try, too. I already recognized that the UART Serial Board is jumpered for 3.3V by default.
I'm not sure if I mentioned this before, but the red wire connection from the serial board to the terminal click 5V is
not ok this way !
But isn't it the traditional way to power the SparkFun MicroMod carrier board through the USBC port?
Then, V_USB is the same as V_USB_2, which should be VIN, which is in turn connected to the +5V pin of the mikroBUS socket.
The debug header is only SWD ( Serial Wire Debug ) and typically doesn't power the board. Actually it takes the voltage on the
VCC ( J9, pin 1 ) and selects the output buffers accordingly. That might be the reason why you see something like 3V everywhere.
Basically this is correct, as the STM32 is a pure 3.3V device, and the debug interface should have the same voltage. But it can't power
your board.
It's good to give this a try, too. I already recognized that the UART Serial Board is jumpered for 3.3V by default.
I'm not sure if I mentioned this before, but the red wire connection from the serial board to the terminal click 5V is
not ok this way !
But isn't it the traditional way to power the SparkFun MicroMod carrier board through the USBC port?
Then, V_USB is the same as V_USB_2, which should be VIN, which is in turn connected to the +5V pin of the mikroBUS socket.
The debug header is only SWD ( Serial Wire Debug ) and typically doesn't power the board. Actually it takes the voltage on the
VCC ( J9, pin 1 ) and selects the output buffers accordingly. That might be the reason why you see something like 3V everywhere.
Basically this is correct, as the STM32 is a pure 3.3V device, and the debug interface should have the same voltage. But it can't power
your board.
Kind regards
Frank
Fusion for STM32 v8, STM32F407ZG@168MHz, 4" TFT capacitive
mikromedia 3, PIC32MZ2048EFH100@200MHz, 3" TFT capacitive
NECTO Studio 3.0.0, mikroC AI for ARM/PIC32, mikroSDK v.2.7.2
Frank
Fusion for STM32 v8, STM32F407ZG@168MHz, 4" TFT capacitive
mikromedia 3, PIC32MZ2048EFH100@200MHz, 3" TFT capacitive
NECTO Studio 3.0.0, mikroC AI for ARM/PIC32, mikroSDK v.2.7.2
-
- Posts: 96
- Joined: 09 Apr 2021 20:37
Re: LDC1000 sensor values
Hi
that something like 0xA5 might be returned.
I'm really sorry that I don't own such a board or the SparkFun MicroMod setup. So, I can only talk about it like a blind about the color.
Are you sure about this? As ldc1000_read_byte adds 0x80 to the address register number, to indicate a read, I would assumeIn theory, the
device_id = ldc1000_read_byte( &ldc1000, LDC1000_CMD_FREQCTRMSB);
with a jumper should return 0x25...
that something like 0xA5 might be returned.
I'm really sorry that I don't own such a board or the SparkFun MicroMod setup. So, I can only talk about it like a blind about the color.
Kind regards
Frank
Fusion for STM32 v8, STM32F407ZG@168MHz, 4" TFT capacitive
mikromedia 3, PIC32MZ2048EFH100@200MHz, 3" TFT capacitive
NECTO Studio 3.0.0, mikroC AI for ARM/PIC32, mikroSDK v.2.7.2
Frank
Fusion for STM32 v8, STM32F407ZG@168MHz, 4" TFT capacitive
mikromedia 3, PIC32MZ2048EFH100@200MHz, 3" TFT capacitive
NECTO Studio 3.0.0, mikroC AI for ARM/PIC32, mikroSDK v.2.7.2
Re: LDC1000 sensor values
I'm not 100% sure what the traditional way to power the board is. I was following the setup on sparkfun's example for the micromod, in it they used the JTAG connection.
But a quick update, we finally have success. The power was the issue. Whenever I use the USB power to the board and read the UART, I'm getting the sensor to measure a conductive surface and it adjusts according to distance.
I appreciate all the help.
But a quick update, we finally have success. The power was the issue. Whenever I use the USB power to the board and read the UART, I'm getting the sensor to measure a conductive surface and it adjusts according to distance.
I appreciate all the help.
-
- Posts: 96
- Joined: 09 Apr 2021 20:37
Re: LDC1000 sensor values
Good news finally!
Thanks for the information. It was interesting to dig into this issue and learn some new system and a new Click Board.
Stay well!
Thanks for the information. It was interesting to dig into this issue and learn some new system and a new Click Board.
Stay well!
Kind regards
Frank
Fusion for STM32 v8, STM32F407ZG@168MHz, 4" TFT capacitive
mikromedia 3, PIC32MZ2048EFH100@200MHz, 3" TFT capacitive
NECTO Studio 3.0.0, mikroC AI for ARM/PIC32, mikroSDK v.2.7.2
Frank
Fusion for STM32 v8, STM32F407ZG@168MHz, 4" TFT capacitive
mikromedia 3, PIC32MZ2048EFH100@200MHz, 3" TFT capacitive
NECTO Studio 3.0.0, mikroC AI for ARM/PIC32, mikroSDK v.2.7.2