nrf51 and VL53L0X

RE: nrf51 and VL53L0X

mrono — Tue, 05 Feb 2019 14:49:30 GMT

        uint8_t buffer[5]; /* Addr + data */
        buffer[0] = index;
        buffer[1] = data >> 24;
        buffer[1] = data >> 16;
        buffer[1] = data >> 8;
        buffer[1] = data;
        ret = nrf_drv_twi_tx(&m_twi_master, address >> 1, buffer, 2, false);

I was going to say that you can use the official library provided by ST and just implement the I2C communication layer to it. Then I had a quick look at that library, and it does just that.

But the implementation seems to have some issues... Such as the one I pasted above, which is surely wrong.

If you want to use this library, I'd suggest you focus on the file that has the I2C routines in it. Fixing that should be sufficient, as the rest is provided by the chip manufacturer.

RE: nrf51 and VL53L0X

Edvin — Tue, 05 Feb 2019 14:18:33 GMT

Ok, so then VL53L0X_GetMeasurementDataReady() is probably never returning true. What HW are you using? The nRF51 DK?

Try to debug inside VL53L0X_GetMeasurementDataReady() inside vl53l0x_api.c to see if you can figure out why it returns this. This is not our libraries, and I don't have the correct HW to test it, unfortunately. Maybe you can check with the author of the project whether he knows why your project doesn't work.

But regarding the debugger, what HW do you use?

Best regards,

Edvin

RE: nrf51 and VL53L0X

Teecup — Thu, 31 Jan 2019 14:47:42 GMT

Thank you for the response! I am using Keil. I actually narrowed down some things and now I am stuck in the do {} while (!isMeasurementReady()); loop from the github example. Polling the API version and product revision work fine now, but I can' t get any readings since the code is stuck in this loop forever.

I don't know if I understand the debugger. I turned off optimizations and enabled debugging via preprocessor, but when I run the application in debug mode, it breaks right at the beginning of main(), although I can clearly see some Info logs beyond that point.

RE: nrf51 and VL53L0X

Edvin — Thu, 31 Jan 2019 13:18:30 GMT

Hello Simon,

Can you try the following for me:

In your project in SDK12.3.0, go to your preprocessor defines. This is usually found in your project settings. Let me know what IDE (Segger embedded studio, Keil or IAR) you are using, and I can show you how to change them.

1. Add "DEBUG" to your preprocessor defines.

2. Turn off optimization for your project (also done in your project settings). Set it to (-O0).

3. Set a breakpoint on line 76 in app_error.c.

4. Start debugging your project.

Does the application stop at your breakpoint at any point in time? If so, study the .line_num, .error_code and .p_file_name variables, and locate what APP_ERROR_CHECK(err_code) that received an err_code != NRF_SUCCESS (== 0).

Best regards,

Edvin