• State Resolved
  • Locked Locked
  • Replies 15 replies
  • Subscribers 82 subscribers
  • Views 800 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Original question:

LAUNCHXL-F28379D: Issue with ADC Interrupt Not Triggering on TMS320F28379D

LAUNCHXL-F28379D: LAUNCHXL-F28379D: Issue with ADC Interrupt Not Triggering on TMS320F28379D

Nero Dai
Prodigy 130 points
Part Number: LAUNCHXL-F28379D
Other Parts Discussed in Thread: TMS320F28379D, SYSCONFIG,

Hi guys~

I am working on a project using the TMS320F28379D microcontroller and facing an issue where the ADC interrupt is not being triggered as expected. Below is a brief overview of the problem and the steps I've taken to troubleshoot:

  1. Problem Statement:

    • Unable to get the ADC interrupt (specifically adcA1ISR) to trigger.
    • The goal is to make the following code snippet work as expected:
      c code
      while(ADC_getInterruptStatus(ADCA_BASE, ADC_INT_NUMBER1) == false) { }
      SCISendData("ADC conversion complete\r\n");

  2. Attempts Made:

    • Checked and ensured correct interrupt number INT_ADCA1.
    • Included the ADC initialization and configuration in the code.
    • Registered the interrupt using Interrupt_register(INT_ADCA1, adcA1ISR); and enabled it with Interrupt_enable(INT_ADCA1);.
    • Added global interrupt enable with EINT;.
    • Included SCI print statements within adcA1ISR to confirm if it's being triggered, which it isn't.
    • Examined potential issues related to interrupt priority and nesting.

Despite these efforts, the ADC interrupt service routine does not seem to trigger, and I am unable to identify the cause.

Additional Context:

  • Using Texas Instruments' Code Composer Studio for development.
  • ADC is expected to read temperature values.

Any insights or suggestions on resolving this issue would be greatly appreciated.

Fullscreen
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
#include "F2837xD_Ipc_drivers.h"
#include "driverlib.h"
#include "device.h"
#include "stdio.h"
#include "string.h"
#include "led.h"
#include "key.h"
#include "sci.h"
#include "micro_printf.h"
#include "board.h"
#include "spi_test_v1.h"
#define delay_s(x) SysCtl_delay(((((long double)(x)) / (1.0L / \
(long double)DEVICE_SYSCLK_FREQ)) - 9.0L) / 5.0L)
#define delay_ms(x) SysCtl_delay(((((long double)(x)) / (1000.0L / \
(long double)DEVICE_SYSCLK_FREQ)) - 9.0L) / 5.0L)
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

#include "driverlib.h"
#include "device.h"
#include "board.h"
#include <stdio.h>

// 添加您的其他必要的头文件
#define MAX_DAC_VALUE 4095 // 假设DAC是12位的
#define MIN_DAC_VALUE 0


//__interrupt void sciaTXFIFOISR(void);
//__interrupt void sciaRXFIFOISR(void);
uint16_t adcResult;
float temperature;
void SPI_GPIO_Init();
void spi_init();
void spi_TX(uint16_t data);
uint16_t calculate_DAC_value(float voltage);
short read_current_temperature();
void initADC();
void initADCSOC();
void initEPWM();
//__interrupt void adcA1ISR();
//void initSCI(void);
void SCISendData(const char *string);

// PI Controller Variables
volatile short tsvo_pg, tsvo_ig; // Proportional Gain (PG) and Integral Gain (IG)
volatile short tsvo_setpoint, tsvo_err, tsvo_out;
volatile long tsvo_acc, tsvo_mem;

void spi_initController() {
Device_init();
Device_initGPIO();
//initSCI(); // 初始化SCI
initADC();
initADCSOC(); // 初始化ADC
initEPWM(); // 初始化ePWM

DINT;
SPI_GPIO_Init();
spi_init();

// 初始化PI控制器的参数
tsvo_pg = 2000; // Proportional Gain
tsvo_ig = 200; // Integral Gain
tsvo_mem = 0; // Integral memory initialization

float target_temperature = 60.0; // 目标温度60°C
tsvo_setpoint = calculate_DAC_value(target_temperature); // 设定点
}


