Custom board using BT832 and BT832X ...power drain issue.

[pbecchi]

I am new to Nrf52832.......I have started development of a custom board based on Bt832 and BT832X.

I have built 2 proto boards one with BT832F and the other with BT832X except that the HW is identical.

I have I prepared a code using AdafruitGLX Nfr Arduino libraries .This code is basically a BLE uart server , with a certain command will activate some Gpio port. 

The code works without any problem on Bt832X  and give an acceptable power drain of

1mA during advertising and

100uA during main loop.

Now I have tried the BT832 and I have discovered that same code works only if I add an external 32kHz oscillator.This is because the low freq. 9scillator is only present on Bt832X! It should not be possible to run the code on the RC oscillator? I haven't be able to do it!

But after having added a 32768 Cristal and 2 12pF capacitors I have run the same code on BT832F .......but with following power drain figures

7mA during advertising

3mA during loop if not connected

6mA during loop if connected.

I would like to understand what is going on!! Can anybody tell me?

[MartinBL]

1. It should not be possible to run the code on the RC oscillator? 
   Yes, it is possible. How you do it depends on what SDK you are using?
2. Do you have any tools to measure and plot current over time? Average currents aren't very meaningful. 7 mA could e.g. be the CPU running constantly or the radio going haywire. If we could see a plot of the current over time we would probably be able to guess which one it is. 
3. Do you know whether both the BT832X and F module are using the DCDC regulator? After skimming through the datasheets it seems like the BT832F does have the necessary components to use DCDC, while the BT832X doesn't. Do you somehow deal with this in your code?
4. Have you tried to run an example from the SDK just to compare the currents? If you still get high currents, then it could be a HW issue. Did you solder on the crystal? Could there be any accidental solder bridges drawing currents?
5. Are you running the exact same .hex-file on both modules?

[pbecchi]

Hi Martin, thanks for your reply.

i did some additional test as i describe  answering your question:

1. adafruit libraries use 11.0.0 SKD.

2.i had the power profiler kit in order since 2 weeks....waiting for restock......i will order it from elsewhere!

3.As far as i know, only BT832X has an internal DCDC converter.... I have tested his function in my code and got an important power saving.

4.I have tried several examples on BT832F BT832X and nRF52 DK. The only board that give always low uA is ddevkit. On my laast test I have assembled a new BT832X and this time got same high power drain as for BT832. I doubt it could be due to a combination of an HW and SW problem. Some results is described at this link:https://github.com/adafruit/Adafruit_nRF52_Arduino/issues/165. Fanstell modules are LGA type and since I have solder those myself , I am afraid there could be some short on GPIO locate on the hidden pads that i cannot reach and check. Neverless when I put a Serial.begin statement all strange behaviour is gone.........

5.I always upload identical .hex files, but i doubt is some chip could be on debug mode....how to check?

[MartinBL]

Hi,

Did you get your PPK yet? I think a plot of the current consumption is needed to figure out what goes on. There are too many unknown variables as it is now. 

 

[pbecchi]

I received it yesterday...... I am probably not able to use it well!

I have just extracted a trace a power consumption during starting 36s (32 sec advertising+ 4 s central UART waiting for events)

What else can I do with PPK? There is any way to log data out of it?

What really you would like to see? 

May be you can learn me on how to use better the PPK!

This by the way is the most favorable case ...the one with the lower power consumption!

Probably I may send same plot for the case of higher drain......

Let me know?

[pbecchi]

Still waiting your comments......!

Thanks.

[MartinBL]

Can you upload a screenshot showing the current consumption of the bad device?

[pbecchi]

Here you are:

[MartinBL]

In your first post you talked about 

7mA during advertising

3mA during loop if not connected

6mA during loop if connected.

Your screenshot looks quite normal and you are drawing 441 uA on average.

A couple of weeks ago you also mention that "On my last test I have assembled a new BT832X and this time got same high power drain as for BT832". Is it so that what module you are using doesn't matter anymore? That points to a problem with your HW doesn't it?

Can you please summarize your current situation and problems?

Do you know what goes on in the areas I have marked with green here:

Are you toggling on and off an LED for example? It could also be a peripheral (TWI or UART for example) that does some work.

[pbecchi]

Just to explain and summarise:

All initial measurements have been done with a multimeter that normally give a inaccurate average measurement.

All initial test where done with no UART while final ppk plots where both done with UART active.

This explain why ppk average reading on BT832X exceed the one performed with the multimeter.

I am not home now, but as soon as I am back, I will repeats PPK plots with disabled UART on BT832X , BT832 and nRF52DK.

I have noted that abnormal consumption is related to UART....

When UART is disabled I have found minimal drain on nRF52Dk and even less on BT832X, while I find abnormal values on BT832(the ones of first message).

When UART is enabled I find higher drain (300 to 500uA) with similar results for all boards.

Yes, the problem may be HW related...could be that with a faulty soldering of the BT832 LGA pins ...a UART pin could be grounded..... 

Could this explain the UART related behaviour?

[MartinBL]

If the exact same .hex file produces different results on two different boards you can assume it is a HW or soldering issue:

If you desolder a misbehaving module from a board, solder it onto another board, and the problem problem persists, then it is likely related to the module. 

The UART peripheral uses the HF clock. This clock system draws ~470 uA.