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

DM355 Flash And Boot Utils build

John Reynolds
Intellectual 255 points

Hi, We're trying to flash a product based on the DM355EVM demo pcb. I was able to flash the DM355EVM UBL and uboot with

the DM355 FlashAndBoot Utils1-10 pre-compiled bins . Our  new product is using a different flash chip, a MT29F2G08AADWP-D,

being that  the one used in the demo pcb is being discontinued.  When I try to flash the new device I  get a NAND open error. I assume the

FlashAnd Boot Utils1-10 doesn't support  the new device's ID.

 I looked at the make script for the  DM355 FlashAndBoot Utils1-50 code and it looks like it uses GNU linux make tools and linux

commands, ie rm etc. The CSS branch references MONO C# ,so I assumed this would run under linux with the MONO package and

a arm-linux-eabi-gcc cross compiler. But I  also see a reference to timake and a .pjt file that looks like it requires

Code Composer Studio  to build !

 I'm confused, how do I build the  FlashAndBoot Utils ?

 

Thanks,

 John

 

  • 0
    Intellectual 255 points

    I'm making some progress building  the DM355 FlashAndBoot Utils1-50. I installed CCS 3.3 on Win XP  along with

    TMS470 Code Generation Tools 4.5.0, 4.51.4.52. I also installed the GNU WiN make, rm , cp etc utilities in order to run

    the make script from the cmd line.

     I had to change the  ProjectDir="S:\DM355EVM\DM35x_FlashAndBootUtils_1_50\DM35x\CCS\NANDWriter\"  and

    Options=--abi=ti_arm9_abi in \NANDWriter.pjt to compile without errors.

     When I select either of the above CG tools in the CCS component manger I get the following link error in the nandwritter directory. When

    I used the original CG tools I got more link errors.

     

     

    [Linking...] "C:\Program Files\Texas Instruments\TMS470 Code Generation Tools 4.
    5.0\bin\cl470" -@"Debug.lkf"
    <Linking>

     undefined           first referenced

      symbol                 in file

     ---------           ----------------

     _EMIFStart          S:\\DM355EVM\\DM35x_FlashAndBootUtils_1_50\\DM35x\\CCS\\NAN
    DWriter\\Debug\\nandwriter.obj
     _EXTERNAL_RAM_END   S:\\DM355EVM\\DM35x_FlashAndBootUtils_1_50\\DM35x\\CCS\\NAN
    DWriter\\Debug\\util.obj
     _EXTERNAL_RAM_START S:\\DM355EVM\\DM35x_FlashAndBootUtils_1_50\\DM35x\\CCS\\NAN
    DWriter\\Debug\\util.obj

    error: unresolved symbols remain
    error: errors encountered during linking; "./Debug/NANDWriter.out" not built

    >> Compilation failure

     

     I assume the DM355 is in the TMS470 family as far as the CCS tools is concerned. Any ideas ?

     

     

     Thanks,

     John

     

     

  • 0
    Intellectual 255 points

     I was able to compile the project by changing the gcc option  back to -abi=eabi, which is the default. The ProjectDIr setting in the CCS .pjt files didn't make any difference what they were set to. Using the later versions of the CG tools in CCS solved the problem, as the other post mentioned. I am using Code Sorcery's  arm-none-eabi tools on Windows. I also comented out the grep / sed line in the make file which didn't work under Windows GNU tools. This just printed out the boot loction from the map file.

    John