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

Error during creation of image file when running the OMAPL137_AM17X _SAMPLE

Franz Frisch
Prodigy 185 points
Other Parts Discussed in Thread: OMAP-L137

Hi,

I'm trying to build a WinCe6 image for the OMAP-L137 EVM running the  OMAPL137_AM17X_SAMPLE.sln example delivered in the BSP_WINCE_ARM9_01_10_00 package.

Currently no image is created by VS2005 because of the following error message in file

build.err:

*************************************************************************************************************

PREROMIMAGE processing...

makeimg: run command: romimage C:\WINCE600\OSDesigns\OMAPL137_AM17X_SAMPLE\OMAPL137_AM17X_SAMPLE\RelDir\OMAPL137_AM17X_ARMV4I_Release\ce.bib

Windows CE ROM Image Builder v4.0.120 Copyright (c) Microsoft Corporation
Built: Jul 25 2006 16:37:02

Q flag encountered, adding module k.fatutil.dll
Q flag encountered, adding module k.toolhelp.dll
Q flag encountered, adding module k.ceddk.dll
Q flag encountered, adding module k.ws2.dll
Q flag encountered, adding module k.wspm.dll
Q flag encountered, adding module k.nspm.dll
Q flag encountered, adding module k.ssllsp.dll
Q flag encountered, adding module k.schannel.dll
Q flag encountered, adding module k.dhcpsrv.dll
Q flag encountered, adding module k.mmtimer.dll
Q flag encountered, adding module k.secur32.dll
Q flag encountered, adding module k.msasn1.dll
Q flag encountered, adding module k.crypt32.dll
Q flag encountered, adding module k.winsock.dll
Q flag encountered, adding module k.spnego.dll
Error: Could not find file 'C:\WINCE600\OSDesigns\OMAPL137_AM17X_SAMPLE\OMAPL137_AM17X_SAMPLE\RelDir\OMAPL137_AM17X_ARMV4I_Release\pru_suart_emu.fw' on disk
pru_suart_emu.fw C:\WINCE600\OSDesigns\OMAPL137_AM17X_SAMPLE\OMAPL137_AM17X_SAMPLE\RelDir\OMAPL137_AM17X_ARMV4I_Release\pru_suart_emu.fw NK

Error: failed setting line
makeimg: FATAL ERROR: Command returned non-zero exit code 1 (dec).
makeimg: FATAL ERROR: Command returned non-zero exit code 1 (dec).

*****************************************************************************************************************************************

As far as I understand the file 'pru_suart_emu.fw' cannot be found in the mentioned directory, but why ? I took a look into that directory and indeed the file is missing.

I already tried to remove 'PRU_Software_Uart' component in the catalog view of VS2005 but this resulted in a long list of warnings, which l finally respected and did not change this setting.

Furthermore I found the following chapter in http://processors.wiki.ti.com/index.php/ARM9_WinCE_BSP_User_Guide  : where there is something written about this PRU stuff:

Registry Entries

There is one group of registry entries for the PRU driver and another four sets of registry entries, one for each Soft UART. These are all defined in:

…\<BSPFolder>\FILES\platform.reg

The PRU driver registry entries are as follows.

[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\PRU]

but I do not fully understand what this means and what I can do to solve my problem...

I tried to run the platform.reg file but this did not work.

I have to say that until now I have not installed the CCS tool, but only the WinCE development tools and the BSP_WINCE_ARM9_01_10_00.

I'd appreciate very much any hints for solving my problem !

With kind regards,

Franz

 

  • 0
    TI__Intellectual 1640 points

    Franz,

    You can find a work around for the issue which is being tracked as SDOCM00082755 here.

    As mentioned in the release notes, the latest issues are being tracked in the above link.

    Regards,

    WM

     

  • 0 in reply to WMK
    Prodigy 185 points

    Thank you very much WMK for your quick response !

    I've tried the workaround which is suggested in SDOCM00082755 and changed the file platform.bib , starting on from line 256 according to the following picture :

    Afterwards I made a clean build followed by a complete rebuild of the OS .

    Result: The same error occured again :-(

    Then I thought about this change and I think it is not suitable to fix the problem because in the original file ( here on the left side of above picture ) the FW-file of the PRU is already unconditionally included, whereas after the fix it is included only if "PRU-Support item"  is checked in the catalog item view of VS2005 ( and this is the case with the OMAPL127_example ).

    Conclusion:

    The problem cannot be solved using the workaroud shown in SDOCM00082755 !

    Anyway, I'm looking forward to hear from you and try other possible solution(s).

    With kind regards,

    Franz

     

  • 0 in reply to Franz Frisch
    TI__Intellectual 1640 points

    Franz,

    Please create an empty directory "bin" in C:\WINCE600\PLATFORM\OMAPL137_AM17X\SRC\DRIVERS\PRU\firmware and rebuild (should not need to clean build).

    Let us know if this helps.

    Thanks

    WM

  • 0 in reply to WMK
    Prodigy 185 points

    Hi WMK,

    thank you very much for your help.

    This time it worked !

    NK.bin has been created now !

    This is a great forum here.

    Best regards,

    Franz