Part Number: UNIFLASH
Tool/software:
Hello,
I created a session file for AM263x EVM using the Start button in 'Detected Devices':
I committed the session file to version control for use by my colleagues.
However, when they attempt to use the session file the following error appears:
The cause is because my device serial number was embedded in the committed session file. When my colleagues attempt to use it with their EVM boards, the serial number is different and triggers the above behaviour. If they edit the .uniflash file and change the embedded serial number to match their EVM, the problem is not present.
A session file created using New Configuration does not suffer the same because it is agnostic of serial number.
<Q>
- Is it intentional that a session file created in this way only works with one EVM sample? I can't imagine why this is useful.
- Please can you pretty print the session file? Removing the whitespace saves only about 3kb (25%) and just makes debugging a problem like this more difficult.
Thank you.