void spi_updateController() {
// short read_current_temperature = 59;
short currentTemperature = read_current_temperature();

tsvo_err = tsvo_setpoint - read_current_temperature();
tsvo_acc = tsvo_err * tsvo_pg;
tsvo_acc += tsvo_mem;

tsvo_out = tsvo_acc >> 16;
if (tsvo_out > MAX_DAC_VALUE) tsvo_out = MAX_DAC_VALUE;
if (tsvo_out < MIN_DAC_VALUE) tsvo_out = MIN_DAC_VALUE;

spi_TX(tsvo_out);

tsvo_mem += tsvo_err * tsvo_ig;

// 打印当前温度
char tempStr[32];
// sprintf(tempStr, "Current Temp: %d\r\n", currentTemperature);
sprintf(tempStr, "Temperature: %d\r\n", currentTemperature);
// sprintf(tempStr, "Temperature: 60\r\n");
SCISendData(tempStr);
//SCISendData("Hello World\r\n");
// 检查SCI接收缓冲区
//if(SCI_getRxFIFOStatus(SCIA_BASE) > SCI_FIFO_RX0) {
//char receivedChar = SCI_readCharNonBlocking(SCIA_BASE);
// 处理接收到的字符
// 例如：回显接收到的字符
//char echoStr[2] = {receivedChar, '\0'};
//SCISendData(echoStr);
//}
DEVICE_DELAY_US(40000);
}

void SPI_GPIO_Init() {
// GPIO配置代码保持不变
}

void spi_init() {
// SPI配置代码保持不变
}

void spi_TX(uint16_t data) {
// SPI发送代码保持不变
}

uint16_t calculate_DAC_value(float voltage) {
float maxVoltage = 3.7; // 最大电压为3.7伏特

// 确保输入电压不超出范围
if (voltage < 0) {
voltage = 0;
} else if (voltage > maxVoltage) {
voltage = maxVoltage;
}

// 将电压值映射到DAC值
uint16_t dacValue = (uint16_t)((voltage / maxVoltage) * MAX_DAC_VALUE);

return dacValue;
}


short read_current_temperature() {
// 触发ADC转换
ADC_forceSOC(ADCA_BASE, ADC_SOC_NUMBER0);
SCISendData("4.ADC conversion triggered\r\n");
// 等待转换完成
while(ADC_getInterruptStatus(ADCA_BASE, ADC_INT_NUMBER1) == false) {
}
SCISendData("5.ADC conversion complete\r\n");
// 读取ADC转换结果
adcResult = ADC_readResult(ADCARESULT_BASE, ADC_SOC_NUMBER0);
char adcResultStr[50];
sprintf(adcResultStr, "ADC Result: %d\r\n", adcResult);
SCISendData(adcResultStr);
// 将ADC结果转换为温度值
temperature = ADC_getTemperatureC(adcResult, 3.0f);

// 将温度值转换为DAC值
return calculate_DAC_value(temperature);
}


void initADC()
{
// SCISendData("1Starting ADC initialization\r\n");
//
// Set ADCDLK divider to /4
//
ADC_setPrescaler(ADCA_BASE, ADC_CLK_DIV_4_0);

//
// Set resolution and signal mode (see #defines above) and load
// corresponding trims.
//
ADC_setMode(ADCA_BASE, ADC_RESOLUTION_12BIT, ADC_MODE_SINGLE_ENDED);

//
// Set pulse positions to late
//
ADC_setInterruptPulseMode(ADCA_BASE, ADC_PULSE_END_OF_CONV);

//
// Power up the ADC and then delay for 1 ms
//
ADC_enableConverter(ADCA_BASE);
DEVICE_DELAY_US(1000);
SCISendData("1.ADC initialization complete\r\n");
}


void initADCSOC() {
// SCISendData("3Starting ADC SOC initialization\r\n");
// ADC SOC配置代码
// 从adc_ex3_temp_sensor.c文件中复制对应的配置代码
ADC_setupSOC(ADCA_BASE, ADC_SOC_NUMBER0, ADC_TRIGGER_EPWM1_SOCA, ADC_CH_ADCIN13, 140);
// char message[100];
// sprintf(message, "ADC_SOC_NUMBER0: %d, ADC_TRIGGER_EPWM1_SOCA: %d, ADC_CH_ADCIN13: %d\r\n", ADC_SOC_NUMBER0, ADC_TRIGGER_EPWM1_SOCA, ADC_CH_ADCIN13);
// SCISendData(message);
// SCISendData("ADC SOC setup complete\r\n");
ADC_setInterruptSource(ADCA_BASE, ADC_INT_NUMBER1, ADC_SOC_NUMBER0);
// SCISendData("ADC interrupt source set\r\n");
ADC_enableInterrupt(ADCA_BASE, ADC_INT_NUMBER1);
// SCISendData("ADC interrupt enabled\r\n");
ADC_clearInterruptStatus(ADCA_BASE, ADC_INT_NUMBER1);
// SCISendData("ADC interrupt status cleared\r\n");

SCISendData("2.ADC SOC initialization complete\r\n");
}

