How to read from sensor with i2c(twi) communication.

RE: How to read from sensor with i2c(twi) communication.

awneil — Fri, 23 Nov 2018 12:09:41 GMT

[quote userid="73638" url="~/f/nordic-q-a/39686/how-to-read-from-sensor-with-i2c-twi-communication/155676"]re-setting the address[/quote]

Please explain what you mean by that!

[quote userid="74848" url="~/f/nordic-q-a/39686/how-to-read-from-sensor-with-i2c-twi-communication/158818"]how to reset the slave address[/quote]

The Slave Address is a property of the slave - so, if it can be "reset", this will be described in the Slave's documentation.

RE: How to read from sensor with i2c(twi) communication.

ps_anu — Fri, 23 Nov 2018 11:58:11 GMT

how to reset the slave address..

RE: How to read from sensor with i2c(twi) communication.

y001 — Fri, 02 Nov 2018 08:04:25 GMT

It worked after re-setting the address.

Thank you

RE: How to read from sensor with i2c(twi) communication.

awneil — Wed, 24 Oct 2018 11:14:05 GMT

[quote userid="14926" url="~/f/nordic-q-a/39686/how-to-read-from-sensor-with-i2c-twi-communication/154256"]you can't expect someone to magically figure out your issue[/quote]

Indeed.

y001 - debugging is a key part of development; ie, it's part of your job.

How To Debug: www.avrfreaks.net/.../2418156

RE: How to read from sensor with i2c(twi) communication.

Jørgen Holmefjord — Wed, 24 Oct 2018 11:06:58 GMT

You should debug on the board connected with the sensor, if not you are not able to see errors from the real application.

The debugger on the nRF52-DK can be connected to external devices through Debug output interface, to flash and debug nRF5x ICs.

It should not be a problem to combine TWI sensor example with FatFS example, but you will have to described and find the issues in your application yourself. We do not have your hardware available, and you can't expect someone to magically figure out your issue only by posting the entire code. Debugging is a great tool to figure out what your issue is.

RE: How to read from sensor with i2c(twi) communication.

y001 — Wed, 24 Oct 2018 08:23:47 GMT

Since I do not have what I see logs on the board, I attempted to try the debgging method of the link destination.

However, since I am using such an nrf52DK,I am not connected with an acceleration sensor etc. while writing a program.

Is there any other solution?

Once warning was resolved, I tried a debugging method that looked like the link destination,

I will only come out.

Should not you use fatfs and twi_sensor together sddenly like other respondent awneil of this question?

RE: How to read from sensor with i2c(twi) communication.

y001 — Wed, 24 Oct 2018 08:01:52 GMT

I do not know to check whether the data is readable as using only twi_sensor.c but do you know it?

RE: How to read from sensor with i2c(twi) communication.

awneil — Tue, 23 Oct 2018 07:57:43 GMT

[quote userid="73638" url="~/f/nordic-q-a/39686/how-to-read-from-sensor-with-i2c-twi-communication/153952"]I tried to check bu writing to SD card with fatfs to judge whether I could read data securely.[/quote]

That's a very cumbersome approach!

RE: How to read from sensor with i2c(twi) communication.

Jørgen Holmefjord — Tue, 23 Oct 2018 07:57:36 GMT

Do you have a UART or RTT interface where you can view logs on your board? If so, try setting NRF_LOG_ENABLED and NRF_LOG_BACKEND_[UART/RTT]_ENABLED to 1, and also make sure NRF_LOG_DEFERRED is set to 0 under NRF_LOG_ENABLED. Then check if there are any errors or useful information on the log output.

If not, try this debugging method and check if there are any error codes reported.

RE: How to read from sensor with i2c(twi) communication.

y001 — Tue, 23 Oct 2018 05:19:55 GMT

The syntax error was fixed!

Which of NRF_LOG should I look at?

RE: How to read from sensor with i2c(twi) communication.

y001 — Tue, 23 Oct 2018 05:06:32 GMT

Thank you for reply!

There was no error code, there was one warning.

../../../main.c(194): warning:    #550-D: parameter "x1" was set but never used
    static void read sensor_data(uint8_t x1)
../../../main.c: 1 warning, 0 errors

NRF_LOG is

Syntax error in Options Block - line 1172:

'E' expected

And I do not know because it has gone out.

Have you added the sdk_config code of twi_sensor's twi part to sdk_config.h in fatfs?

