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

OMAP-L138: AISgen_d800k008.exe command line vs GUI

Philippe Racine
Prodigy 40 points

Part Number: OMAP-L138
Other Parts Discussed in Thread: OMAP-L137

Hi, I am using AISgen to convert .out file to .bin for a long time. I found out we can use AISgen_d800k008.exe in command line using the -cfg="".

I made a batch file and I succeeded to generate a .bin file by command line.

But when I tried to download my .bin to my OMAP-L138, it was not working.

First, I suspected my .cfg to be different, but no. What I did in my last test is this : In my .bat file, I start AISgen_d800k008.exe without any parameters, so the AISgen GUI appears. I load my .cfg file manually, I click the Generate AIS button, the size of the written file is 239428. I close everything. I launch the AISgen_d800k008.exe by the shortcut on the desktop, I load the same .cfg file, I click the Generate AIS button, the size of the written file is 240984. It is a 1556 bytes difference.

The bigger .bin works, the smaller does not work when downloaded.

If I compare both .bin files the difference is a block of bytes beginning at line 48. The beginning and the end are the same.

The only difference in my last test, is the launch of the AISgen_d800k008.exe, one is done by a .bat file, the other is by clicking a shortcut. It is the same .exe, the same .cfg in the same folder.

Does anyone know how I can get the same result by command line as using the GUI ?

Thank you

C:\flasher\flash.bin

  • 0
    TI__Guru**** 161600 points
    Hi,

    Have a look at these two threads:
    e2e.ti.com/.../93888
    e2e.ti.com/.../179796
    Both of them show examples how to use the AISgen tool from command line.

    Best Regards,
    Yordan
  • 0
    Guru 26430 points
    AISgen is graphical wrapper to the console program HexAIS. AISGen produces an INI file and command line for HexAIS. The command line is logged out to a TXT file. All these files are in the install directory. You could use HexAIS directly instead of AISgen. Basic command line is:

    HexAIS_OMAP-L138.exe -ini AISgen.ini -o output_ais.bin

    Add other commmmand line options from the AISgen log file.

    It will be interesting which method produces identical bin files. In theory, they should all be the same.
  • 0 in reply to Norman Wong
    Prodigy 40 points

    Very interesting, here are my AIGgen_log.txt

    Here is the one when call by .bat

    ***Loaded configuration from file C:\Users\Patricia\Desktop\Root\Util\GenereLDZ\Debug\GenereLDZ.cfg
Begining the AIS file generation.
AIS file being generated for bootmode: NONE.
ERROR: Not a valid object file.
Parsing the input object file, C:\Users\Patricia\Desktop\Root\MultiDetek2 DSP\DSP - MultiNG\Debug\DSP - MultiNG.out.
AIS file generation was successful.
***Wrote 239460 bytes to file C:\Users\Patricia\Desktop\Root\Util\GenereLDZ\Debug\imageMD2_2_04.bin

    Here is the one when AISgen is open by mouse clicking

    ***Loaded configuration from file C:\Users\Patricia\Desktop\Root\Util\GenereLDZ\Debug\GenereLDZ.cfg
Begining the AIS file generation.
AIS file being generated for bootmode: NONE.
Parsing the input object file, C:\ti\SYSBIOSv4\Labs\Lab12b_ARM_Boot\OMAPL138-ARM_BOOT_REV1_Silicon.out.
Parsing the input object file, C:\Users\Patricia\Desktop\Root\MultiDetek2 DSP\DSP - MultiNG\Debug\DSP - MultiNG.out.
AIS file generation was successful.
***Wrote 241016 bytes to file C:\Users\Patricia\Desktop\Root\Util\GenereLDZ\Debug\imageMD2_2_04.bin

    The difference in size is because OMAPL138-ARM_BOOT_REV1_Silicon.out is not parse...

    As I am using the same .cfg, I guess the graphical wrapper do something that make the first input object file valid.

    I tried to change my regional settings in Windows to English(United States), just to be sure the ";" was for a list separator. No difference (I did not reboot my computer though...)

    Then I wanted to try HexAIS_OMAP-L138.exe directly, but I don't find any .ini where the logged out .txt  file is...

    I search on my C:\ for any *.ini modified today, and nothing relevant comes out...

    I found 4 .ini files in the AISgen installation folder, but I rename the folder containing them and the AISgen still work like before. It tells me, those files are not use by AISgen.

    Next step will be to build my own .ini file I guess.

    Regards

  • 0 in reply to Philippe Racine
    Prodigy 40 points
    Knowing that my problem was an input file not parse, I tried to shorten the path of my input file.

    And now it work!

    So, my conclusion is with the same .cfg (so the same paths) the GUI and the command line act different. But with short paths, you will see no difference.

    Thank for everyone
  • 0 in reply to Philippe Racine
    Guru 26430 points
    I am surprised that length of the path is a problem. It is not that long. Usually it is the spaces in the path that cause problems. You have to double quote the entire path if there is a space in the path name.

    AISgen should generate an ini file in the AISgen install directory every time you generate a bin file. At least it is on my ancient WinXP machine. On newer Windows, the install directory is usually not writable by a normal user. Hopefully AISgen is written to put files in the user data areas. I vaguely remember you have AISgen cannot be installed in the "Program Files" directory for this reason.
  • 0 in reply to Norman Wong
    Prodigy 40 points
    I totally agree with you! I am flabbergasted by the situation.

    The path without space got a error, but the path with spaces works all the time. I tried to add double quote in the .cfg file but I got "***One or more parameter error must be corrected.".

    I have win7, maybe this is why I don't have the .ini file. Because an AIGgen_log.txt is generated every time a .bin is generated, so I see no reason why the .ini could not be generated at the same time. Just to go further, I try to put the AISgen.exe in admistrator and run in WinXP compatibility, no change.

    For now, I will keep the path short without space, should not be a big trouble with what I want to do.

    Thank you very much !
  • 0 in reply to Philippe Racine
    Guru 26430 points
    Looks like my memory is bad. It has been a few years since I worked on these devices. I gave you the wrong info. I checked my AISGEN installation and found that AISGEN is different for each platform.
    OMAP-L137 - AISGEN(v0.8.2.0) is a wrapper for HexAIS, will generate ini files.
    OMAP-L138 - AISGEN(v1.9) appears to be a standalone executable, will not generate ini files.
    Sorry about that.

    My usage of L138 ASIGEN uses a pathname of 84 characters with no spaces. This was using the command line. Appears to work. Same file for GUI and command line.

    The real complaint is that AISGEN does not seem to report errors. It dumps them into the log file.