• State Answer Suggested
  • Locked Locked
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 99 subscribers
  • Views 422 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.

Start working on DM355 DVEVM

Simone Mauroner
Prodigy 120 points

Hi,

after setting up the board I'm trying to start working on it.

First of all I've launched the demos but only the "decode" demo works. That's because I've a PAL camera. I've changed the J1 jumper and set the bootargs accordingly to the instructions I've read on the GSG and on some threads here on the forum: no results. The ntsc mode is always selected. What's the matter? I always get "PAL camera connected but NTSC selected"...

videostd variable is correctly set by J1 as "pal"

My bootargs are:

bootargs=console=ttyS0,115200n8 noinitrd rw ip=192.168.10.11:192.168.10.10:192.168.10.1:255.255.255.0:::off root=/dev/nfs nfsroot=192.168.10.10:/home/ns/workdir/filesys,nolock mem=116M video=davincifb:vid0=720x576x16,2500K:vid1=720x576x16,2500K:osd0=720x576x16,2025K davinci_enc_mngr.ch0_output=COMPOSITE davinci_enc_mngr.ch0_mode=pal

Second (and most important) point:

I've compiled and run the "Hello world!" program using the arm gcc but, since I'm not a linux geek, I hoped to have an IDE included in the box (as Microchip, Atmel, Rabbit, Cyan tech.  do) which could lead me from very basics.

I cannot understand where is it. I read, on some threads, about commercial tools but, as I'm evaluating the product, I'd prefer not to spend more money before I decide if the 355 is what I'm looking for (BTW I think this is the aim of eval boards...).

Thanks,

s.

  • 0
    Expert 1200 points

    you are probably already doing cross compilation on a PC.

    this PC might run a PC-Linux like Red Hat or Fedora Core.

    there is a big bunch of free Editors and even commercial third party tools including some products from MontaVista and similar vendors.

    the best known free solution might be nowadays "Eclipse".

     

    the most common denomiator for them all is the GNU make utility.

    just hook in a "make all" into your editor of choice and you have an IDE.

    Debugging might be your third aspect and the variety of solutions in this area is similar.

     

    i think no one at TI wanted to re-invent the "wheel" in that case.

     

     

    PAL/NTSC selection is based on some jumper that far that i know.

    some of the samples will honour it, other might now at present time.

    using only 640x480 (=NTSC) from a 762x576 (=PAL) input image

    ensures that the samples should run despit this.

     

    having multi standard support is sort of custom application development.

    and it would make the samples look more complex, e.g. by the need of

    dynamically allocating video buffers and similar. it would be more complex

    when video output and input would follow different standards and thus

    some buffer and rate conversion would be needed to resolve their interconnection.

     

    if you have the source or write your own set of sources

    then you should be able to go anywhere you want with your project.

  • 0 in reply to Alexander Stohr
    TI__Mastermind 37340 points

    I believe to to get PAL working, you need to run the demos with the correct option (-y 2); this is explained in the accompanying help files (encode.txt, decode.txt, and encodedecode.txt) or by running the demos with the -h (for help) option. 

  • 0 in reply to Juan Gonzales
    Prodigy 120 points

    Hi Juan,

    the "-y" option is not present (dvsdk_1_30_00_23)

    s.

  • 0 in reply to Alexander Stohr
    Prodigy 120 points

    Hi Alexander,

    that's the point ! I'd like to use Eclipse (I used it for java programming) but for me it's not so easy to set up the environment in order to use it. IMHO TI should give to the customer something better than the "Getting Started Guide" (maybe there's some documentation but I can't find it).

    Now I can boot via tftp+nfs but I'm not able to anything. I tried to build the usual example to switch the led off, I got tons of errors regarding libraries and header files. Of course something in the PATH (or something else) is wrong but what? As I told I'm not a linux geek. I've the hands on the DVEVM since wednesday and I'm still struggling against setenv, bootargs, path etc. I know that the DM355 is not a PIC or an AVR but with them I was able to make something interesting after 30 minutes.

    s.

  • 0 in reply to Simone Mauroner
    Expert 1200 points

    thanks for providing us the link to the detail explanation in the wiki. i suppose it solved your query.

    (it seems i added the category tag to that wiki topic some ages ago whilst not really reading or remembering its contents - as it was done fro dozends of similar texts, so please excuse not popping up at all with that link in my reply.)

     

    i admit the DM355 as an ARM-on-Linux system is more complex than a conventional small scale embedded device but it buys you more advanced capabilities like developing high performance audio and video applications. even if it comes to you as a "System on a Chip" (SoC) its definitely more comparable to a PDA or PC system than to a "bit moving" micro processor. having USB, Ethernet, IDE, PCI and a few more base technologies as your system design options is easier to attach when using all those units from via a well know, wide spread, in depth documented, highly flexible and standardized operating system. alternate operatings systems found in the DaVinci family consists several other RTOS, some mobile platforms and some WinCE versions. all have their pros and cons - if you would ask me for the pros of linux then its the openness of its own code and the rich set of applications, network services and tools you can get for free for merging into your project if ever a special need pops up.