Error received nack on transmit of address

[BH1750] ERROR: received NACK on transmit of address

Re: [BH1750] ERROR: received NACK on transmit of address

Post

by ajithk » Sat Jul 09, 2022 12:57 pm

IIRC, the BH1750 has 2 possible I2C addresses. Perhaps the ADDR pin has a bad solder and/or is seeing different voltages on the non-working units. One defensive option is to modify the code to try both addresses.

Re: [BH1750] ERROR: received NACK on transmit of address

Post

by chm9871 » Mon Jul 11, 2022 2:33 pm

Re: [BH1750] ERROR: received NACK on transmit of address

Post

by chm9871 » Tue Jul 12, 2022 12:41 pm

Re: [BH1750] ERROR: received NACK on transmit of address

Post

by mikeysklar » Tue Jul 12, 2022 4:29 pm

Re: [BH1750] ERROR: received NACK on transmit of address

Post

by chm9871 » Tue Aug 30, 2022 12:29 pm

Re: [BH1750] ERROR: received NACK on transmit of address

Post

by mikeysklar » Fri Sep 02, 2022 5:57 am

Re: [BH1750] ERROR: received NACK on transmit of address

Post

by adafruit2 » Mon Sep 05, 2022 11:34 am

a GPIO pin just cannot power 4 sensors, it does not have the current capability for so many sensors. maybe you could power one sensor per GPIO (maybe!) otherwise you are going to get flaky behavoir — you need to have a power circuit to enable/disable the power with at least 50-100mA of output capability

Re: [BH1750] ERROR: received NACK on transmit of address

Post

by chm9871 » Mon Sep 05, 2022 5:15 pm

Re: [BH1750] ERROR: received NACK on transmit of address

Post

by adafruit2 » Mon Sep 05, 2022 5:31 pm

as you can tell there isnt a simple way of doing it, its a good idea for a product! some of our current boards have a ‘switchable’ I2C port, like the Feather ESP32 V2 but dont have a SD card so you’d have to wire that instead — bit of a tradeoff but maybe worth it

• Total Posts : 57
• Reward points : 0
• Joined: 2008/11/20 07:11:47
• Location: 0
• Status: offline

Hi,
i’m using PIC16F18323 with MPLAB X IDE V3.60
I send i write command by an Arduino UNO to the PIC, but the PIC responds NACK after the adress byte.
This means that the adress is correct and the communication is going on but it seems also that there is an error.. reading the datasheet it seems there is the buffer full but the SSPOV bit never go up.
I also monitor the arriving of an address byte or a data byte by changing the status of two leds (Arduino sends data every second).

void main(void) {
    // inizializzazione del PIC
    mcu_init();
    // carica le configurazioni iniziali
    load_starting_values();
     while (1) {
        if(SSP1IF) {
            rx_data = SSP1BUF;
            if(D_nA) // Data byte
                OUT1 = !OUT1;
            else
                OUT2 = !OUT2;
            OUT3 = SSPOV;
                        SSP1IF = 0;
            CKP = 1; // Release clock (clock stretch)
        }
    }
}

post edited by microbot.it — 2017/06/27 06:50:03

• Total Posts : 1963
• Reward points : 0
• Joined: 2012/04/01 13:49:27
• Location: Russia, Novorossiysk
• Status: offline

Re: I2C responds NACK every time


2017/06/26 06:41:54

(permalink)

Hi. You need to show full functions code, all initialization and configuration. The code you’ve shown doesn’t disclosure the functions  mcu_init() and load_starting_values() nor shown the chip configuration bits.

• Total Posts : 6043
• Reward points : 0
• Joined: 2015/04/30 10:49:57
• Location: 0
• Status: offline

Re: I2C responds NACK every time


2017/06/26 07:14:16

(permalink)

You need to initialize, start i2c, stop i2c and you need a device address.

 #define I2C_DS1307_RTC          0xd0 //Maxim real time clock
#define I2C_DS3231_RTC          0xd0 //Maxim Extremely Accurate real time clock

 Your code is not complete by a large margin.

• Total Posts : 57
• Reward points : 0
• Joined: 2008/11/20 07:11:47
• Location: 0
• Status: offline

Re: I2C responds NACK every time


2017/06/26 07:56:40

(permalink)

This is the missing code:

