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.

CCS/OMAP-L138: blink not working when imported as a task in SYN/BIOS

Part Number: OMAP-L138
Other Parts Discussed in Thread: SYSBIOS

Tool/software: Code Composer Studio

Hi All

1/ I have a led blink example working on the ARM core in regular C.

2/ I have now created a new project in syn-bios project and have created a task with the working code. It compiles error free but produces the following error

i.sysbios.family.arm.exc.Exception: line 205: E_dataAbort: pc = 0xc3004974, lr = 0xc300cf04.
xdc.runtime.Error.raise: terminating execution

3/ From what I can tell there is some issue accessing hardware functions from a task. specifically:- 

3.1/ PSCModuleControl(SOC_PSC_1_REGS, HW_PSC_GPIO, PSC_POWERDOMAIN_ALWAYS_ON, PSC_MDCTL_NEXT_ENABLE);

3.2/ savePinmux = (HWREG(SOC_SYSCFG_0_REGS + SYSCFG0_PINMUX(13)) & ~(SYSCFG_PINMUX13_PINMUX13_15_12));

HWREG(SOC_SYSCFG_0_REGS + SYSCFG0_PINMUX(13)) = (PINMUX13_GPIO6_12_ENABLE | savePinmux);

3.3/ GPIODirModeSet(SOC_GPIO_0_REGS, 10, GPIO_DIR_OUTPUT);

There is obviously something that I need to know that can not be found in other examples. Can any one supply a program that blinks a LED on the ARM core in the SYN Bios environment?

Any advice would be greatly received.

Andrew 

  • Andrew,

    We don`t support TI RTOS/SYSBIOS on the ARM on ARM9 device like OMAPL13x devices. This is a usecase that is untested in the TI RTOS environment so we wont be able to provide any guidance on this issue.

    We have a Linux or a bare-metal offering for this device to be run on the ARM. If this usecase is critical to your development, please reach out to your local TI contact and provide the usecase and we may need to evaluate the effort to enable SYSBIOS on ARM on this device.

    TI RTOS is support on Cortex A8 (AM335x), Cortex-A9 (AM437x) and A15 (AM57xx) and C66x (AM57xx, OMAPL1x).

    Regards,
    Rahul