Hi Nii, What board are you using? It appears like an incorrect ADC board configuration.
The analog value for channels 4 and 5 are changing a little bit from each sampling, but they appear to make sense. Try to isolate the issue, you can start with a single channel, start without DMA, etc. Also enabling the DEBUG ADC could give you some hints. BR, Alan On 8/6/20, Nii Jyeni <niijy...@hotmail.com> wrote: > I found a strange problem when using the latest source code to test the ADC > example. The analog value can be obtained when the ADC example is run for > the first time. When the ADC example is run again, it is blocked and it > looks like it is dead. But send Ctrl+C to the console can terminate it. > > OS:MacOS > Nuttx:nightly > MCU:stm32f429iit6 > Board:customize > > NuttShell (NSH) NuttX-9.1.0 > nsh> adc -n 2 > adc_main: g_adcstate.count: 2 > adc_main: Hardware initialized. Opening the ADC device: /dev/adc0 > Sample: > 1: channel: 4 value: 3091 > 2: channel: 5 value: 3782 > Sample: > 1: channel: 4 value: 3192 > 2: channel: 5 value: 3612 > nsh> adc -n 2 > adc_main: g_adcstate.count: 2 > adc_main: Hardware initialized. Opening the ADC device: /dev/adc0 <— > terminated by send ctrl + c > nsh> adc -n 2 > adc_main: g_adcstate.count: 2 > adc_main: Hardware initialized. Opening the ADC device: /dev/adc0 <— > terminated by send ctrl + c > nsh> > > This is the configuration information about ADC that I am using: > CONFIG_STM32_ADC1=y > CONFIG_STM32_ADC1_DMA=y > CONFIG_STM32_TIM1=y > CONFIG_STM32_TIM1_ADC=y > CONFIG_EXAMPLES_ADC=y > CONFIG_EXAMPLES_ADC_GROUPSIZE=3 > CONFIG_ADC=y > > Does anyone know what is going on? and how to solve this problem.
