• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 98 subscribers
  • Views 1284 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.

problems booting from flash without debugger (concerto + messageQ)

Harm Verhagen
Prodigy 210 points
Other Parts Discussed in Thread: SYSBIOS, F28M35H52C

Hi,

We're experiencing problems booting our application from Flash.

We have a sysBIOS application with IPC/MessageQ on a Concerto dual core. 

Booting from flahs doesn't seem to work, and we kinda stuck.

Simple apps (blinky_dc) boot fine, but it seems adding sysBIOS/IPC  casuses problems.

To investigate why I decided to boot a TI example appliation from FLASH.

I did read: http://e2e.ti.com/support/embedded/bios/f/355/t/195714.aspx   but I have different results.

I can't let the TI example application boot and execute from flash (without CSS)

Could you please check & comment why this fails?

What did I try?

dev board has dipswitches set to boot from flahs (blinky_dc boots from flash correctly)

1) I took the IPC message queue example app  for arm + dsp

2) I added code to the ARM part, to control LD3. giving visual indication that the app works.

    (mesq get: LD on,  mesq put: off  -> when test finishes , enable led for ~1 second, by busy wait)

   increased 

3) tested, works fine in debugger.

4) configured sysbios ARM: boot  from flash + boot C28   DSP: added "boot from flash"

5) write with debugger to flash (2x)

6) power cycle board

What did I expect 

50 blinks, then 1 second long blink.

What happens

led flashes very fast (estimated by eye 10-20 Hz),  led is never shown for 1 second.

It seems to application (an the ARM) keeps booting over and over again.

version information

BIOS: bios_6_33_05_46

IPC: ipc_1_24_03_32

Hardware: F28M35H52C  on a development board 

  • 0
    TI__Guru* 96960 points

    Hi Harm,

    What version of XDCtools are you using?

    What are the exact settings you have for the Concerto ti.catalog.arm.cortexm3.concertoInit.Boot module?

    Todd

  • 0 in reply to ToddMullanix
    Prodigy 210 points

    >What version of XDCtools are you using

    Version info: 

    • bios_6_33_05_46
    • ipc_1_24_03_32
    • xdctools_3_23_03_53
    • CCS 5.2

    I'm am going to try the same example application using a fresh  CCS 5.1 install. 

    >What are the exact settings you have for the Concerto ti.catalog.arm.cortexm3.concertoInit.Boot module?

    See below screenshots of my  sysBIOS boot settings.

    (I disable "initiate boot of the C28 processor" when I test in the debugger, enable it when trying to run standalone)

  • 0 in reply to Harm Verhagen
    TI__Guru* 96960 points

    Hi Harm,

    You need to upgrade to xdctools_3_23_04_60.There were some bug fixes in the C28 and M3 concerto Boot modules.

    FYI: Are you using TI-RTOS (also called MCUSDK). This product is a bundled SYS/BIOS, NDK, xdctools, MWare, etc plus SYS/BIOS friendly drivers for UART, I2C, EMAC, SD, USB, etc. for Concerto. You can download it at http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/index.html.

    Todd

  • 0 in reply to ToddMullanix
    Prodigy 210 points

    xdctools_3_23_04_60  helps !!

    I am able to boot the example application (IPC messageQ)  standalone now.

    These are the versions that work:

    bios_6_33_06_50
    ipc_1_24_03_32
    xdctools_3_23_04_60

    We are not using TI-RTOS.

    Next, we go try go make 'our' app boot standalone, using the versions mentioned above.

    Thanks!