SYSBIOS on Beaglebone Black

Hi Emmanuel,

Thanks for your help which pushed me ahead in my target. I'm using sysbios v6.35. I have followed the guide given in above link. I put the api's for led blink from starterware compilation and linking have been resolved but i cant get the led blinking. Any suggestions.

Thank you

Hi Kasim,

I think the problem you may be facing is due to MMU configuration.  The MMU has to be configured to allow the peripherals to be accessed by code at run-time.  Please see the SYS/BIOS API for the MMU: 

SYS/BIOS API -> ti.sysbios.family.arm.a8 -> Mmu

The code should be similar to the following: 

var Mmu = xdc.useModule('ti.sysbios.family.arm.a8.Mmu');
Mmu.enableMMU = true;

/* Force peripheral section to be NON cacheable */
var peripheralAttrs = {
    type : Mmu.FirstLevelDesc_SECTION, /* SECTION descriptor */
    bufferable : false,
    cacheable  : false,
    shareable  : false,
    noexecute  : true,
};

/* Define the base addresses in which the peripherals reside. */
/* Clock Module, GPIO0, UART0, I2C0 */
var peripheral0BaseAddr = 0x44E00000
/* GPIO1, UART1, UART2, I2C1, McSPI0, McASP0 CFG, McASP1 CFG */
var peripheral1BaseAddr = 0x48000000
/* GPIO2, GPIO3, UART3, UART4, UART5, I2C2, McSPI1 */
var peripheral2BaseAddr = 0x48100000

/* Configure the corresponding MMU page descriptor */
Mmu.setFirstLevelDescMeta(peripheral0BaseAddr, peripheral0BaseAddr, peripheralAttrs);
Mmu.setFirstLevelDescMeta(peripheral1BaseAddr, peripheral1BaseAddr, peripheralAttrs);
Mmu.setFirstLevelDescMeta(peripheral2BaseAddr, peripheral2BaseAddr, peripheralAttrs);

Let me know if this helps,

-- Emmanuel

Yes.... thank you Emmanuel..Now LED is blinking.

       Now i am trying to make idle task which will blink LED.

      but when i start debug then code was terminated and console output was :

               ti.sysbios.family.arm.exc.Exception: line 176: E_dataAbort: pc = 0x80001f58, lr = 0x80007170.
               xdc.runtime.Error.raise: terminating execution

    this error was out when BIOS_Start() was executing.

Please help me i am new with RTOS ans SYSBIOS....

  Thank You

    Nilesh

Nilesh,

Please post this to a new thread rather than appending new issues on an existing chain.  In that way, you will get a faster response from the person currently assigned to the forums, and it will be easier for others to find.

Hi Emmanuel and David,

Please help me..i have started new thread on How to configure HWI in sysbios for beaglebone black.

http://e2e.ti.com/support/embedded/tirtos/f/355/t/320044.aspx

Thanks

Nilesh

Hello, I'm having the same issue as the thread starter where I just get the "Jumping to StarterWare application" thing.  My board is the BBB, and I am not using JTAG, only SD boot.

I built the bootloader project in StarterWare, and renamed the resulting boot_ti.bin to "MLO".  That is the MLO that i am using right now.  I understand that it requires a "converted" application binary as well.  The Starterware examples run fine, as long as I use and rename the "<application_name>_ti.bin" files.  Whatever are the normal "<application_name>.bin" files for?   But that is not my current question. 

When I built the Sys/bios project, I get the resulting "hello_BeagleBone_Black_CortexA.out" file as the binary.  I added post compile instructions to make the .bin's  this way.

"tiobj2bin.bat"  "task_BeagleBone_Black_CortexA.out"  "task_BeagleBone_Black_CortexA.bin"  "armofd.exe"  "armhex.exe"  "mkhex4bin.exe" & "tiimage.exe" "0x80000000" "NONE" "task_BeagleBone_Black_CortexA.bin" "task_BeagleBone_Black_CortexA_ti.bin"

I then renamed the last "...ti.bin" to "app" and put it on the SD card with the original MLO.  It just hangs at "Jumping to StarterWare Application". 

What am I doing wrong?