Dear STea,
Thanks for the response! I've shared my ADC_Test.ioc file. How will you identify whether there are conflicting pins or not?
When hovering over the three ADC options, I *do* note that they claim to potentially be in conflict with ETH RMII:
Yet it's not clear WHAT might be in conflict. I am not using PB0 (as far as I know).
With my board, my ONLY option for the ETH mode is RMII:
If the ADCs are really in conflict with the ETH RMII...does this mean this board is not suitable to run both components simultaneously?
Thanks for the provided link. I feel like my situation is a bit different, as I'm not getting "noise" in the ADC buffer (at least, I don't think so), but rather the buffer isn't being populated at all.
I'm eager to learn what you can glean from the .ioc file!
Thanks in advance for any help you can provide!
Dear STea,
Thanks for the reply. I'd like to share some additional findings regarding this issue. I believe that maybe my ADC/DMA problem is less related to ETH/LWIP, but instead related to enabling the I/DCache (which I enable as part of the ETH/LWIP configuration).
Consider the following steps to create a brand new project from the CubeIDE:
- File -> New -> STM32 Project
- Board Selector tab -> Commercial Part Number: NUCLEO-H723ZG
- Select the board in the lower right-hand pane and click Next.
- Fill out the Project Name (e.g., ADC_Test) and click Finish.
- When prompted with "Initialize all peripheral with their default Mode?", click No (otherwise the ETH and other peripherals will be enabled by default).
When the IDE loads the new IOC file:
Under Pinout & Configuration:
- Select Analog -> ADC1
- Configure IN2 as IN2 Single-ended.
- Under DMA Settings, click Add and then select ADC1 from the dropdown in the DMA Request column.
Switch to Clock Configuration:
- Click Resolve Clock Issues and accept the defaults.
Back under Pinout & Configuration.
Under the ADC1 Parameter Settings, it should look like:
Save the IOC file and click Yes to generate code.
In main.c, add the following code before the main(void) function in the USER CODE 0 section:
/* Private user code ---------------------------------------------------------*/
/* USER CODE BEGIN 0 */
#define ADC_BUF_LEN 2000
int adcEnd = 0;
uint16_t adc_buf[ADC_BUF_LEN];
void HAL_ADC_ConvCpltCallback(ADC_HandleTypeDef* hadc)
{
if (hadc == &hadc1)
{
adcEnd = 1;
}
}
void HAL_ADC_ErrorCallback(ADC_HandleTypeDef *hadc)
{
int errorCode = hadc->ErrorCode;
}
void process_request_adc()
{
adcEnd = 0;
memset(adc_buf, 0x0F, sizeof(adc_buf)); // Decimal 3855 - just some arbitrary value to see if the buffer changes.
// Trigger the ADC.
HAL_ADC_Start_DMA(&hadc1, (uint32_t*)adc_buf, sizeof(adc_buf));
while(!adcEnd)
{
HAL_Delay(10);
}
uint32_t* test = adc_buf;
}
/* USER CODE END 0 */
In the main(void) function, within the USER CODE 2 section, add the following:
/* USER CODE BEGIN 2 */
process_request_adc();
/* USER CODE END 2 */
Save and debug the application, placing a breakpoint at the last line of the process_request_adc() function to be able to view the contents of adc_buf (or set it up as a Watch variable). You'll note that the 3885 values have been overwritten to some random values, which indicates a successful ADC/DMA action.
Stop debugging.
Under the IOC Pinout & Configuration:
- System Core -> CORTEXT_M7
- Enable Cortex Interface Settings CPU ICache and DCache.
Save the IOC file and click Yes to generate code.
Debug again. Note that the contents of adc_buf now remain unchanged from their initialized values of 3855. The ADC callback is being invoked, but the contents of the buffer we're using for the DMA are not being overwritten.
Why?!?
