Changes between Version 46 and Version 47 of Docs/825gen2/Dev/UpdatingLegacyApps

Timestamp:

09/19/24 09:45:07 (8 weeks ago)

Author:

Don Wilson

Comment:

--

Docs/825gen2/Dev/UpdatingLegacyApps

@@ -29 +29 @@
 21. A few source code changes may be needed for proper operation on the 825 Gen2. If the app has USB import/export features it may use a fixed path "/mnt/fl1" for the USB drive. The USB drive path will not be the same on the 825 Gen2. Search the project for the string "/mnt/fl1" to find any code that should be changed. The library lib825ev has a function called [wiki:Docs/Prog/Manual/ApplicationLibraries/lib825ev/File/FindFlashDrive FindFlashDrive] for the 825 Gen2 to get the path string. The path may be similar to "/run/media/sda1" but it is best to use the !FindFlashDrive function instead of a hard coded path.
 
-22. Also (probably rare) if the app communicates with another system by serial port or network that interprets the message payloads as binary integers, floats, etc... it may be necessary to make changes to account for different endianness. The 825 Gen2 is ARM-64 little-endian, The Legacy 825 is Coldfire big-endian.
+22. Also (probably rare) if the app communicates with another system by serial port, network, or file import/export that interprets the data content as binary integers, floats, etc... it may be necessary to make changes to account for different [https://en.wikipedia.org/wiki/Endianness endianness]. The 825 Gen2 is ARM-64 little-endian, The Legacy 825 is Coldfire big-endian. 
 
 Creating a simulator build configuration is also useful. Refer to [wiki:Simulating825gen2 Simulating 825 Gen2 Apps] for information about setting up a simulator build configuration.