• State
  • Locked Locked
  • Replies 6 replies
  • Subscribers 31 subscribers
  • Views 989 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.

sflash utility freezes with about 233Kb left to program, using uart 0 ROM_UpdateUart() call.

Randall Miner
Intellectual 505 points
Other Parts Discussed in Thread: TM4C1292NCPDT, UNIFLASH, TM4C1294NCPDT

Hello,

I want to find out if anyone else has encountered this issue and knows a solution.

Using a launchpad kit TM4C1294 (TM4C1292NCPDT processor), I have an application built using ccs which sets up uart0 at 115200bps and then invokes the ROM bootloader call ROM_UpdateUART().   The sflash utility partially programs the flash as evidenced by the downcounting "Remaining Bytes:" count but it freezes at 233560.     The application being downloaded is known good as it was previously testing in the same target using ccs (prints hello world on uart 0).

sflash is being called as follows:   sflash.exe -c 8 -d -p 0x00 -r 0x3ab85 helloworld.bin

where 0x3ab85 is the same address as the reset vector, the execution point right before main().

I have not been able to get LM Flash Programmer to run due to what is possibly a DLL issue (error message - application unable to start correctly 0xc000007b).

When the above sflash freeze occurs, I have to take the board to another engineer who does have LM Flash working, so that the jtag reset can be done, otherwise neigher ccs, uniflash or sflash can connect to the board with in infamous "clock" error msg.

I am running this on a Lenovo 64bit windows 7 laptop.   USB cable is the physical transport for the virtual stellaris com port).

There is no error message I can post because like I said above, sflash just freezes.

Any ideas?

  • 0
    TI__Guru**** 244400 points
    Hello Randall,

    The important thing is that LM Flash Programmer must work. The dll used by the LM FLash Programmer is also used in the sflash application as well. Did you try the same on the working system?

    The next point is that TM4C129 Connected LaunchPad has TM4C1294NCPDT uC and not TM4C1292NCPDT. So I am inclined to ask if this is a custom implementation?

    Regards
    Amit
  • 0 in reply to Amit Ashara
    Intellectual 505 points

    Hi Amit,

    Thanks for the quick reply.  I am wrong about which uC my launchpad has, I take your word for it.  No its not custom at all.

    On the subject of the LM programmer, I was assuming its a missing or wrong DLL because when searching on the internet for the windows error I get, the postings indicated that a DLL issue is usually the cause.  Also I have a tool called "depends" which lists dependencies of an executable and when I ran this tool on lmflash.exe, it reported two DLLs missing.   The tool is obviously wrong since you say sflash.exe requires the same DLLs as LM Programmer because my sflash.exe runs fine.

    The good news is that at least for my sflash issue, I have a resolution.   In parallel to posting here, I emailed our TI FAE, Mark Swanson.  He told me of an issue with bootloading from uarts where if the default packet size of 8 were used, the same issue I hit, would occur.  Mark recommened I add the parameters -d 60 to my sflash.exe command line to set the packet size at 60 bytes.   It worked beautifully.

    I'd still like to get LM Flash Programmer to work.   It works on my engineering manager's machine.  I have the same version he does, the latest.  I've uninstalled and reinstalled.   It just won't run on my machine.  Again the error message is:  LMFLASH.exe Application Error  "The application was unable to start correctly (0xC000007b). Click OK to close the application".

    My machine is Lenovo W540 thinkpad, Windows 7 professional service pack 1, 64 bit, 16Gb ram, Intel i7-4600.

  • 0 in reply to Randall Miner
    TI__Guru**** 244400 points
    Hello Randall

    Which dll is missing? Is that also reported by the tool?

    Regards
    Amit
  • 0 in reply to Amit Ashara
    Intellectual 505 points

    According to the Dependency Walker tool, it says GPSVC.DLL and IESHIMS.DLL cannot be found.  This is my first time using dependency walker so I cannot say how reliable it is.  

  • 0 in reply to Randall Miner
    TI__Guru**** 244400 points
    Hello Randall.

    The walker tool seems to be used quite often.

    IESHIMS.dll is for Internet explorer.
    GPSVC.dll is a system dll and frankly I am not too sure.

    The possible solution is to run a repair in windows to fix the missing dlls.

    Regards
    Amit