TWI Scanner Example is not Working in Custom Board (NRF52840)

[namitha K M]

Hi,

1. Here I am using the nrf52840 in my customized board, in parallel I have nrf52840 dev board. In My custom Onboard debugger is not available so I am using SWD to load the program from NRF52840 DK board to Custom Board (NRF52840).

2. I am loading TWI Scanner Example program to my custom board, from that nothing is displayed on terminal, But If I am flashing same TWI scanner example to Dev boards its working and its displaying like TWI Scanner Started But in my custom board nothing is displayed. 

3. I have mention I2C pin as P0.06 & P0.07, and also I have mention UART in my custom board as P1.11(TX), P1.12(RX), P1.10(CTS), P0.30(RTS).

My doubt why log is not displaying anything in my custom board. and one more doubt also whether I have to mention custom board UART pins in TWI Scanner Example??

I have raised this questions in my previous thread, there is no reply that's why I posed this thread. Please anyone help me on this. I am waiting for your quick response...

Thanks in advance.

[Susheel Nuguru]

2. I am loading TWI Scanner Example program to my custom board, from that nothing is displayed on terminal, But If I am flashing same TWI scanner example to Dev boards its working and its displaying like TWI Scanner Started But in my custom board nothing is displayed. 

Jansi, 

Please connect the TWI pins to the logic analyzer or similar and see if there are any data TWI data being transmitted/received on these pins.

Please notice the TWI is not used in NRF_LOG. NRF_LOGGER module only uses UART/RTT or Flash as the backend and not TWI. The TWI data that you are transmitting/receiving in your firmware cannot be seen in the terminal, but the NRF_LOG statements that you have in your firmware should be transmitted on the UART pins and using your TTL/FTDI connections, you should be able to redirect them to your computer USB board into a virtual com port. 

1. Please check on your UART pins using a logic analyzer to see if there is any data that is being transmitted on uart pins? If you can see the expected data on the pins using the logic analyzer,
2. then check to see the FTDI connections and then
3. check if you have configured the COM terminal on the computer with correct baudrate and other settings like flow control etc..

If you still have problem seeing your firmware NRF_LOG data on serial terminal then post me the snapshots of

1. Check the backend you are using for the firmware in your custom board. I am assuming you are using uart as backend.
2. Logic logic analyzer to all four uart pins and take a snapshot of Logic analyzer data showing that the NRF_LOG data is being transmitted to the UART pins. 
3. your FTDI connections picture
4. Your com port terminal settings matching the serial backend you use. Like baudrate, stop/parity bit and hardware flow control setting.

This was supposed to be a very simple task to see your serial data of your custom board. Not sure what is wrong without seeing your logic analyzer snapshots.

[namitha K M]

Hi,

Thanks for the reply.

Please notice the TWI is not used in NRF_LOG. NRF_LOGGER module only uses UART/RTT or Flash as the backend and not TWI -->How to to change backend flashing option in firmware. 

I don't have Logic analyzer, can you please tell me alternate way to check the data. 

Thanks in advance.

[namitha K M]

Hi,

I will share some screenshot related to my previous thread questions in below,

1. Check the backend you are using for the firmware in your custom board. I am assuming you are using uart as backend.---> Yes I am using UART as backend like 

Ex:-

#ifndef NRFX_UART_ENABLED
#define NRFX_UART_ENABLED 1
#endif

#ifndef NRF_LOG_BACKEND_UART_ENABLED
#define NRF_LOG_BACKEND_UART_ENABLED 1
#endif

and 

#ifndef NRF_LOG_BACKEND_RTT_ENABLED
#define NRF_LOG_BACKEND_RTT_ENABLED 0
#endif

2. I have checked that TWI pins in oscilloscope, I did not find any data for both SCL pins , SDA pins and also UART pins.

3. In below attachment I will share the FTDI connector connections

and also I will share my main.c and pca10056.h and sdk.config.h

Please help me on this. Thanks in advance.

/**
 * Copyright (c) 2016 - 2018, Nordic Semiconductor ASA
 * 
 * All rights reserved.
 * 
 * Redistribution and use in source and binary forms, with or without modification,
 * are permitted provided that the following conditions are met:
 * 
 * 1. Redistributions of source code must retain the above copyright notice, this
 *    list of conditions and the following disclaimer.
 * 
 * 2. Redistributions in binary form, except as embedded into a Nordic
 *    Semiconductor ASA integrated circuit in a product or a software update for
 *    such product, must reproduce the above copyright notice, this list of
 *    conditions and the following disclaimer in the documentation and/or other
 *    materials provided with the distribution.
 * 
 * 3. Neither the name of Nordic Semiconductor ASA nor the names of its
 *    contributors may be used to endorse or promote products derived from this
 *    software without specific prior written permission.
 * 
 * 4. This software, with or without modification, must only be used with a
 *    Nordic Semiconductor ASA integrated circuit.
 * 
 * 5. Any software provided in binary form under this license must not be reverse
 *    engineered, decompiled, modified and/or disassembled.
 * 
 * THIS SOFTWARE IS PROVIDED BY NORDIC SEMICONDUCTOR ASA "AS IS" AND ANY EXPRESS
 * OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
 * OF MERCHANTABILITY, NONINFRINGEMENT, AND FITNESS FOR A PARTICULAR PURPOSE ARE
 * DISCLAIMED. IN NO EVENT SHALL NORDIC SEMICONDUCTOR ASA OR CONTRIBUTORS BE
 * LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
 * CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE
 * GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
 * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
 * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT
 * OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 * 
 */