void initEPWM() {
// ePWM初始化代码
// 从adc_ex3_temp_sensor.c文件中复制对应的配置代码
EPWM_disableADCTrigger(EPWM1_BASE, EPWM_SOC_A);
EPWM_setADCTriggerSource(EPWM1_BASE, EPWM_SOC_A, EPWM_SOC_TBCTR_U_CMPA);
EPWM_setADCTriggerEventPrescale(EPWM1_BASE, EPWM_SOC_A, 1);
EPWM_setCounterCompareValue(EPWM1_BASE, EPWM_COUNTER_COMPARE_A, 1000);
EPWM_setTimeBasePeriod(EPWM1_BASE, 1999);
EPWM_setClockPrescaler(EPWM1_BASE, EPWM_CLOCK_DIVIDER_1, EPWM_HSCLOCK_DIVIDER_1);
EPWM_setTimeBaseCounterMode(EPWM1_BASE, EPWM_COUNTER_MODE_STOP_FREEZE);
}

__interrupt void adcA1ISR()
{
//
// Read the raw result
//
SCISendData("ADC ISR triggered\r\n");
adcResult = ADC_readResult(ADCARESULT_BASE, ADC_SOC_NUMBER0);

//
// Convert the result to a temperature in degrees C
//
temperature = ADC_getTemperatureC(adcResult, 3.0f);

//
// Clear the interrupt flag
//
ADC_clearInterruptStatus(ADCA_BASE, ADC_INT_NUMBER1);

//
// Check if overflow has occurred
//
if(true == ADC_getInterruptOverflowStatus(ADCA_BASE, ADC_INT_NUMBER1))
{
ADC_clearInterruptOverflowStatus(ADCA_BASE, ADC_INT_NUMBER1);
ADC_clearInterruptStatus(ADCA_BASE, ADC_INT_NUMBER1);
}

//
// Acknowledge the interrupt
//
Interrupt_clearACKGroup(INTERRUPT_ACK_GROUP1);
}


void SCISendData(const char *string) {
// 使用FIFO发送数据
while (*string != '\0') {
SCI_writeCharBlockingFIFO(SCIA_BASE, *string++);
}
}

for now, sci print is
"1.ADC initialization complete

2.ADC SOC initialization complete

3.System initialization complete

4.ADC conversion triggered

"

