LAUNCHXL-CC1352P: CC1352P1: OpenThread temp_sensor example adding external sensor using I2C

Eduardo Viel

Part Number: LAUNCHXL-CC1352P
Other Parts Discussed in Thread: SYSCONFIG

Hi,

I am studying the usage of OpenThread network. I am using as example the temp_sensor example available in the Resource Explorer for CC1352P-2 LaunchPad, but as I am using the LP CC1352P1, I am changing the antenna output power to 5 dBm. The temp_sensor application is connected to another LP running the cli_ftd example. When I run the examples I am able to connect them and everything works as expected.

Then I try to read an external sensor using the I2C interface. The following images show the changes I made in the temp_sensor code:

Add I2C_init() in main.c:

Changed tempsensor.c file to read I2C temperature value:

This is the read_ens210_temp() function:

For some reason when the temp_sensor app runs and joins the network provided by the cli_ftd app it looks like it's crashing after the I2C reading:

I can see that the temperature value changes and then it stops responding, I cannot get CoAP responses from the LP and it doesn't respond anything.

Do you have any suggestions on where there might be an error or something I can look up to find the causes?

Thank you.

over 2 years ago

0 Sid over 2 years ago

TI__Mastermind 20412 points

Hi Eduardo,

Please can you check the status of all the I2C APIs? What is the returned values for them?

Regards,

Sid

0 Eduardo Viel over 2 years ago in reply to Sid

Intellectual 613 points

Hi Sid,

By checking the status of the I2c APIs you mean checking the return value of the I2C_transfer() function?

Regards.

0 Sid over 2 years ago in reply to Eduardo Viel

TI__Mastermind 20412 points

Yes, the return value of I2C_transfer

0 Sid over 2 years ago in reply to Sid

TI__Mastermind 20412 points

Or the status field in the I2C transaction would make more sense.

It has more detailed status.

0 Eduardo Viel over 2 years ago in reply to Sid

Intellectual 613 points

This brings me another question: how can I print these values so I can check if they are correct? I mean, I already tried to use the standard "printf" already on this and other simple projects and when I access the terminal it doesn't print anything.

How can I print these values on my screen?

Thank you!

0 Sid over 2 years ago in reply to Eduardo Viel

TI__Mastermind 20412 points

Hi Eduardo,

You could run it in the debug mode.

You can also use UART2_write APIs to display data on the terminal. Please check UART examples in the SDK for the usage.

dev.ti.com/.../node

UART driver documentation:

https://dev.ti.com/tirex/content/simplelink_cc13xx_cc26xx_sdk_7_10_02_23/docs/drivers/doxygen/html/_u_a_r_t2_8h.html

Regards,
Sid

0 Eduardo Viel over 2 years ago in reply to Sid

Intellectual 613 points

Hi Sid,

Thank you for the orientation.

I am now monitoring the status field after all the I2C transactions:

All the status values are 0 (success status) in all transactions:

Do you have any other recommendation?

Regards,

Eduardo.

0 Sid over 2 years ago in reply to Eduardo Viel

TI__Mastermind 20412 points

Hi Eduardo,

It seems that the I2C transfers are not really crashing. If you have multiple threads in your application, please can you try making the I2C thread least priority?

So that the device also executes other threads
Regards,

Sid

0 Eduardo Viel over 2 years ago in reply to Sid

Intellectual 613 points

Hi Sid,

Looking at the SysConfig file it looks like the I2C driver already has the lowest priority:

Regards,

Eduardo.

0 Sid over 2 years ago in reply to Eduardo Viel

TI__Mastermind 20412 points

Hi Eduardo,

In your main(), I assume you create threads using pthread_create, you assign application level thread priorities there.

Please check the priority of the thread that calls the function that reads the sensor values.

Regards,

Sid

0 Eduardo Viel over 2 years ago in reply to Sid

Intellectual 613 points

Hi Sid,

The TempSensor_taskCreate() is the only thread being created in main:

In the tempsensor.c file:

This thread priority you refer is the priParam.sched_priority?

I appreciate your patience!

Best regards,

Eduardo.

+1 Sid over 2 years ago in reply to Eduardo Viel

TI__Mastermind 20412 points

Hi Eduardo,

For reference, yes that is the priority I was referring to.

But I got some insight from a colleague that I had missed, the issue could be you not closing the i2c peripheral in the read sensor thread, I2C_close(). Please call I2C_close after the I2C_transfer.

Regards,

Sid

0 Eduardo Viel over 2 years ago in reply to Sid

Intellectual 613 points

Hi Sid,

That was definitely the issue. After adding I2C_close() it stops crashing. So every time I want to use I2C I need to open it and then closet it? Does it apply to other peripherals too?

Regards,

Eduardo

Zigbee & Thread

Zigbee & Thread forum

LAUNCHXL-CC1352P: CC1352P1: OpenThread temp_sensor example adding external sensor using I2C