#ifndef PCA10056_H
#define PCA10056_H

#ifdef __cplusplus
extern "C" {
#endif

#include "nrf_gpio.h"

// LEDs definitions for PCA10056
#define LEDS_NUMBER    4

#define LED_1          NRF_GPIO_PIN_MAP(0,13)
#define LED_2          NRF_GPIO_PIN_MAP(0,14)
#define LED_3          NRF_GPIO_PIN_MAP(0,15)
#define LED_4          NRF_GPIO_PIN_MAP(0,16)
#define LED_START      LED_1
#define LED_STOP       LED_4

#define LEDS_ACTIVE_STATE 0

#define LEDS_LIST { LED_1, LED_2, LED_3, LED_4 }

#define LEDS_INV_MASK  LEDS_MASK

#define BSP_LED_0      13
#define BSP_LED_1      14
#define BSP_LED_2      15
#define BSP_LED_3      16

#define BUTTONS_NUMBER 4

#define BUTTON_1       11
#define BUTTON_2       12
#define BUTTON_3       24
#define BUTTON_4       25
#define BUTTON_PULL    NRF_GPIO_PIN_PULLUP

#define BUTTONS_ACTIVE_STATE 0

#define BUTTONS_LIST { BUTTON_1, BUTTON_2, BUTTON_3, BUTTON_4 }

#define BSP_BUTTON_0   BUTTON_1
#define BSP_BUTTON_1   BUTTON_2
#define BSP_BUTTON_2   BUTTON_3
#define BSP_BUTTON_3   BUTTON_4

#define RX_PIN_NUMBER   NRF_GPIO_PIN_MAP(1,3)
#define TX_PIN_NUMBER   NRF_GPIO_PIN_MAP(1,2)
#define CTS_PIN_NUMBER  NRF_GPIO_PIN_MAP(0,9)
#define RTS_PIN_NUMBER  NRF_GPIO_PIN_MAP(0,10)
#define HWFC           true

#define BSP_QSPI_SCK_PIN   19
#define BSP_QSPI_CSN_PIN   17
#define BSP_QSPI_IO0_PIN   20
#define BSP_QSPI_IO1_PIN   21
#define BSP_QSPI_IO2_PIN   22
#define BSP_QSPI_IO3_PIN   23


// serialization APPLICATION board - temp. setup for running serialized MEMU tests
#define SER_APP_RX_PIN              NRF_GPIO_PIN_MAP(1,13)    // UART RX pin number.
#define SER_APP_TX_PIN              NRF_GPIO_PIN_MAP(1,14)    // UART TX pin number.
#define SER_APP_CTS_PIN             NRF_GPIO_PIN_MAP(0,2)     // UART Clear To Send pin number.
#define SER_APP_RTS_PIN             NRF_GPIO_PIN_MAP(1,15)    // UART Request To Send pin number.

#define SER_APP_SPIM0_SCK_PIN       NRF_GPIO_PIN_MAP(0,27)     // SPI clock GPIO pin number.
#define SER_APP_SPIM0_MOSI_PIN      NRF_GPIO_PIN_MAP(0,2)      // SPI Master Out Slave In GPIO pin number
#define SER_APP_SPIM0_MISO_PIN      NRF_GPIO_PIN_MAP(0,26)     // SPI Master In Slave Out GPIO pin number
#define SER_APP_SPIM0_SS_PIN        NRF_GPIO_PIN_MAP(1,13)     // SPI Slave Select GPIO pin number
#define SER_APP_SPIM0_RDY_PIN       NRF_GPIO_PIN_MAP(1,15)     // SPI READY GPIO pin number
#define SER_APP_SPIM0_REQ_PIN       NRF_GPIO_PIN_MAP(1,14)     // SPI REQUEST GPIO pin number

// serialization CONNECTIVITY board
#define SER_CON_RX_PIN              NRF_GPIO_PIN_MAP(1,14)    // UART RX pin number.
#define SER_CON_TX_PIN              NRF_GPIO_PIN_MAP(1,13)    // UART TX pin number.
#define SER_CON_CTS_PIN             NRF_GPIO_PIN_MAP(1,15)    // UART Clear To Send pin number. Not used if HWFC is set to false.
#define SER_CON_RTS_PIN             NRF_GPIO_PIN_MAP(0,2)     // UART Request To Send pin number. Not used if HWFC is set to false.


#define SER_CON_SPIS_SCK_PIN        NRF_GPIO_PIN_MAP(0,27)    // SPI SCK signal.
#define SER_CON_SPIS_MOSI_PIN       NRF_GPIO_PIN_MAP(0,2)     // SPI MOSI signal.
#define SER_CON_SPIS_MISO_PIN       NRF_GPIO_PIN_MAP(0,26)    // SPI MISO signal.
#define SER_CON_SPIS_CSN_PIN        NRF_GPIO_PIN_MAP(1,13)    // SPI CSN signal.
#define SER_CON_SPIS_RDY_PIN        NRF_GPIO_PIN_MAP(1,15)    // SPI READY GPIO pin number.
#define SER_CON_SPIS_REQ_PIN        NRF_GPIO_PIN_MAP(1,14)    // SPI REQUEST GPIO pin number.

#define SER_CONN_CHIP_RESET_PIN     NRF_GPIO_PIN_MAP(1,1)    // Pin used to reset connectivity chip

// Arduino board mappings
//#define ARDUINO_SCL_PIN             NRF_GPIO_PIN_MAP(0,6)    // SCL signal pin
//#define ARDUINO_SDA_PIN             NRF_GPIO_PIN_MAP(0,7)   // SDA signal pin
//#define ARDUINO_AREF_PIN            2     // Aref pin

#define TWI_SCL_M  NRF_GPIO_PIN_MAP(0,6)
#define TWI_SDL_M  NRF_GPIO_PIN_MAP(0,7)

#define ARDUINO_13_PIN              NRF_GPIO_PIN_MAP(1, 15)  // Digital pin 13
#define ARDUINO_12_PIN              NRF_GPIO_PIN_MAP(1, 14)  // Digital pin 12
#define ARDUINO_11_PIN              NRF_GPIO_PIN_MAP(1, 13)  // Digital pin 11
#define ARDUINO_10_PIN              NRF_GPIO_PIN_MAP(1, 12)  // Digital pin 10
#define ARDUINO_9_PIN               NRF_GPIO_PIN_MAP(1, 11)  // Digital pin 9
#define ARDUINO_8_PIN               NRF_GPIO_PIN_MAP(1, 10)  // Digital pin 8

#define ARDUINO_7_PIN               NRF_GPIO_PIN_MAP(1, 8) // Digital pin 7
#define ARDUINO_6_PIN               NRF_GPIO_PIN_MAP(1, 7) // Digital pin 6
#define ARDUINO_5_PIN               NRF_GPIO_PIN_MAP(1, 6) // Digital pin 5
#define ARDUINO_4_PIN               NRF_GPIO_PIN_MAP(1, 5) // Digital pin 4
#define ARDUINO_3_PIN               NRF_GPIO_PIN_MAP(1, 4) // Digital pin 3
#define ARDUINO_2_PIN               NRF_GPIO_PIN_MAP(1, 3) // Digital pin 2
#define ARDUINO_1_PIN               NRF_GPIO_PIN_MAP(1, 2) // Digital pin 1
#define ARDUINO_0_PIN               NRF_GPIO_PIN_MAP(1, 1) // Digital pin 0

#define ARDUINO_A0_PIN              3     // Analog channel 0
#define ARDUINO_A1_PIN              4     // Analog channel 1
#define ARDUINO_A2_PIN              28    // Analog channel 2
#define ARDUINO_A3_PIN              29    // Analog channel 3
#define ARDUINO_A4_PIN              30    // Analog channel 4
#define ARDUINO_A5_PIN              31    // Analog channel 5


#ifdef __cplusplus
}
#endif

