Mity CPU Platforms » MityDSP-L138 (ARM9 Based Platforms)

Also, as a followup question, the StarterWare examples are setting up the system for the evmOMAPL138. For instance, the UARTecho example tries to configure UART2 while the MityDSP is setup for UART1. Are there examples setup like the starterware examples that have been configured to work on the MityDSP board? I would like to be able to run a helloworld example that would print some text out the UART so that I know I am on the right track.

Thanks,
Tim

Hello,

Thank you for starting this thraed, because I'm facing the same problem as Tim had 2 weeks ago - and unfortunatelly, I didn't succeed so far...

Following the steps I made (most of it according to the chapter Flashing an Application on the TI wiki site http://processors.wiki.ti.com/index.php/Quick_Start_Guide_StarterWare_01.10.XX.XX_%28supports_OMAPL138%29):

• Took the uart_armv5_omapl138 project from StarterWare and changed all occurance of UART2 (and related) into UART1 (see attached file uartEcho.c)
• Building the project gave me folloging warning:
  

  #10063-D entry-point symbol other than "_c_int00" specified:  "Entry" 
  

  Could that be the (a) reason, why the program isn't running?
• Then, I converted the application executable into a binary using out2rprc:
  

  out2rprc.exe uartEcho.out uartEcho.bin
  Parsing the input object file, uartEcho.out.
  File conversion complete!
  

• Also Flashing ended with Operation completed successfully
  

  sfh_OMAP-L138 -flash -v -p COM1 UBL_SPI_MEM.ais uartEcho.bin
  

• After resetting the board I get the UBL prompt qith Jumping to entry point 0xC1080000 - and that's it!
• Then I connected with JTAG to the module and investigated the Memory around 0xC1080000:
  

  $D:/Program Files/Texas Instruments/OMAPL138_StarterWare_1_10_01_01/system_config/armv5/cgt/init.asm:65:139$, Entry
  43525052    00000001    00000004    00000004    00000000    C1080000    00000000    00000044    00000005    C1080000    00000000    00000030    00000000    72746E45
  696F7079    0000746E    00000000    00000000
  Clear_Bss_Section
  00000000    00000000    00000000    00000000
  Loop
  00000000    00000000    00000000    00000001    C1080000    00000000    00000094    E59F0070
  _stackptr
  E321F0DB
  _bss_start
  E1A0D000
  _bss_end
  E2400008
  _start_boot
  E321F0D7
  _data_auto_init
  E1A0D000
  $Tramp$AA$S$$__TI_auto_init
  E2400008    E321F0D1
  UARTConfigSetExpClk
  E1A0D000    E2400008    E321F0D2    E1A0D000    E2400C05    E321F0D3    E1A0D000    E2400008    E321F0DF
  $C$L1
  E1A0D000    E59F002C    E59F102C    E2411004    E3A02000    E4802004    E1500001    DAFFFFFC    EB00026E    E59FA014
  $C$L2
  E1A0E00F    E12FFF1A    E24FF008    C3FF7FFC    C1080ECC    C1081060    C1080DE4    C1080A24    EA000264    E1A00000    00000001
  $C$L3
  C1080094    00000000    00000E38    E590C014
  $C$L4
  E31C0060    1A000001    E3A00000    EA000000    E3A00001    E12FFF1E    E590C014    E20C001E    E12FFF1E    E590C00C    E3CCC038    E580C00C    E590C00C    E2011038
  E181C00C
  UARTConfigGetExpClk
  

Any help/advice will be appreciated!
Stéphane

Hi Stephane -

Unfortunately we believe you are executing the low level initialization code for the TI EVM which is different than what needs to execute for our module. We believe this is why you are having difficulty.

We need to address for you how we are going to get StarterWare support functional for you (and other customers) on our boards. We will work to address this as quickly as possible.

Thank you -
Tom

Hi guys,

Just wanted to give you a heads up that we've been able to get the EVM UART echo example in the TI startware up and running here at Critical Link. We've been able to load with with the debugger/emulator as well as load the ELF output file using an updated (and posted) version of u-Boot that includes the loadelf command. I posted what I could on a Startware wiki page. It's "hot off the presses" but seems to be working.

Over the next couple of days we'll try to refine the process and add some more information. Would appreciate any comments. I know this is late (maybe too late), but I wanted to circle back with you on this.

-Mike

see StarterWare

Quick note. The new u-Boot command to load up the Starterware image was "bootelf" not "loadelf". I've corrected the wiki page. Sorry for the confusion (I was trying to post that before having to climb on an airplane!). The u-Boot image should have that command.

-Mike