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

Timestamp:

11/19/25 12:32:47 (2 days ago)

Author:

Don Wilson

Comment:

--

Docs/825gen2/Dev/UpdatingLegacyApps

@@ -102 +102 @@
 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)
+== Debugging ==
+
+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>
@@ -120 +120 @@
 }}}
 
-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. 
+== Installation Package ==
+
+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