Changes between Version 146 and Version 147 of Docs/825gen2/Dev/UpdatingLegacyApps

Timestamp:

11/19/25 12:28:50 (2 days ago)

Author:

Don Wilson

Comment:

--

Docs/825gen2/Dev/UpdatingLegacyApps

@@ -1 +1 @@
 = Updating Legacy 825 Apps to run on 825 Gen2 =
+
+== Project Changes ==
 
 1. Run the new 825 development environment VM (Virtual Machine). Open the Eclipse IDE (Integrated Development Environment).
@@ -55 +57 @@
 [[Image(825gen2_buildsignature.png)]]
 
-23. 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.
-
-24. Some apps may use a fixed outdated file path "/dev/com3" for COM3 serial communications. This should be updated to use the CCommSerial class. For example:
+== Source Code Changes == 
+
+A few source code changes may be needed for proper operation on the 825 Gen2. 
+
+1. 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.
+
+2. Some apps may use a fixed outdated file path "/dev/com3" for COM3 serial communications. This should be updated to use the CCommSerial class. For example:
    {{{#!c++
 CFile file;
@@ -75 +81 @@
 }}}
 
-25. The 825 Gen2 defaults to 12 hour time which requires AM/PM labels to show the date/time. Legacy 825 indicators defaulted to 24 hour time. Many legacy apps do not allow for enough space to display the AM/PM labels. So slight modification of the date/time display code may be needed to accommodate 12 hour time.
+3. The 825 Gen2 defaults to 12 hour time which requires AM/PM labels to show the date/time. Legacy 825 indicators defaulted to 24 hour time. Many legacy apps do not allow for enough space to display the AM/PM labels. So slight modification of the date/time display code may be needed to accommodate 12 hour time.
 {{{#!c++
 void ShowDateTime(void)
@@ -94 +100 @@
 }}}
 
-26. 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. 
-
-27. Before running the app for debugging from SSH it will often be necessary to create a directory on the 825 Gen2 for the app's data. Check the app header files to confirm the directory the app will use for configuration and data files. (The last part of the directory should normally match the project name and the release build executable name. Some newer apps may automatically check when starting up and create the directory if it does not exist)
+4. 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. 
+
+== Debugging / Installation Package ==
+
+1. Before running the app for debugging from SSH it will often be necessary to create a directory on the 825 Gen2 for the app's data. Check the app header files to confirm the directory the app will use for configuration and data files. (The last part of the directory should normally match the project name and the release build executable name. Some newer apps may automatically check when starting up and create the directory if it does not exist)
 {{{
 mkdir /mnt/nand/apps/<projectname>
@@ -112 +120 @@
 }}}
 
-28. In the VM /srv/nfs/arm825/mnt/nand/apps/<projectname> directory it is helpful to create a script "mktgz.sh" to generate a release package to give to customers to install the app. 
+2. In the VM /srv/nfs/arm825/mnt/nand/apps/<projectname> directory it is helpful to create a script "mktgz.sh" to generate a release package to give to customers to install the app. 
 {{{
 #!/bin/sh