• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 17 subscribers
  • Views 482 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

CC1352R: Observation of AUX domain event bus signal on GPIO pin in the Sensor Controller

Angel Trendafilov
Intellectual 315 points
Part Number: CC1352R


Hello,

We decided to test the basic functionality of the Sensor Controller using Timer 2 and the option to observe signals on GPIO pins.

For this purpose we used a new Launch Pad CC1352R1F3, SDK 6.10.00.29, example project PWMLED2 and new SC project with new task.

Everything works properly (PWM signal is generated), but when we started the observation of the signals we found something strange. We can monitor/observe the signals OBS_AON_RTC_CH2, OBS_AON_RTC_CH2_DLY and OBS_SCLK_LF, but never the signal OBS_AON_RTC_4KHZ. This is absolutely strange for us, because this functionality is already used in our previous old project.

We tested everything that we can - different SDKs and examples modifying only the SC project to observe this signal. This functionality works only with our old project created with SDK 4.10.00.78 and without SYSCFG file.

We will be happy if you can help us. Thanks in advance.

  • 0
    TI__Mastermind 25645 points

    Hi Angel,

    Did you develop the Sensor Controller application using Sensor Controller Studio, or did you it using the SCS assembly language reference?

    It might be that you have to migrate/recompile the Sensor Controller application using a newer version of the studio.

    Regards,

    Arthur

  • 0 in reply to Arthur R☑️
    Intellectual 315 points

    Hello Arthur R,

    The project is developed using Sensor Controller Studio 2.9.0.208, Patches 1, 2, 3, 4.

    It is very simple. One SC task with digital output. The code is:

    obsSelectSignal(OBS_AON_RTC_4KHZ);

    obsConnectSignalToGpio(AUXIO_O_CLK_OUT); // CLK_OUT is a digital output defined in the SC task. Not used by the main MCU.

    This code exists only in the Initialization code. The sections Execution and Termination code are empty.

    What is strange here.

    If the code is:

    obsSelectSignal(OBS_SCLK_LF);

    obsConnectSignalToGpio(AUXIO_O_CLK_OUT);
    It works properly. We cam measure the output frequency 32.768kHz.
    If the code is:

    obsSelectSignal(OBS_AON_RTC_CH2);

    obsConnectSignalToGpio(AUXIO_O_CLK_OUT);
    or
    obsSelectSignal(OBS_AON_RTC_CH2_DLY);
    obsConnectSignalToGpio(    AUXIO_O_CLK_OUT);
    It works properly. We cam measure the output frequency 1Hz.

    if the code is:

    obsSelectSignal(OBS_AON_RTC_4KHZ);

    obsConnectSignalToGpio(AUXIO_O_CLK_OUT);

    It doesn't work. Noting on the output.
    The fact that the first 2 configurations work properly means that the project is compiled correctly.
  • 0 in reply to Angel Trendafilov
    Intellectual 315 points

    Any news about this issue? Thanks.

  • 0 in reply to Angel Trendafilov
    TI__Guru* 82341 points

    Hi Angel,

    Please use "Timer 0 Event Trigger" or "Timer 1 Event Trigger". 

    The underlying issue is that in your code, the AON_RTC:CTL.RTC_4KHZ_EN register is set to 0 (or not set to 1). If you use one of the timer event triggers, SCS will generate code to set the register to 1.

    Cheers,

    Marie H

  • 0 in reply to Marie H
    Intellectual 315 points

    Hi Marie H,

    Thanks for this information. Sorry, but this is a patch. I loose one event trigger only to enable this functionality. Where is documented? Help? Application notes. Good job TI.