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.

LP5569: LP5569 EVM GUI gives syntax error on simple program

Part Number: LP5569

Hi,

I am trying to compile a simple program for the LP5569 using the LP5569 EVM GUI software (version 1.0.0). See below for a screenshot.

I don't understand why the compiler claims that my "wait 0.2" command is wrong. "0.2" is clearly within range of "0 to 0.484". I have tried several times, on both Windows 10 and Windows 7. I have tried writing the commands myself, and creating the program using the drop down menus under "Input Instruction". I have tried using a comma for the decimal separator. I have tried running the lasm.exe program from the command prompt directly, but I have had no luck.

Any help is greatly appreciated.

Best,

Fredrik

  • Hi, Fredrik,

    It's quite strange that I don't see this error using the same code.

    Please using the attached file and load it to compile to see if the error still exsits.

    https://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/196/LP5569_5F00_test.7z

    Please let me know if this solves your problem.

    Thanks.

    Regards,

    Kenneth

  • Hi Kenneth, thanks for getting back to me so quickly. Unfortunately. your example file did not compile either. I get the same syntax error on line 3.

    I noted that when I insert the "wait" command under "Input Instruction", the default decimal separator is a comma. I am in Norway, where we use commas as the decimal separator (but neither commas nor periods seem to work). Could there be a region-related bug in the compiler executable?

  • I found a solution. I think your GUI asks Windows for the default decimal separator, which in my case was the comma. The comma is coincidentally also the argument separator for asm commands.

    To solve this, open Control Panel > Region and click Additional settings. Change the Decimal symbol setting from "," to "." and restart the GUI. Everything works as expected now.

    You should probably update the GUI to always use the period for decimal separation, as this may not be an acceptable solution for everyone.