LMK05318: File not found when running script on TICS Pro

Hi Ishraq,

The script is working as expected, so the MATLAB runtime must be on the system path. Also, if you have write access to outfile.txt from the command prompt, the program should have the same access. To be honest, I'm not sure what's preventing your script from running in TICS Pro. I suspect it has something to do with the full installation of MATLAB and Windows permissions, but we don't have the logging facilities to capture the explicit error.

We can work around whatever limitation is preventing the script from running. Inconveniently, we cannot just import the romdump file after running the script ourselves. TICS Pro automatically renames the romdump file to romdump_old.txt to prevent junk data from being loaded in case the script fails to run (you have already encountered this behavior). However, we can trick TICS Pro into using the old romdump file by preventing romdump.txt from being renamed.

First, a procedure which assumes you have authority to set file permissions for your computer (reference from this article for permissions procedure, may be helpful for image references):

1. Configure everything in the TICS Pro GUI how you desire, then click the run script button.
2. If you still see a problem where romdump.txt cannot be found, repeat the process outlined above with the command prompt, with one modification: instead of ./outfile.txt as the final argument, use ./romdump.txt. You could also rename the generated outfile.txt to romdump.txt.
3. Create an empty file in the LMK05318 directory called romdump_old.txt.
4. Right click on romdump.txt, select properties.
5. On the security tab, click "advanced" to located advanced permissions.
6. Click disable inheritance button, and when prompted convert inherited permissions to explicit permissions
7. On the permissions page, add a new permission with the add button.
8. Click "Select a principal" and set the object name to "Everyone" (no quotes)
9. Change the permission type to "Deny"
10. Show advanced permissions, and deny deletion, read permissions, change permissions, and taking ownership.
11. "OK" through all the submenus.
12. In TICS Pro, run the script again. TICS Pro should fail to rename romdump.txt or delete romdump_old.txt, and will continue using romdump.txt generated externally.
13. If the script needs to be regenerated, delete romdump.txt, and repeat steps 1,2,12.

If you don't have the ability to set permissions for your files, or if you are (perhaps rightly) concerned about the side effects of creating a file which cannot be deleted without permissions modification, you will need an alternate solution that is more timing-sensitive:

1. Configure everything in the TICS Pro GUI how you desire, then click the run script button.
2. If you still see a problem where romdump.txt cannot be found, repeat the process outlined above with the command prompt, with one modification: instead of ./outfile.txt as the final argument, use ./romdump.txt. You could also rename the generated outfile.txt to romdump.txt.
3. Open some kind of interactive programming environment (e.g. a python shell), and create an open file pointer to romdump.txt. A python example:
   

   import os
   os.chdir("C:\\ProgramData\\Texas Instruments\\TICS Pro\\Configurations\\Devices\\Network Synchronizer Clock (Digital PLLs)\\LMK05318\\")
   f = open('romdump.txt')

4. In the python interpreter, queue the command f.close() but do not execute it yet. Be prepared to switch focus back to the python interpreter.
5. Run the script in TICS Pro again. Part of the script execution should open a command prompt. The moment that new command prompt appears (should be immediately after clicking "OK" to the "Run the script?" prompt), execute the python interpreter command to close the file pointer.
6. romdump.txt should not be deleted or renamed, and the script should proceed as normal. 

Regards,