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

Making boot files for C6670

Victor Kazmirenko
Guru 13202 points


Hello!

I apologize if I post to wrong place and ask to move this question to more appropriate forum in such a case.

I am trying Ethernet boot for C6670. At first I want to verify boot process with EVM, next I will proceed with custom board. I have found example called 'simple' in MCSDK. Though batch file did not work for me, I was able to reproduce all steps one by one and booted example to DSP. Next I am trying to load my custom app. One of the first steps is to perform hex conversion. For that I see

hex6x simple.rmd

command in the makefile. My concern is .rmd file. From its contents I can guess that is kind of option set for hex conversion utility. I'd like to know how do I get this file for my custom application. Is there a way to automate this task? Pointing to further reading appreciated.

Thanks in advance.

  • 0
    TI__Guru** 116770 points

    The .rmd file is a mnaully generated file. If you open the file in a editor, you should be able to see the options used with the hex6x tool. For a custom application, all you need to do is modify the name of the application file (.out) and the output boot table file(.btbl) name in that file. If you want to modify the options for the hex6x tool, the tool is documented with all its options and examples in the Chapter 11 of TMS320C6000 Assembly Language Tools v7.4 documentation that should be part of your CCS installation under $(INSTALL_DIR/ccsv5/tools/compiler/doc)

    Hope this helps, let us know if you have any follow up questions.

    Regards,

    Rahul

  • 0 in reply to Rahul Prabhu
    Guru 13202 points

    Hello, Rahul,

    Thank you for information. The reference you provided is what I was looking for. I think I understand meaning of input file name, ASCII mode, boot mode, entry point and order options. Experimentally I found that length should be increased in ROMS directive to accommodate my program. Please point me out, where should I read about origin = 0x400.

    Thank you.

  • 0 in reply to Victor Kazmirenko
    Intellectual 530 points

    Hello 

    if i am not mistaken origin and length

    represent which adresses to take out of the .out file into the boot table file created.

    This means if the .out file containts only section the falls within  origin - (origin + length)

    if you have a section in the .out file which doesnt fall within this range 

    than it would not appear in the boot table file

    so you would not have this code

    this is my assumption

  • 0 in reply to ilay nissim
    Guru 13202 points

    Hello,

    I guess, your understanding is correct. However, my concern was why origin is exactly 0x400? Not t say that is magic number of 1K, and that might have something to do with boot sequence, but I don't see clear reference yet. Would appreciate pointing me out.