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

Unable to set the environment variables correctly in OMAP L137/ZTMS320C6747 EVM

Rahul Jaimini
Prodigy 40 points
Other Parts Discussed in Thread: CCSTUDIO

Hi !

Its my first time with this board. Till now, I have followed all the Getting Started guides blindly and I am done with Hardware Setup, Installing the SDK software, Flashing the Bootloaders, Setting up the Target File System. So after all this, when I tried to boot, I am getting the underpasted response.

 

BOOTP broadcast 1

*** Unhandled DHCP Option in OFFER/ACK: 43

*** Unhandled DHCP Option in OFFER/ACK: 43

DHCP client bound to address 161.85.18.28

TFTP from server 161.85.26.197; our IP address is 161.85.18.28

"In my earlier attempts I did set this address in serverip env but now I have changed my Linux workstation to a different machine (161.85.18.114) to work as root. But the EVM doesn't seem to respond to this. Everytime I set the variables according to new configuration and saveenv, it does ROM erase and re write. But I donno how it gets the previous serverip again (161.85.26.197) while trying to boot."

 

Filename '\boot\pxeboot.n12'.

Load address: 0xc0700000

Loading: ## Warning: gatewayip needed but not set

#####

done

Bytes transferred = 25068 (61ec hex)

Wrong Image Format for bootm command

ERROR: can't get kernel image!

 

 

"I believe I have everything well setup on the File System side. Its just trying to connect to undesired tftp server where it won't find a thing and that's why the ERROR."

PS: All of my machines are under the same subnet 161.85.18.*

SOS ! SOS ! SOS !  :((

  • 0
    Prodigy 40 points

    never mind guys ! 

    I got it up and running with tftpboot 0xc0700000 [server]:[bootfile] command and finally am able to log in as root !

    but the mystery behind non-changing serverip is still no clear to me ! ... 

  • 0 in reply to Rahul Jaimini
    TI__Mastermind 37340 points

    this is great news.  I believe this mistery may have something to do with how your network dhcp server responds to requests.  As a test, you can try using static IPs (get rid of network and dependance on dhcp server) per the following app note: http://focus.ti.com/general/docs/litabsmultiplefilelist.tsp?literatureNumber=spraaq0

  • 0 in reply to Juan Gonzales
    Prodigy 40 points

    Hi Juan,

    I understand you have great expertise in development boards. Could you may be guide me through the process of software development (DSP/BIOS programming) for this embedded platform. Lemme provide you the details in short.

    OMAP L137 TMS3206747 Floating Point Starter Kit (board: filesystem in place, up n running; dsplink.ko kernel module loaded; sample applications like loop, ringio etc successfully simulated)

    EVMOMAP-L137 CCStudio v3.3 installed.

    There're so many pdfs and I am not able to find any precise way coz I find them incoherent.

    Please Help !!

     

  • 0 in reply to Rahul Jaimini
    TI__Mastermind 37340 points

    To be honest, my expertise lies on ARM/Linux side; there are other active community members that have much better knowledge than I do on DSP side that I am sure can provide better direction than I can in these matters.  Just as an FYI, you can think of DSP/BIOS as the operating system for DSP, CCS is the IDE... In addition, w/ OMAPL137 SDK, you will have some DSP peripheral drivers for the EVM...  From a software point of view, on top of these OS (DSP/BIOS) and drivers, you can use (but do not have to) our codec engine framework... this framework is used in many of our DaVinci/OMAP platforms hence from a DSP portability standpoint, it may be beneficial to use it.  In addition, it provides a software architecture where DSP algorithsm from different vendors can co-exists by defining satandards such as XDAIS (defines means by which algos ask for system resources rather than taking them, framework manages resources) and requiring algorithms comply to it to be able to fit into the framework.....  Anyway, this is just s brief overview of the software layers.  With regards to using CCS, there are tutorials included with the IDE isntall, but maybe someone else can offer better advice on this front...