//==========================================================
// <e> NRFX_PRS_ENABLED - nrfx_prs - Peripheral Resource Sharing module
//==========================================================
#ifndef NRFX_PRS_ENABLED
#define NRFX_PRS_ENABLED 1
#endif
// <q> NRFX_PRS_BOX_0_ENABLED  - Enables box 0 in the module.
 

#ifndef NRFX_PRS_BOX_0_ENABLED
#define NRFX_PRS_BOX_0_ENABLED 0
#endif

// <q> NRFX_PRS_BOX_1_ENABLED  - Enables box 1 in the module.
 

#ifndef NRFX_PRS_BOX_1_ENABLED
#define NRFX_PRS_BOX_1_ENABLED 0
#endif

// <q> NRFX_PRS_BOX_2_ENABLED  - Enables box 2 in the module.
 

#ifndef NRFX_PRS_BOX_2_ENABLED
#define NRFX_PRS_BOX_2_ENABLED 0
#endif

// <q> NRFX_PRS_BOX_3_ENABLED  - Enables box 3 in the module.
 

#ifndef NRFX_PRS_BOX_3_ENABLED
#define NRFX_PRS_BOX_3_ENABLED 0
#endif

// <q> NRFX_PRS_BOX_4_ENABLED  - Enables box 4 in the module.
 

#ifndef NRFX_PRS_BOX_4_ENABLED
#define NRFX_PRS_BOX_4_ENABLED 1
#endif

// <e> NRFX_PRS_CONFIG_LOG_ENABLED - Enables logging in the module.
//==========================================================
#ifndef NRFX_PRS_CONFIG_LOG_ENABLED
#define NRFX_PRS_CONFIG_LOG_ENABLED 0
#endif
// <o> NRFX_PRS_CONFIG_LOG_LEVEL  - Default Severity level
 
// <0=> Off 
// <1=> Error 
// <2=> Warning 
// <3=> Info 
// <4=> Debug 

#ifndef NRFX_PRS_CONFIG_LOG_LEVEL
#define NRFX_PRS_CONFIG_LOG_LEVEL 3
#endif

// <o> NRFX_PRS_CONFIG_INFO_COLOR  - ANSI escape code prefix.
 
// <0=> Default 
// <1=> Black 
// <2=> Red 
// <3=> Green 
// <4=> Yellow 
// <5=> Blue 
// <6=> Magenta 
// <7=> Cyan 
// <8=> White 

#ifndef NRFX_PRS_CONFIG_INFO_COLOR
#define NRFX_PRS_CONFIG_INFO_COLOR 0
#endif

// <o> NRFX_PRS_CONFIG_DEBUG_COLOR  - ANSI escape code prefix.
 
// <0=> Default 
// <1=> Black 
// <2=> Red 
// <3=> Green 
// <4=> Yellow 
// <5=> Blue 
// <6=> Magenta 
// <7=> Cyan 
// <8=> White 

#ifndef NRFX_PRS_CONFIG_DEBUG_COLOR
#define NRFX_PRS_CONFIG_DEBUG_COLOR 0
#endif

// </e>

// </e>

// <e> NRFX_TWIM_ENABLED - nrfx_twim - TWIM peripheral driver
//==========================================================
#ifndef NRFX_TWIM_ENABLED
#define NRFX_TWIM_ENABLED 1
#endif
// <q> NRFX_TWIM0_ENABLED  - Enable TWIM0 instance
 

#ifndef NRFX_TWIM0_ENABLED
#define NRFX_TWIM0_ENABLED 0
#endif

// <q> NRFX_TWIM1_ENABLED  - Enable TWIM1 instance
 

#ifndef NRFX_TWIM1_ENABLED
#define NRFX_TWIM1_ENABLED 0
#endif

// <o> NRFX_TWIM_DEFAULT_CONFIG_FREQUENCY  - Frequency
 
// <26738688=> 100k 
// <67108864=> 250k 
// <104857600=> 400k 

#ifndef NRFX_TWIM_DEFAULT_CONFIG_FREQUENCY
#define NRFX_TWIM_DEFAULT_CONFIG_FREQUENCY 26738688
#endif

// <q> NRFX_TWIM_DEFAULT_CONFIG_HOLD_BUS_UNINIT  - Enables bus holding after uninit
 