#pragma config RSTOSC = HFINT32 // HFINTOSC with 2x PLL (32MHz)
#pragma config FEXTOSC = OFF // External Oscillator not enabled
#pragma config MCLRE = OFF // MCLR/VPP pin function is digital input; MCLR internally disabled
#pragma config WDTE = OFF // WDT disabled
#pragma config PWRTE = ON // PWRT enabled
#pragma config CLKOUTEN = OFF // CLKOUT function is disabled; I/O or oscillator function on OSC2
#pragma config CSWEN = OFF // The NOSC and NDIV bits cannot be changed by user software
#pragma config FCMEN = OFF // Fail-Safe Clock Monitor is disabled
#pragma config LVP = OFF // High-voltage on MCLR/VPP must be used for programming
#pragma config WRT = ALL // 0000h to 07FFh write protected, no addresses may be modified
#pragma config CP = ON // User NVM code protection enabled
#pragma config CPD = ON // Data NVM code protection enabled
#pragma config BOREN = OFF // Brown-out Reset disabled
#pragma config LPBOREN = OFF // Low-Power BOR is disabled
#pragma config BORV = HIGH // Brown-out voltage (Vbor) set to 2.7V
#pragma config STVREN = ON // Stack Overflow or Underflow will cause a Reset
#pragma config DEBUG = OFF // Background debugger disabled
#pragma config PPS1WAY = ON // The PPSLOCK bit can be cleared and set only once; PPS registers remain locked after one clear/set cycle
void load_starting_values(void) {
    OUT1 = 0;
    OUT2 = 0;
    OUT3 = 0;
}
void mcu_init(void) {
     //Internal Oscillator Frequency = 32MHz
 while(!HFOR && !PLLR)
  NOP(); 
  // Set RA0, RA1, RA2, RA3 as Digital Input; Set RA4 as Digital Output; Set A5 as Analog Input
 TRISA0 = 1; // AD2 / PGD 
 ANSA0 = 0; 
 TRISA1 = 1; // AD1 / PGC
 ANSA1 = 0;
 TRISA2 = 1; // AD0 
 ANSA2 = 0; 
// TRISA3 = 1; // AD3 / MCLR
 TRISA4 = 0; // OUT2
 ANSA4 = 0; 
 TRISA5 = 1; // IN1
 ANSA5 = 1; 
   //Set RC2, RC3 as Analog Input; Set RC4, RC5 as Digital Output
 TRISC2 = 1; // IN2
 ANSC2 = 1;
 TRISC3 = 1; // IN3
 ANSC3 = 1;
 TRISC4 = 0; // OUT3 
 ANSC4 = 0;
 TRISC5 = 0; // OUT1
 ANSC5 = 0;
      //ADC Configuration: 
 ADFM = 1; // Format Right justified
 ADCON1bits.ADCS = 3; // ADCRC (dedicated RC oscillator) 1.0-6.0 uS 
 ADCON1bits.ADPREF = 0; // Positive Voltage Reference is VDD 
 ADCON1bits.ADNREF = 0; // Negative Voltage Reference is GND 
 ADCON0bits.CHS = 0x0F; // Analog Channel not connected
    ADACT = 0; // No auto-conversion trigger selected
 ADON = 1; // ADC is enabled
 //I2C Configuration:
 TRISC0 = 1; //SCL 
 ANSC0 = 0;
 TRISC1 = 1; //SDA 
 ANSC1 = 0;
 SEN = 1; // Clock stretching is enabled
 SSPM0 = 0; // I2C Slave mode, 7-bit address
 SSPM1 = 1; // I2C Slave mode, 7-bit address
 SSPM2 = 1; // I2C Slave mode, 7-bit address
 SSPM3 = 0; // I2C Slave mode, 7-bit address
 SSP1ADD = 0x20; // 7-bit I2C Slave address
    SSP1ADDbits.ADD1 = AD0;
    SSP1ADDbits.ADD2 = AD1;
    SSP1ADDbits.ADD3 = AD2;
    SSP1ADDbits.ADD4 = AD3;
 SSPEN = 1; // Enables the serial port and configures the SDA and SCL pins
}

• Total Posts : 57
• Reward points : 0
• Joined: 2008/11/20 07:11:47
• Location: 0
• Status: offline

Re: I2C responds NACK every time


2017/06/26 08:03:53

(permalink)

and this is the arduino code:

#include <Wire.h> // library used with I2C protocol
#define I2C_address 0x1F
int led = 13;
void setup()
{
  Wire.begin();
  pinMode(led, OUTPUT); 
}
void blink_led()
{
  digitalWrite(led, HIGH);
  delay(25);
  digitalWrite(led, LOW);
  delay(25);
}
void loop()
{
  Wire.beginTransmission(I2C_address); 
  Wire.write(0x00);
  Wire.endTransmission();
  blink_led();
  delay(500);
}

• Total Posts : 6043
• Reward points : 0
• Joined: 2015/04/30 10:49:57
• Location: 0
• Status: offline

Re: I2C responds NACK every time


2017/06/26 08:54:05

(permalink)

Still incomplete.  It will never work without the core functions.

 You should write some low level i2c functions like stop, start, restart etc…

