About Sid Price

Sid Price · 2021-11-25

I have a simple ranging project generated by CubeMX using X-Cube-TOF1 v2.0.0. The host is Nucleo-L452.Initialization of the VL53L2CX appears to work without errors, however when the "VL53LX_run_device_test" function runs it fails after the timeout, r...

Sid Price · 2021-11-09

My question says it all. I would like to use X-Cube-TOF1 package with X-Nucleo-53L0A1. I do not see that board mentioned in the list of options.

Sid Price · 2021-10-22

I am working on a design using STM32L433 as a composite USB (CDC and MSC) device using the STM32L4xx HAL and FreeRTOS. I have the device enumerating and I now need to add access to the storage medium (eMMC). The challenge I am facing is that the devi...

Sid Price · 2021-09-08

How can I lock the firmware package version used by my CubeIDE project. I do not want the firmware to be updated when I make changes to the MCU pin usage.

Sid Price · 2021-06-27

I am trying to use STM32CubeIDE to create a project for an STM32F038C6 MCU, the problem is that the generated project does not fit into the 4K SRAM of the MCU, it is some 2500 bytes overflow. Even when I remove the "user" heap, not required and reduc...

Sid Price · 2021-12-10

I think I have found and resolved the issue.The SATEL board was being powered from the Nucleo 5V rail. The Nucleo has 3.3V I/O. When I switched the SATEL board to use the 3.3V rail the sample application appears to work.Sid

Sid Price · 2021-12-04

@Julien NGUYEN More information for you is that if I define VL53LX_LOG_ENABLE the firmware works. There is a flood of data from the sensor sent to the serial port and if I capture that I see that the ranging is working.This suggests there is some ki...

Sid Price · 2021-12-04

@Julien NGUYEN Excuse my delayed response, the forum does not send me a notification when a new post is made. Is there a setting for that?My hookup looks the same as yours.

Sid Price · 2021-11-30

@Julien NGUYEN I am still stuck on this issue, both Nucleo-L452RC and Nucleo-F401RE show the symptom. As I said, it does not appear to be an I2C issue because the device is identified through I2C and other commands as part of the setup work.Sid

Sid Price · 2021-11-27

Hi Julien, I have the separate SATEL PCBs (green).I2C appears to be working correctly the ID of the 53L3CX is read and there are many I2C interactions before the project attempts to run the test code.Sid

User statistics

User Activity

Vl53L3CX and X-CUBE-TOF1 v2.0.0 issue

Is it possible to use the X-Cube-TOF1 package with X-Nucleo-53L0A1?

Using USB HAL for MSC with multiple access to storage

How to lock the firmware package version

How to configure CMSIS-RTOS to fit onto STM32F038 MCU

Re: Vl53L3CX and X-CUBE-TOF1 v2.0.0 issue

Re: Vl53L3CX and X-CUBE-TOF1 v2.0.0 issue

Re: Vl53L3CX and X-CUBE-TOF1 v2.0.0 issue

Re: Vl53L3CX and X-CUBE-TOF1 v2.0.0 issue

Re: Vl53L3CX and X-CUBE-TOF1 v2.0.0 issue