SCISendData("5.ADC conversion complete\r\n"); -----》 fail

  • 0
    TI__Mastermind 32636 points

    Hi,

    Are you able to zip and send your complete project so I can try to replicate your issue? 

    Also, could you try using SysConfig to set up your ADC ISR? Since there are several steps for setting up the ADC ISR, it is easy to make a mistake. SysConfig will simplify the process. Please see this lab for the steps needed to setup your ADC ISR with SysConfig: https://dev.ti.com/tirex/explore/node?node=A__AVSjOwDYHkfv9LUHQuulzA__C2000-ACADEMY__3H1LnqB__LATEST

    Best Regards,

    Ben Collier

  • 0 in reply to Benjamin Collier
    Prodigy 130 points

    28379d_sci_old.ziphere we go,  thank you  for help

  • 0 in reply to Benjamin Collier
    Prodigy 130 points

    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20
    21
    //#############################################################################
    //
    // FILE: adc_ex3_temp_sensor.c
    //
    // TITLE: Sample temperature sensor and convert to temperature
    //
    //! \addtogroup driver_example_list
    //! <h1>ADC Temperature Sensor Conversion</h1>
    //!
    //! This example sets up the ePWM to periodically trigger the ADC. The
    //! ADC converts the internal connection to the temperature sensor,
    //! which is then interpreted as a temperature by calling the
    //! ADC_getTemperatureC() function.
    //!
    //! \b Watch \b Variables \n
    //! - \b sensorSample - The raw reading from the temperature sensor
    //! - \b sensorTemp - The interpretation of the sensor sample as a temperature
    //! in degrees Celsius.
    //
    //#############################################################################
    //
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
    Section ADC I use this as an example.

  • 0 in reply to Benjamin Collier
    Prodigy 130 points

    In your project, you are using the TI LAUNCHXL-F28379D microcontroller board to control the MAX1978 development board for temperature regulation. The MAX1978 is a thermoelectric cooler (TEC) controller, capable of heating or cooling the TEC. Key components of your project involve Serial Communication Interface (SCI), Serial Peripheral Interface (SPI), Analog-to-Digital Converter (ADC), and Digital-to-Analog Converter (DAC). The TEC control principle relies on the TEC device, which adjusts temperature through varying electric currents. The MAX1978 controller specifically manages the TEC by providing bidirectional current control for precise temperature adjustments. The LAUNCHXL-F28379D microcontroller acts as the central control unit, processing data, executing programs, and controlling the MAX1978, with communication facilitated through SPI and SCI interfaces. SCI is potentially used for communication with external devices or computer systems, while SPI is for interfacing with the MAX1978 or other SPI devices. ADC is utilized to read analog signals, like temperature sensor data, and DAC might be used to generate analog signals to control the MAX1978. Your provided code is likely to contain control logic for initializing hardware interfaces of the microcontroller, reading sensor data, and adjusting the TEC based on temperature feedback. The overall process involves the microcontroller reading temperature data from sensors via ADC, calculating the required heating or cooling based on set and actual temperatures, and adjusting the MAX1978 output through DAC or direct digital controls to regulate the TEC's temperature, with SCI and SPI interfaces for communication with the MAX1978 and other peripherals. Further insights into your code, especially how SPI and SCI interfaces are used, as well as how ADC readings and DAC outputs are handled, would enable more specific assistance.

    hope this helpful lol

  • 0
    Prodigy 130 points

    Part Number: LAUNCHXL-F28379D

    Hi guys~

    In my project, I am using the TI LAUNCHXL-F28379D microcontroller board to manage a MAX1978 thermoelectric cooler (TEC) controller for accurate temperature control. I employ Serial Communication Interface (SCI) and Serial Peripheral Interface (SPI) for communication, along with Analog-to-Digital Converters (ADC) to read temperature data and Digital-to-Analog Converters (DAC) for adjusting the TEC. My code primarily involves setting up these interfaces, processing sensor information, and regulating the TEC's temperature based on the data received.

    I am working on a project using the TMS320F28379D microcontroller and facing an issue where the ADC interrupt is not being triggered as expected. Below is a brief overview of the problem and the steps I've taken to troubleshoot:

    1. Problem Statement:

      • Unable to get the ADC interrupt (specifically adcA1ISR) to trigger.
      • The goal is to make the following code snippet work as expected:
        (c code)
        while(ADC_getInterruptStatus(ADCA_BASE, ADC_INT_NUMBER1) == false) { }
        SCISendData("ADC conversion complete\r\n");  //no work

    2. Attempts Made:

      • Checked and ensured correct interrupt number INT_ADCA1.
      • Included the ADC initialization and configuration in the code.
      • Registered the interrupt using Interrupt_register(INT_ADCA1, adcA1ISR); and enabled it with Interrupt_enable(INT_ADCA1);.
      • Added global interrupt enable with EINT;.
      • Included SCI print statements within adcA1ISR to confirm if it's being triggered, which it isn't.
      • Examined potential issues related to interrupt priority and nesting.

    Despite these efforts, the ADC interrupt service routine does not seem to trigger, and I am unable to identify the cause.

    Additional Context:

    • Using Texas Instruments' Code Composer Studio for development.
    • ADC is expected to read temperature values.

    Any insights or suggestions on resolving this issue would be greatly appreciated.

    ADC module using this example

    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20
    21
    //#############################################################################
    //
    // FILE: adc_ex3_temp_sensor.c
    //
    // TITLE: Sample temperature sensor and convert to temperature
    //
    //! \addtogroup driver_example_list
    //! <h1>ADC Temperature Sensor Conversion</h1>
    //!
    //! This example sets up the ePWM to periodically trigger the ADC. The
    //! ADC converts the internal connection to the temperature sensor,
    //! which is then interpreted as a temperature by calling the
    //! ADC_getTemperatureC() function.
    //!
    //! \b Watch \b Variables \n
    //! - \b sensorSample - The raw reading from the temperature sensor
    //! - \b sensorTemp - The interpretation of the sensor sample as a temperature
    //! in degrees Celsius.
    //
    //#############################################################################
    //
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

    8468.28379d_sci_old.zip

  • 0 in reply to Nero Dai
    TI__Mastermind 30185 points

    Hello Nero,

    It looks like this is still related to the post you linked here, I will join it with the original since we don't allow duplicate threads to be created (which are already actively being supported).

  • 0 in reply to Omer Amir
    Prodigy 130 points

    I'm attempting to re-describe my situation so that everyone understands what it is. Could you please delete the previous one and replace it with the revised version? It's been stuck for three days and is really perplexing.

  • 0 in reply to Benjamin Collier
    Prodigy 130 points

    I use CCS's debug tool, An error was found when trying to run the "short read_current_temperature() {" function using" step into "will point to
    "/ / * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

    //

    // Error handling function to be called when an ASSERT is violated

    //

    / / * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

    void __error__(const char *filename, uint32_t line)

    {

    //

    // An ASSERT condition was evaluated as false. You can use the filename and

    // line parameters to determine what went wrong.

    //

    ESTOP0;

    }"

  • 0 in reply to Nero Dai
    TI__Mastermind 32636 points

    Nero,

    I am a little confused by the structure of your project. It looks like you have copied many of the driverlib files into your own folder (3.device). Also it looks like you used SysConfig to generate board.h then removed your sysconfig file. 

    I stepped through your ADC initialization functions and it looks like none of the driverlib ADC functions are working correctly. None of the ADC registers are being written. My guess is that problems are being caused by the driverlib files having been manually copied and pasted in your project. I also do not think that you included the driverlib.lib file. 

    My suggestion would be to start from the adc_ex3_temp_sensor example (or the lab I linked above if you want to use SysConfig), then slowly add in your code/files. I would not mess with the files listed under "Includes", "device" or the driverlib.lib file unless you have to.

    In general, I would suggest that you add to the existing project structure instead of removing things and creating your own, if possible.

    Best Regards,

    Ben Collier

  • 0 in reply to Benjamin Collier
    Prodigy 130 points

    I apologize for any inconvenience this has given you. I started with a SCI template project provided by a classmate. I'm not familiar with many configurations because I'm new to CCS. The major program I worked on was spi_test_v1.c. The debugging tool reveals that there is an issue with the interrupt.
    “void initADC()，void initADCSOC()， void initEPWM() ”work well, but __interrupt void adcA1ISR() fail 

  • 0 in reply to Benjamin Collier
    Prodigy 130 points

    Because both two of our senior workers are on leave, working on growth alone is a little difficult. lol

  • +1 in reply to Nero Dai
    TI__Mastermind 32636 points

    Nero,

    It looks like the correct functions to set up the interrupt have been called in the user generated files, but the issue is deeper than a problem with setting up the interrupt. If driverlib functions are not working as expected, then your clocks may not be set up correctly, and peripherals may not be set up correctly.

    I have observed that the SOC setup functions are not doing anything. All ADCA registers are still reading only 0. No ADC conversions are ever being done. I am not exactly sure why, but I think it's due to problems with driverlib that are being caused by the project structure. I just checked the EPWM registers and these are not being written as well.

    You will need to address the root cause of this issue, which is likely the misbehaving driverlib functions, which is somehow being caused by the project structure. Again, I recommend that you start from a known good example, then add your code.  

    Best Regards,

    Ben Collier

  • 0 in reply to Benjamin Collier
    Prodigy 130 points


    Thank you very much; I agree with you and am attempting to resolve the driverlib issue.

  • 0 in reply to Benjamin Collier
    Prodigy 130 points


    Hi Ben Collier,
    After tweaking driverlib, it is now working. Thank you so much!

  • 0 in reply to Nero Dai
    TI__Mastermind 32636 points

    Hi Nero,

    Glad the issue is resolved!

    Best Regards,

    Ben Collier