• Total Posts : 57
• Reward points : 0
• Joined: 2008/11/20 07:11:47
• Location: 0
• Status: offline

Re: I2C responds NACK every time


2017/06/26 09:03:08

(permalink)

Gort2015
Still incomplete.  It will never work without the core functions.

 You should write some low level i2c functions like stop, start, restart etc…

Why?
i always used this way and it worked fine.
At this level i just need to recognize address call (i will have interrupt flag SSP1IF), read the buffer to clear the BF flag and turn on a led to know if the last byte was an address or a data…
What i making wrong?

• Total Posts : 6043
• Reward points : 0
• Joined: 2015/04/30 10:49:57
• Location: 0
• Status: offline

Re: I2C responds NACK every time


2017/06/26 09:33:05

(permalink)

If you are using i2c then you need core functions not just one single piece of code,
otherwise you will get nack/ack problems.

 You are not starting and stoping.

• Total Posts : 4604
• Reward points : 0
• Joined: 2012/07/01 04:19:50
• Location: Norway
• Status: offline

Re: I2C responds NACK every time


2017/06/26 10:31:17

(permalink)

Hi
The original poster is writing Slave code for the PIC16
He already have Master code running in the Arduino.
Writing functions like «stop, start, restart etc…»  for the slave device is beyond misleading.

 Then:

This means that the adress is correct …