#endif // PCA10056_H

[Susheel Nuguru]

namitha K M said:

2. I have checked that TWI pins in oscilloscope, I did not find any data for both SCL pins , SDA pins and also UART pins.

You want your UART data (not TWI data) to pass through the FTDI converter and then to your computer's COM terminal. It is the UART lines that you need to connect to the oscilloscope and not the TWI lines. 

If you are not seeing any data on the UART pins then no wonder that you do not see anything on the COM port terminal. You first need to debug why there is no data on the UART pins since it seems like that is the main issue in your case.I do not have your custom board, so I do not know why you do not see any data on URAT pins when checked with your oscilloscope. Your firmware works on DK (which you have tested aswell) So it is something with your custom board. Do you have any HFCLK XTAL on your board+ if so, have you started it?

[namitha K M]

Hi,

Thanks for the reply

You want your UART data (not TWI data) to pass through the FTDI converter and then to your computer's COM terminal. It is the UART lines that you need to connect to the oscilloscope and not the TWI lines------------> Yeah I want to read some ADC data , that ADC having I2C communication, that's why I am using TWI Scanner example, whatever ADC data I am reading, same data only I have to send through UART. This is my task. 

[namitha K M]

Can you please tell me, In  sdk.config.h, whether I have to change anything, to print some data in UART console. please suggest me.