#ifndef NRFX_TWIM_DEFAULT_CONFIG_HOLD_BUS_UNINIT
#define NRFX_TWIM_DEFAULT_CONFIG_HOLD_BUS_UNINIT 0
#endif

// <o> NRFX_TWIM_DEFAULT_CONFIG_IRQ_PRIORITY  - Interrupt priority
 
// <0=> 0 (highest) 
// <1=> 1 
// <2=> 2 
// <3=> 3 
// <4=> 4 
// <5=> 5 
// <6=> 6 
// <7=> 7 

#ifndef NRFX_TWIM_DEFAULT_CONFIG_IRQ_PRIORITY
#define NRFX_TWIM_DEFAULT_CONFIG_IRQ_PRIORITY 7
#endif

// <e> NRFX_TWIM_CONFIG_LOG_ENABLED - Enables logging in the module.
//==========================================================
#ifndef NRFX_TWIM_CONFIG_LOG_ENABLED
#define NRFX_TWIM_CONFIG_LOG_ENABLED 0
#endif
// <o> NRFX_TWIM_CONFIG_LOG_LEVEL  - Default Severity level
 
// <0=> Off 
// <1=> Error 
// <2=> Warning 
// <3=> Info 
// <4=> Debug 

#ifndef NRFX_TWIM_CONFIG_LOG_LEVEL
#define NRFX_TWIM_CONFIG_LOG_LEVEL 3
#endif

// <o> NRFX_TWIM_CONFIG_INFO_COLOR  - ANSI escape code prefix.
 
// <0=> Default 
// <1=> Black 
// <2=> Red 
// <3=> Green 
// <4=> Yellow 
// <5=> Blue 
// <6=> Magenta 
// <7=> Cyan 
// <8=> White 

#ifndef NRFX_TWIM_CONFIG_INFO_COLOR
#define NRFX_TWIM_CONFIG_INFO_COLOR 0
#endif

// <o> NRFX_TWIM_CONFIG_DEBUG_COLOR  - ANSI escape code prefix.
 
// <0=> Default 
// <1=> Black 
// <2=> Red 
// <3=> Green 
// <4=> Yellow 
// <5=> Blue 
// <6=> Magenta 
// <7=> Cyan 
// <8=> White 

#ifndef NRFX_TWIM_CONFIG_DEBUG_COLOR
#define NRFX_TWIM_CONFIG_DEBUG_COLOR 0
#endif

// </e>

// <q> NRFX_TWIM_NRF52_ANOMALY_109_WORKAROUND_ENABLED  - Enables nRF52 anomaly 109 workaround for TWIM.
 

// <i> The workaround uses interrupts to wake up the CPU by catching
// <i> the start event of zero-frequency transmission, clear the 
// <i> peripheral, set desired frequency, start the peripheral, and
// <i> the proper transmission. See more in the Errata document or
// <i> Anomaly 109 Addendum located at https://infocenter.nordicsemi.com/

#ifndef NRFX_TWIM_NRF52_ANOMALY_109_WORKAROUND_ENABLED
#define NRFX_TWIM_NRF52_ANOMALY_109_WORKAROUND_ENABLED 0
#endif

// </e>

// <e> NRFX_TWI_ENABLED - nrfx_twi - TWI peripheral driver
//==========================================================
#ifndef NRFX_TWI_ENABLED
#define NRFX_TWI_ENABLED 1
#endif
// <q> NRFX_TWI0_ENABLED  - Enable TWI0 instance
 

#ifndef NRFX_TWI0_ENABLED
#define NRFX_TWI0_ENABLED 0
#endif

// <q> NRFX_TWI1_ENABLED  - Enable TWI1 instance
 

#ifndef NRFX_TWI1_ENABLED
#define NRFX_TWI1_ENABLED 0
#endif

// <o> NRFX_TWI_DEFAULT_CONFIG_FREQUENCY  - Frequency
 
// <26738688=> 100k 
// <67108864=> 250k 
// <104857600=> 400k 

#ifndef NRFX_TWI_DEFAULT_CONFIG_FREQUENCY
#define NRFX_TWI_DEFAULT_CONFIG_FREQUENCY 26738688
#endif

// <q> NRFX_TWI_DEFAULT_CONFIG_HOLD_BUS_UNINIT  - Enables bus holding after uninit
 