This may not be correct at all.
NACK and No Response is the same thing,
the only sure indication that PIC16 slave respond to the address, is:  if (SSP1IF) {…
bit getting set, and code entering the «if …» block.
For this to happen, the correct address must be entered in SSPADD register, and SSP hardware correctly set up and enabled, and PIC16 running.

 I2C address in SSPADD register shall be left-shifted 7 bit address, aka. 8 bit address.
Meaning, the left 7 bits of SSPADD register are compared to left 7 bits of address byte received from the bus.

 One possible experiment is to clear SSPMSK register:  SSP1MSK = 0;
then slave will respond to any address from the master.

 Regards,
   Mysil

• Total Posts : 9999
• Reward points : 0
• Joined: 2016/06/05 14:55:32
• Location: One step ahead…
• Status: offline

Re: I2C responds NACK every time


2017/06/26 13:24:09

(permalink)

microbot.it
I send i write command by an Arduino UNO to the PIC, but the PIC responds NACK after the adress byte.
This means that the adress is correct and the communication is going on

No it doesn’t!
As Mysil stated, «NAK» means the PIC did NOT respond.
That could be caused by all sorts of problems.
** Wrong address
** SDA and SCAL reversed
** SDA and SCL connected to wrong pins

What is this code doing?
You set the address, then immediately overwrite it with something else

SSP1ADD = 0x20; // 7-bit I2C Slave address
 SSP1ADDbits.ADD1 = AD0;
 SSP1ADDbits.ADD2 = AD1;
 SSP1ADDbits.ADD3 = AD2;
 SSP1ADDbits.ADD4 = AD3;

• Total Posts : 57
• Reward points : 0
• Joined: 2008/11/20 07:11:47
• Location: 0
• Status: offline

Re: I2C responds NACK every time


2017/06/27 00:31:22

(permalink)

Sorry, i wrote not clear enought.

Mysil
…
This may not be correct at all.
NACK and No Response is the same thing,
the only sure indication that PIC16 slave respond to the address, is:  if (SSP1IF) {…
bit getting set, and code entering the «if …» block…

Yes, the PIC enter the IF block and i see OUT2 changing its status via a LED (it is a define to a pin).
What appens is that it never change the OUT1 status, so never receive DATA byte but it receive ADDRESS byte only, so probably it responde with NACK and master stop the communication.
If a switch OUT1 with OUT2 just OUT1 is blinking.. so both pins have right configuration.

qhb
…
What is this code doing?
You set the address, then immediately overwrite it with something else
…

I have setted a default address value and changed it via a four bit dip switch to connect more boards (later).

 About the address, i also used a «i2c scanner» sketch in Arduino and verified that the led attached on OUT2 blinks only on the right address.

• Total Posts : 57
• Reward points : 0
• Joined: 2008/11/20 07:11:47
• Location: 0
• Status: offline

Re: I2C responds NACK every time


2017/06/27 05:13:58

(permalink)

Mysil
…
One possible experiment is to clear SSPMSK register:  SSP1MSK = 0;
then slave will respond to any address from the master.
…

Just done, OUT2 blink for each adress byte (from 0 to 127) but never accepts data byte (OUT1 never blink)

• Total Posts : 6043
• Reward points : 0
• Joined: 2015/04/30 10:49:57
• Location: 0
• Status: offline

Re: I2C responds NACK every time


2017/06/27 06:39:00

(permalink)

I have a function that scans the i2c bus for addresses and either prints to stdout (List is NULL) or to a byte array (List is addr).  No of devices found is returned

 In 16bit asm so you’ll need to convert to C or 8bit asm.

 int scanI2C     (unsigned char *List);  //write to *List, if null write to stdout, return device cnt

.include "xc.inc"
.global _scanI2C
;----------------------------------------------------
.section i2c_data,data
device_text:    .string "device 0x"
found_text:     .string " foundr"
.section i2c_code,code
;----------------------------------------------------
.equ arg_pList,     w0
.equ tmp,           w2
.equ cnt,           w8
.equ id,            w9
.equ plist,        w10
_scanI2C:   ;int scanI2C(unsigned char *List)
    push.d  w8
    push    w10
    mov     arg_pList,plist
    clr     cnt
    mov     #0xfe,id
loop:
    rcall  _startI2C
    ;~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
busy:
    mov     I2CCON,tmp
    and     #0x1f,tmp
    bra     nz,busy
    ;~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    mov     id,I2C1TRN
wait:
    btsc    I2CSTAT,#TRSTAT
    bra     wait
    ;~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    btsc    I2CSTAT,#ACKSTAT
    bra     next
    ;~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    ;found
    inc     cnt,cnt
    cp0     plist
    bra     z,print
    ;~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    ;to list
    mov.b   id,[plist++]
    bra     next
    ;~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
print:
    mov     #device_text,w0
    call    _puts
    mov     #16,tmp
    repeat  #17
    div.u   id,tmp
    push    w1
    ;~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    ;high nibble
    cp      w0,#9
    bra     leu,$+4
    add     #7,w0
    add     #48,w0
    call    _putchar
    ;~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    ;low nibble
    pop     w0
    cp      w0,#9
    bra     leu,$+4
    add     #7,w0
    add     #48,w0
    call    _putchar
    ;~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    mov     #found_text,w0
    call    _puts
    ;~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
next:
    rcall   _stopI2C
    dec2    id,id
    bra     nz,loop
    mov     cnt,w0
    pop     w10
    pop.d   w8
    return
;----------------------------------------------------
.end

• Total Posts : 57
• Reward points : 0
• Joined: 2008/11/20 07:11:47
• Location: 0
• Status: offline

Re: I2C responds NACK every time


2017/06/27 06:46:46

(permalink)
☄ Helpfulby mxhyj 2020/12/15 04:30:54

Ok i solved the problem…
i forgot to assign the PPS registers.
Now it is working adding this code:

    // PPS assignment
    SSP1CLKPPS = 0b10000;
    SSP1DATPPS = 0b10001;
    RC1PPS = 0b11001;
    PPSLOCK = 0x55;
    PPSLOCK = 0xAA;
    PPSLOCKED = 1;

Thank you all

• Total Posts : 3183
• Reward points : 0
• Joined: 2016/12/07 14:20:36
• Location: Wien
• Status: offline

Re: I2C responds NACK every time


2017/06/27 08:08:42

(permalink)

PPS on I2C? Oh, those new PICs…

• Total Posts : 6043
• Reward points : 0
• Joined: 2015/04/30 10:49:57
• Location: 0
• Status: offline

Re: I2C responds NACK every time


2017/06/27 08:40:41

(permalink)

Yes, pps on i2c should have happened on the first pps chips.

• Total Posts : 3183
• Reward points : 0
• Joined: 2016/12/07 14:20:36
• Location: Wien
• Status: offline

Re: I2C responds NACK every time


2017/06/27 08:52:48

(permalink)

I used to know that it was because of open-drain/5V tolerant pins…

• Total Posts : 7
• Reward points : 0
• Joined: 2020/04/10 00:02:08
• Location: 0
• Status: offline

Re: I2C responds NACK every time


2020/12/15 04:33:08

(permalink)

Thank you, I stuck on this problem for days.
Your post solved my problem, appreciate it ^^

• Total Posts : 35931
• Reward points : 0
• Joined: 2003/11/07 12:41:26
• Location: Australia, Melbourne
• Status: offline

Re: I2C responds NACK every time


2020/12/15 12:22:58

(permalink)

mxhyj
Thank you, I stuck on this problem for days.
Your post solved my problem, appreciate it ^^

Which post?
This reply looks suspiciously like a generic post from a spammer to get a foot into a forum.

I also post at: PicForum
To get a useful answer, always state which PIC you are using!

• Total Posts : 15913
• Reward points : 0
• Joined: 2007/05/06 12:03:20
• Location: Harry’s Gray Matter
• Status: offline

Re: I2C responds NACK every time


2020/12/15 12:39:48

(permalink)

Agree. Microchip needs to close newly opened accounts after a period of inactivities.