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.

TMS320F28379D: Initializing ADC on CPU2

Part Number: TMS320F28379D
Other Parts Discussed in Thread: SYSCONFIG

Hello,

I am working on a DSP-like project where I sample an incoming signal, perform filtering and send it out on a UART bus. I would like to split the operation between two cores where CPU2 does all the ADC work and CPU1 does the rest.

Using Resource Explorer I imported an empty project for Dual Core with Sysconfig:

I used Sysconfig to create a simple project where I initialized ADCA for CPU1 and ADCB for CPU2. There is no IPC between the two CPUs. The project was loaded into LAUNCXL-28379D.
When I use the debugger, I see that ADCA registers were initialized properly. However, the ADCB control registers remain in the default state after the initialization is completed on CPU2.

I suspect the ownership of ADCB is taken by CPU1, but I cannot confirm that. Can you help me to resolve this issue?

Thank you.
Leon

  • Hello,

    I wanted to provide additional information on the issue above,

    I downloaded the ipc_ex2_gpio_sysconfig project from Resource Explorer and loaded it to the LaunchPad. The LEDs were toggling as expected. I added configuration for ADCB in the CPU2 part of sysconfig file and I see the same problem.

    Any recommendations?

    Regards,
    Leon

  • It looks like that I found the missing part. I needed to configure peripherals to CPU2 in CPUSELXX registers (under DEV_CFG_REGS - Section 3.15.9 in TRM). In the sysconfig tool, I added the SYSCTL module (under SYSTEM selection) and configured ADCB to connect to CPU2:

    After performing these steps, I was able to initialize ADCB by CPU2.

    Leon

  • Sorry I wasn't able to get back to you sooner. Glad the issue is resolved!