This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

saadc value affects next values

Hi, I'm developing custom board with nrf52832

The problem is that when saadc returns negative value, all values that saadc returns after are max possible values from config So the previous adc value affects all that goes after it. They stay at max until adc will return another negative value.

Things I tried that didn't help:

Checking gnd/0
Setting adc limits by nrf_drv_saadc_limits_set
Pin in single-ended mode
Calibrating adc (different time intervals)
Bitmask to adc returned value (adc is configured with 12 bit, so i zero 4 top bits)
Different channel configs

Looking for help, I'm confused a lot

Top Replies

Parents

0 Jørgen Holmefjord over 5 years ago

Hi,

I'm not sure I understand what you mean by " max possible values from config". Can you give some examples of the values you are seeing? The samples from the SAADC are 16-bit signed integers.

Best regards,
Jørgen
0 Jørgen Holmefjord over 5 years ago in reply to Jørgen Holmefjord

Are you using single-ended or differential mode?

What reference and gain settings are you using?

What is the supply voltage of the chip?

What is the voltage level on the analog input that you are sampling?
0 Jørgen Holmefjord over 5 years ago in reply to polyblank

That is true, but from the image it looks like you input a much higher voltage than that. 3V input with 14-bit mode and 1/6 GAIN/internal reference should give samples of ~13-14000. Is this the raw values in the buffer, or have this been transferred over BLE? Have you checked the voltage level on the analog input with a scope etc., to see that there is nothing else pulling the voltage low? Which analog input do you use? Have you tested with another pin?
0 polyblank over 5 years ago in reply to Jørgen Holmefjord

I can't physically reconfigure connection to test with another pin right now. I use ain0(p0.02). The values you see are transferred over BLE, but they are the same as raw values as I can see in debug mode
0 Jørgen Holmefjord over 5 years ago in reply to polyblank

Are you able to scope the pin, to check that the input is what you expect? Do you have a nRF52 DK that you can reproduce this on, to rule out any board-related issues?
0 polyblank over 5 years ago in reply to Jørgen Holmefjord

I'm going to check all the hardware a bit later. But first, is there any chance this bug is a software problem?
Anyway, thank you Jørgen for answering my questions. I'm very glad that I can get help from specialist. Huge respect to Nordic tech support.
0 Jørgen Holmefjord over 5 years ago in reply to polyblank

I can't think of anything in particular, but if you could post your code I can have a look at it to see if I can spot anything.

Reply

0 Jørgen Holmefjord over 5 years ago in reply to polyblank

I can't think of anything in particular, but if you could post your code I can have a look at it to see if I can spot anything.

Children

0 polyblank over 5 years ago in reply to Jørgen Holmefjord

https://github.com/po1yb1ank/emg_hardware

Sorry for complete mess in main.c, I've been testing a lot of things :)
0 Jørgen Holmefjord over 5 years ago in reply to polyblank

Are you using nRF52832, or nRF52840? From this ticket it looks like you use nRF52832, but in the GitHub repository, it seems like you have used pca10056 projects which are for nRF52840.
0 polyblank over 5 years ago in reply to Jørgen Holmefjord

im using nrf52832, as I said this is test project where I changed 10056 pinouts
0 Jørgen Holmefjord over 5 years ago in reply to polyblank

Ok, I see that you have changed the project to use correct files and defines for nRF52832, it just looked a bit strange.

In that case, I cannot see anything in particular in your code that should cause this behavior. Did you manage to measure the analog inputs to make sure these are at the expected levels?