BHI260 problem uploading firmware via I2C

[RichT]

We have a custom board with the BHI260 interfaced to a Nordic NRF ARM based MCU via I2C however the I2C fails to respond after sending several packets of data.

I can read and write the host registers successfully and these are all left at their default states (I2C operation).

I have followed the startup and nitialisation procedure from the BHI260 programmers manual and the boot register has it's Host Interface Ready bit set.

I  now attempt to upload the Bosch_SHUTTLE_BHI260_BMM150.fw firmware to the device by writing the HOST Interface  "Upload to program ram"  command  to host register 0x00 (the command stream DMA  register) with the length field set as the number of 32 bit words in the firmware followed by NO STOP.  I then attempt to send the firmware 16 bytes at a time with NO STOPs in between until the last packet but only two lots of 16 bytes are received by the device the third is NAK'd for no apparent reason.

Here is an I2C trace captured at the BHI260 pins using a logic analyser, where the first line is my command header followed by lines 1-3 which contain groups of 16 bytes I am sending the last of which is NAK'd preventing me from sending more: 

Start, h50 [ h28 | WR ], h00, h02, h00, h60, h6B,
Restart, h50 [ h28 | WR ], h2B, h66, h00, h00, h00, h00, h5A, h17, h3A, h9E, h7E, hFB, h5C, h68, hD5, hC0,
Restart, h50 [ h28 | WR ], h7C, h27, hF4, h0A, hF4, hD0, h65, h08, h67, h4D, h72, hF4, hA0, h56, hB4, hF4,
Restart, h50 [ h28 | WR ], h07, h64, h7E, h6E, hEF, h83, h00, hDE, h00, h00, h00, h00, h39, h4A, h39, h6B NAK, Stop

This all appears to be correct and the data that is sent matches the hex in the firmware file.

Just in case this is BHI260 processing issue I reduced the I2C clock speed to 100K and I have tried inserting delays between packet sends but this had no effect.

For completeness I have added a scope trace of the I2C data clock, this also appears fine. 

Are there any known issues uploading firmware via the I2C interface? I notice your BYP2  examples only use SPI and not I2C and there do not appear to be any examples that I can find using I2C.

[Vincent]

The I2C interface of BHI260 AB is working as expected,  there is no known issue of I2C interface existing here.  

Please refer to the attached logic analyzer plotter for the same FW download to sensor with I2C interface. 

[RichT]

Please can you provide the software, or a link to the software, that you used to drive the BHI260 I2C to upload the firmware in your trace so that I can compare it to mine

[RichT]

You have provided your trace in a logicdata binary format which I am unable to read as I do not have access to that analyser. Please can you provide your trace in a text format like the one I provided in my original post.

Have you taken a look at my I2C trace to see what I might be doing wrong? The data I am sending in this firmware update is all there, does it look correct to you or not?

To simply reply saying yours works is not particularly helpful in helping me to resolve this issue.

[JArcher]

Hi

@Vincent I have almost exactly the same issue as RichT, I have followed the start-up and initialisation procedure in the programmer’s manual for uploading firmware via I2C. However, I get a NACK condition before the firmware has finished uploading.

Just saying the I2C firmware upload works on your end is not very helpful. I also can’t read that proprietary I2C log file you provided. It would be useful if you could send us some example code for uploading firmware via I2C to BNI260 RAM?