#ifndef NRFX_TWI_DEFAULT_CONFIG_HOLD_BUS_UNINIT
#define NRFX_TWI_DEFAULT_CONFIG_HOLD_BUS_UNINIT 0
#endif

// <o> NRFX_TWI_DEFAULT_CONFIG_IRQ_PRIORITY  - Interrupt priority
 
// <0=> 0 (highest) 
// <1=> 1 
// <2=> 2 
// <3=> 3 
// <4=> 4 
// <5=> 5 
// <6=> 6 
// <7=> 7 

#ifndef NRFX_TWI_DEFAULT_CONFIG_IRQ_PRIORITY
#define NRFX_TWI_DEFAULT_CONFIG_IRQ_PRIORITY 7
#endif

// <e> TWI_ENABLED - nrf_drv_twi - TWI/TWIM peripheral driver - legacy layer
//==========================================================
#ifndef TWI_ENABLED
#define TWI_ENABLED 1
#endif
// <o> TWI_DEFAULT_CONFIG_FREQUENCY  - Frequency
 
// <26738688=> 100k 
// <67108864=> 250k 
// <104857600=> 400k 

#ifndef TWI_DEFAULT_CONFIG_FREQUENCY
#define TWI_DEFAULT_CONFIG_FREQUENCY 26738688
#endif

// <q> TWI_DEFAULT_CONFIG_CLR_BUS_INIT  - Enables bus clearing procedure during init
 

#ifndef TWI_DEFAULT_CONFIG_CLR_BUS_INIT
#define TWI_DEFAULT_CONFIG_CLR_BUS_INIT 0
#endif

// <q> TWI_DEFAULT_CONFIG_HOLD_BUS_UNINIT  - Enables bus holding after uninit
 

#ifndef TWI_DEFAULT_CONFIG_HOLD_BUS_UNINIT
#define TWI_DEFAULT_CONFIG_HOLD_BUS_UNINIT 0
#endif

// <o> TWI_DEFAULT_CONFIG_IRQ_PRIORITY  - Interrupt priority
 

// <i> Priorities 0,2 (nRF51) and 0,1,4,5 (nRF52) are reserved for SoftDevice
// <0=> 0 (highest) 
// <1=> 1 
// <2=> 2 
// <3=> 3 
// <4=> 4 
// <5=> 5 
// <6=> 6 
// <7=> 7 

#ifndef TWI_DEFAULT_CONFIG_IRQ_PRIORITY
#define TWI_DEFAULT_CONFIG_IRQ_PRIORITY 7
#endif

// <e> TWI0_ENABLED - Enable TWI0 instance
//==========================================================
#ifndef TWI0_ENABLED
#define TWI0_ENABLED 0
#endif
// <q> TWI0_USE_EASY_DMA  - Use EasyDMA (if present)
 

#ifndef TWI0_USE_EASY_DMA
#define TWI0_USE_EASY_DMA 0
#endif

// </e>

// <e> TWI1_ENABLED - Enable TWI1 instance
//==========================================================
#ifndef TWI1_ENABLED
#define TWI1_ENABLED 1
#endif
// <q> TWI1_USE_EASY_DMA  - Use EasyDMA (if present)
 

#ifndef TWI1_USE_EASY_DMA
#define TWI1_USE_EASY_DMA 1
#endif

// </e>

// <q> TWIM_NRF52_ANOMALY_109_WORKAROUND_ENABLED  - Enables nRF52 anomaly 109 workaround for TWIM.

RE: How to read from sensor with i2c(twi) communication.

y001 — Tue, 23 Oct 2018 04:40:31 GMT

Thank you for reply!

I saw the linked program, but it seems almost the same.

I tried to check bu writing to SD card with fatfs to judge whether I could read data securely.

RE: How to read from sensor with i2c(twi) communication.

Jørgen Holmefjord — Mon, 22 Oct 2018 12:56:55 GMT

Do you get any error codes? What is the output from NRF_LOG?

RE: How to read from sensor with i2c(twi) communication.

awneil — Mon, 22 Oct 2018 12:20:49 GMT

[quote userid="73638" url="~/f/nordic-q-a/39686/how-to-read-from-sensor-with-i2c-twi-communication"]how to do twi communication based on fatfs program[/quote]

FatFs is an entirely unrelated thing.

Start by getting the I2C comms working on its own: https://devzone.nordicsemi.com/f/nordic-q-a/39691/nrf52832-with-hdc2080-i2c/153794#153794