FMods.net - User contributions [en]

Hardware Info

2025-05-11T22:47:30Z

Admin:

<nowiki>== QNX tools ==</nowiki> 

<nowiki>======</nowiki> <code>pidin</code> ======
[https://openqnx.com/static/neutrino/utilities/p/pidin.html#id5 https://openqnx.com/static/neutrino/utilities/p/pidin.html]

Display information about the system:
<pre>
# pidin info
CPU:ARM Release:6.5.0 FreeMem:683Mb/2032Mb BootTime:Mar 19 17:35:42 UTC 2023
Processes: 139, Threads: 644
Processor1: 1093648626 Cortex A15 1000MHz FPU
Processor2: 1093648626 Cortex A15 1000MHz FPU
</pre>

====== <code>uname</code> ======
[https://openqnx.com/static/neutrino/utilities/u/uname.html#id7 https://openqnx.com/static/neutrino/utilities/u/uname.html]

Return the name of the operating system (POSIX):
<pre>
# uname -a
QNX localhost 6.5.0 2019/12/12-16:00:38CST TI-OMAP5432-Pasa-Ford-Sync3 armle
</pre>

== PASA (Panasonic) tools == 

====== <code>hwid</code> ======
<code>hwid</code> - Displays info about S3 board.

<code>hwid bt</code> - Info about BT stack.

Example output:<pre>
# hwid

MY=17
RADIO_TYPE=NAVI
NVRAM_SIZE=64GB
RAM_SIZE=2GB
DRVC=0
CPU_FREQ=1000
HW_REVISION=A
</pre>

Main Page

2025-05-11T22:46:23Z

Admin: /* Welcome to the FMods.net Ford Sync 3 Community Wiki! test */

== Welcome to the FMods.net Ford Sync 3 Community Wiki! == 
Welcome to our community-driven wiki dedicated to sharing technical information and resources related to Ford Sync 3. Whether you're a Ford vehicle owner, enthusiast, or technician, this wiki serves as a collaborative platform where members can share their expertise, tips, tricks, and troubleshooting guides for maximizing the functionality and performance of Ford's Sync 3 infotainment system.

[https://www.fmods.net/community/ucp.php?mode=register Join us] in exploring the latest features, updates, and hacks for Sync 3, and contribute your own knowledge to help fellow members make the most out of their Ford driving experience. Together, let's build a comprehensive [https://www.fmods.net/community/dlext/index database] of Sync 3 resources for the benefit of the entire Ford community!

== Content list == 
* [[Hardware Info]]
* [[Disk subsystem]]
* [[Graphics subsystem]]
* [[Logging subsystem]]
* [[USB subsystem]]
* [[Unpacking firmware]]
* [[Updating process]]
* [[Software Info]]
* [[Sync 3 Apps]]
* [[Sync 3 Mods]]
* [[Sync 3 Themes]]

Sync 3 Mods

2024-07-16T07:23:53Z

Admin:

'''General'''

To be able to install [https://www.fmods.net/community/dlext/index?cat=1 any Sync 3 Mods,] your Sync 3 system has to be jailbroken first!

To do this, download and apply the following [https://www.fmods.net/community/dlext/index?cat=4 basic Mods] first in this order:

# [https://www.fmods.net/community/dlext/details?df_id=1 Sync 3 Jailbreak]
# [https://www.fmods.net/community/dlext/details?df_id=2 FMods Installer (Daemon)]
# [https://www.fmods.net/community/dlext/details?df_id=3 FMods Tools (ModsTools)]

There is a [https://www.fmods.net/community/viewtopic.php?t=190 guide on fmods.net] with additional info how to jailbreak your Sync 3 unit. Basically: download a mod, unzip it to the root of an exFAT formatted USB stick and put it in the USB port in your car. A special script will notice that the Mod is offered and it wil execute it. There is also a [https://www.fmods.net/community/viewtopic.php?t=2 guide how to install mods].

'''Mod (short for Modification)'''

A mod is essentially a customized alteration or improvement of a factory feature within the Sync 3 system. It requires direct modifications to the original OEM Sync 3 files to function correctly. Here are the key points to remember:

* Mods build upon existing Sync 3 features, enhancing or tweaking them to suit specific needs.
* They often rely on modifying proprietary OEM files, which may require expertise in reverse engineering or understanding the inner workings of the system.
* In most cases, mods are applied using patches to avoid infringing on FoMoCo copyrights. This can lead to some challenges: - Mod authors may need to update their patches with each new Ford Sync 3 system update, which can be cumbersome. - Cross-mod compatibility can be tricky to navigate, especially if multiple mods modify the same files.

Mods are divided into several categories in the [https://www.fmods.net/community/dlext/index fmods.net database]:

# [https://www.fmods.net/community/dlext/index?cat=4 Basic]
# [https://www.fmods.net/community/dlext/index?cat=5 New Features]
# [https://www.fmods.net/community/dlext/index?cat=6 Graphics]
# [https://www.fmods.net/community/dlext/index?cat=7 Utilities]
# [https://www.fmods.net/community/dlext/index?cat=8 Miscellaneous]
# [https://www.fmods.net/community/dlext/index?cat=9 Tools]

Just browse the categories and install the mods of your choice! Sometimes people make custom mods that are not suitable for the fmods.net database. They might be shared in the [https://www.fmods.net/community/index.php fmods.net forum] or shared through the [https://t.me/joinchat/B0B4axHE46E6AGPwr7u6LA fmods.net Telegram channel].

'''How are Mods structured and ... made?'''

Mods are shared in the fmods.net database using the .zip format. Inside you will find a structure which can/will contain several files / folders:

# README.txt or README.md: this is a text file which gives some basic info about the Mod. Always read it as it can help you install and use the mod.
# DONTINDX.msa: this is a file which tells SYNC3 not to index the USB stick but to apply it.
# SyncMyMod folder: this folder contains the contents of the mod.
# autoinstall.sh: this is a bash/shell file which contains the commands that are executed. It can be read using any texteditor. Only make changes if you know what you are doing! Most Mods authors use more advanced TextEditors like [https://notepad-plus-plus.org/downloads/ NotePad++] or (even better) free [https://code.visualstudio.com/download Microsoft Visual Studio Code] which has nice and free QML code helpers. Good to know: sh is ''a shorthand for "bash''", which is the standard shell command language used by Unix (and also for Sync 3).
# files: a folder containing several subfolders with specific filetypes:
# bin: this subfolder of files contains binary files, like used for the Video Player or Rear View Camera Mods.
# other: this subfolder of files can contain backup files/folders and new files/folders. Like qml files, images in the .png, .jpg or .gif filetype or other files.
# patch: this subfolder of files contains the master.patch file(s). Basically, this file is used to patch and change existing .qml-files. To generate a master.patch file, you will need to compare the original file with the modified one. A good tool to compare files and generate a master.patch is [https://winmerge.org/downloads/ Winmerge]. Ask for help in the FMods.net Telegram channel, if you want to help and need addional info to get started on this matter.
# shell: this subfolder of files contains other bash/shell files (.sh filetype). They can be added to the end of the Sync 3 startup_gf.sh file or called in another way (e.g. we made .sh files to delete Apps).

In general a Mod is made by an author that knows a bit of bash/shell to change the autoinstall.sh file, and also has a good knowledge about the language that is used to show the Sync 3 screens to us: [https://doc.qt.io/qt-5/qtqml-index.html Qt QML].

[[wikipedia:QML|QML or Qt Modelling Language]] is a user interface markup language, like HTML is for websites. Ford has made some own libraries that can be used/called inside the qml-pages (usually they are imported in the top of the qml file). Typically qml files do not have 1.000 lines of codes each, but they call other qml files, so Sync 3 has a modular system. If you want to understand a bit of QML, there is a good online [https://www.youtube.com/watch?v=JxyTkXLbcV4 YouTube Tutorial by KDAB]. Also good to know: the Sync 3 compressed Apps.img file contains over 36.000 files!

Mods authors generally use Unix, Linux or something like a virtual Ubuntu system (e.g. inside Oracle Virtual Box) to mount the Sync 3 Apps.img file, unpack it and copy the contents back to their primary operating system. Some authors just code on a computer and test in their cars, others have a special bench station which speeds up development. Of course there is a [https://www.fmods.net/community/viewtopic.php?t=275 guide how to unpack Sync 3 files].

'''Special Mod: canbus box'''

It is possible to add a so called CANbus Box to a duplicated OBD / GWM port of your vehicle to show additional technical information on Sync 3, like TPMS (tire pressure) and all kinds of other values. The piece of hardware can be made yourself. More info is in the [https://www.fmods.net/community/viewtopic.php?t=1195 canbus box guide].

'''Different Sync 3 for default ford-MY20, Lincoln and 10 inch Portrait and Landscape screens'''

Although the Sync3 system has a combined Apps.img package, you might notice that (once unpacked) there are different subfolders. Sync 3 knows 4 different screen setup types:

# The default folder contains (qml-)files for the ford-MY20 8 inch screen Theme.
# The +lincoln-MY20 subfolder contains (qml-)files for cars with a Lincoln 8 inch screen Theme.
# The +10inchP subfolder contains (qml-)files for cars with a 10 inch Portrait screen Theme (ford-10P-MY20).
# The +10inchL subfolder contains (qml-)files for cars with a 10 inch landscape screen Theme (lincoln-10L-MY20). Like a Lincoln Aviator.

Most mods are just made for the default 8 inch Sync 3 screens. But some are ported too for Lincoln, or the 10 inc screens. Generally they are not offered through the Fmods.net Mods database, but through the FMods.net Forum or the FMods Telegram channel.

Sync 3 Mods

2024-07-16T07:22:36Z

Admin:

'''General'''

To be able to install [https://www.fmods.net/community/dlext/index?cat=1 any Sync 3 Mods,] your Sync 3 system has to be jailbroken first!

To do this, download and apply the following [https://www.fmods.net/community/dlext/index?cat=4 basic Mods] first in this order:

# [https://www.fmods.net/community/dlext/details?df_id=1 Sync 3 Jailbreak]
# [https://www.fmods.net/community/dlext/details?df_id=2 FMods Installer (Daemon)]
# [https://www.fmods.net/community/dlext/details?df_id=3 FMods Tools (ModsTools)]

There is a [https://www.fmods.net/community/viewtopic.php?t=190 guide on fmods.net] with additional info how to jailbreak your Sync 3 unit. Basically: download a mod, unzip it to the root of an exFAT formatted USB stick and put it in the USB port in your car. A special script will notice that the Mod is offered and it wil execute it. There is also a [https://www.fmods.net/community/viewtopic.php?t=2 guide how to install mods].

'''Mod (short for Modification)'''

A mod is essentially a customized alteration or improvement of a factory feature within the Sync 3 system. It requires direct modifications to the original OEM Sync 3 files to function correctly. Here are the key points to remember:

* Mods build upon existing Sync 3 features, enhancing or tweaking them to suit specific needs.
* They often rely on modifying proprietary OEM files, which may require expertise in reverse engineering or understanding the inner workings of the system.
* In most cases, mods are applied using patches to avoid infringing on FoMoCo copyrights. This can lead to some challenges: - Mod authors may need to update their patches with each new Ford Sync 3 system update, which can be cumbersome. - Cross-mod compatibility can be tricky to navigate, especially if multiple mods modify the same files.

Mods are divided into several categories in the [https://www.fmods.net/community/dlext/index fmods.net database]:

# [https://www.fmods.net/community/dlext/index?cat=4 Basic]
# [https://www.fmods.net/community/dlext/index?cat=5 New Features]
# [https://www.fmods.net/community/dlext/index?cat=6 Graphics]
# [https://www.fmods.net/community/dlext/index?cat=7 Utilities]
# [https://www.fmods.net/community/dlext/index?cat=8 Miscellaneous]
# [https://www.fmods.net/community/dlext/index?cat=9 Tools]

Just browse the categories and install the mods of your choice! Sometimes people make custom mods that are not suitable for the fmods.net database. They might be shared in the [https://www.fmods.net/community/index.php fmods.net forum] or shared through the [https://t.me/joinchat/B0B4axHE46E6AGPwr7u6LA fmods.net Telegram channel].

'''How are Mods structured and ... made?'''

Mods are shared in the fmods.net database using the .zip format. Inside you will find a structure which can/will contain several files / folders:

# README.txt or README.md: this is a text file which gives some basic info about the Mod. Always read it as it can help you install and use the mod.
# DONTINDX.msa: this is a file which tells SYNC3 not to index the USB stick but to apply it.
# SyncMyMod folder: this folder contains the contents of the mod.
# autoinstall.sh: this is a bash/shell file which contains the commands that are executed. It can be read using any texteditor. Only make changes if you know what you are doing! Most Mods authors use more advanced TextEditors like [https://notepad-plus-plus.org/downloads/ NotePad++] or (even better) free [https://code.visualstudio.com/download Microsoft Visual Studio Code] which has nice and free QML code helpers. Good to know: sh is ''a shorthand for "bash''", which is the standard shell command language used by Unix (and also for Sync 3).
# files: a folder containing several subfolders with specific filetypes:
# bin: this subfolder of files contains binary files, like used for the Video Player or Rear View Camera Mods.
# other: this subfolder of files can contain backup files/folders and new files/folders. Like qml files, images in the .png, .jpg or .gif filetype or other files.
# patch: this subfolder of files contains the master.patch file(s). Basically, this file is used to patch and change existing .qml-files. To generate a master.patch file, you will need to compare the original file with the modified one. A good tool to compare files and generate a master.patch is [https://winmerge.org/downloads/ Winmerge]. Ask for help in the FMods.net Telegram channel, if you want to help and need addional info to get started on this matter.
# shell: this subfolder of files contains other bash/shell files (.sh filetype). They can be added to the end of the Sync 3 startup_gf.sh file or called in another way (e.g. we made .sh files to delete Apps).

In general a Mod is made by an author that knows a bit of bash/shell to change the autoinstall.sh file, and also has a good knowledge about the language that is used to show the Sync 3 screens to us: [https://doc.qt.io/qt-5/qtqml-index.html QuickTime QML].

[[wikipedia:QML|QML or Qt Modelling Language]] is a user interface markup language, like HTML is for websites. Ford has made some own libraries that can be used/called inside the qml-pages (usually they are imported in the top of the qml file). Typically qml files do not have 1.000 lines of codes each, but they call other qml files, so Sync 3 has a modular system. If you want to understand a bit of QML, there is a good online [https://www.youtube.com/watch?v=JxyTkXLbcV4 YouTube Tutorial by KDAB]. Also good to know: the Sync 3 compressed Apps.img file contains over 36.000 files!

Mods authors generally use Unix, Linux or something like a virtual Ubuntu system (e.g. inside Oracle Virtual Box) to mount the Sync 3 Apps.img file, unpack it and copy the contents back to their primary operating system. Some authors just code on a computer and test in their cars, others have a special bench station which speeds up development. Of course there is a [https://www.fmods.net/community/viewtopic.php?t=275 guide how to unpack Sync 3 files].

'''Special Mod: canbus box'''

It is possible to add a so called CANbus Box to a duplicated OBD / GWM port of your vehicle to show additional technical information on Sync 3, like TPMS (tire pressure) and all kinds of other values. The piece of hardware can be made yourself. More info is in the [https://www.fmods.net/community/viewtopic.php?t=1195 canbus box guide].

'''Different Sync 3 for default ford-MY20, Lincoln and 10 inch Portrait and Landscape screens'''

Although the Sync3 system has a combined Apps.img package, you might notice that (once unpacked) there are different subfolders. Sync 3 knows 4 different screen setup types:

# The default folder contains (qml-)files for the ford-MY20 8 inch screen Theme.
# The +lincoln-MY20 subfolder contains (qml-)files for cars with a Lincoln 8 inch screen Theme.
# The +10inchP subfolder contains (qml-)files for cars with a 10 inch Portrait screen Theme (ford-10P-MY20).
# The +10inchL subfolder contains (qml-)files for cars with a 10 inch landscape screen Theme (lincoln-10L-MY20). Like a Lincoln Aviator.

Most mods are just made for the default 8 inch Sync 3 screens. But some are ported too for Lincoln, or the 10 inc screens. Generally they are not offered through the Fmods.net Mods database, but through the FMods.net Forum or the FMods Telegram channel.

Software Info

2024-06-19T21:12:00Z

Admin:

The Sync 3 OS is based on QNX Neutrino 6.5, and it's built using several <code>QNX6 FS</code> images and each image has a specific package P/N.

* <code>[[14G381]]</code> (Main Sync 3 OS)
* <code>[[14G386 / 14G387]]</code> (Utilities packages)
* <code>[[14G391]]</code> (System Voices)
* <code>[[14G421]]</code> (Maps Data)
* <code>[[14G422]]</code> (Navigation Voices)
* <code>[[14G423]]</code> (Gracenotes database)
* <code>[[14G424]]</code> (Maps License)
* <code>[[14G658]]</code> (DAB Stations Logos)

All update packages (except few cases) contains a <code>QNX6 FS</code> .img file, which simply replace the previously available .img file.
For Main Sync 3 OS package is a bit different, because the .img is copied on the Sync 3, and extracted in a specific OS.

Main Page

2024-06-19T10:53:29Z

Admin:

Software Info

2024-06-19T10:51:25Z

Admin:

The Sync 3 OS is based on the QNX Neutrino 6.5, and it's built using several <code>QNX6 FS</code> images and each image has a specific package P/N.

* <code>[[14G381]]</code> (Main Sync 3 OS)
* <code>[[14G386 / 14G387]]</code> (Utilities packages)
* <code>[[14G391]]</code> (System Voices)
* <code>[[14G421]]</code> (Maps Data)
* <code>[[14G422]]</code> (Navigation Voices)
* <code>[[14G423]]</code> (Gracenotes database)
* <code>[[14G424]]</code> (Maps License)
* <code>[[14G658]]</code> (DAB Stations Logos)

All update packages (except few cases) contains a <code>QNX6 FS</code> .img file, which simply replace the previously available .img file.
For Main Sync 3 OS package is a bit different, because the .img is copied on the Sync 3, and extracted in a specific OS.

Software Info

2024-06-19T10:50:25Z

Admin:

The Sync 3 OS is based on the QNX Neutrino 6.5, and it's built using several <code>QNX6 FS</code> images and each image has a specific package P/N.

* <code>[[14G381]]</code> (Main Sync 3 OS)
* <code>[[14G386 / 14G387]]</code> (Utilities packages)
* <code>[[14G391]]</code> (System Voices)
* <code>[[14G421]]</code> (Maps Data)
* <code>[[14G422]]</code> (Navigation Voices)
* <code>[[14G423]]</code> (Gracenotes database)
* <code>[[14G424]]</code> (Maps License)
* <code>[[14G658]]</code> (DAB Station Logos)

All update packages (except few cases) contains a <code>QNX6 FS</code> .img file, which simply replace the previously available .img file.
For Main Sync 3 OS package is a bit different, because the .img is copied on the Sync 3, and extracted in a specific OS.

Software Info

2024-06-19T10:49:20Z

Admin:

The Sync 3 OS is based on the QNX Neutrino 6.5, and it's built using several <code>QNX6 FS images</code>, and each image has a specific package P/N.

* <code>[[14G381]]</code> (Main Sync 3 OS)
* <code>[[14G386 / 14G387]]</code> (Utilities packages)
* <code>[[14G391]]</code> (System Voices)
* <code>[[14G421]]</code> (Maps Data)
* <code>[[14G422]]</code> (Navigation Voices)
* <code>[[14G423]]</code> (Gracenotes database)
* <code>[[14G424]]</code> (Maps License)
* <code>[[14G658]]</code> (DAB Station Logos)

All update packages (except few cases) contains a <code>QNX6 FS</code> .img file, which simply replace the previously available .img file.
For Main Sync 3 OS package is a bit different, because the .img is copied on the Sync 3, and extracted in a specific OS.

Software Info

2024-06-19T10:47:47Z

Admin:

The Sync 3 OS is based on the QNX Neutrino 6.5, and it's built using several <code>QNX6 FS images</code>, and each image has a specific package P/N.

* <code>14G381</code> (Main Sync 3 OS)
* <code>14G386 / 14G387</code> (Utilities packages)
* <code>14G391</code> (System Voices)
* <code>14G421</code> (Maps Data)
* <code>14G422</code> (Navigation Voices)
* <code>14G423</code> (Gracenotes database)
* <code>14G424</code> (Maps License)
* <code>14G658</code> (DAB Station Logos)

All update packages (except few cases) contains a <code>QNX6 FS</code> .img file, which simply replace the previously available .img file.
For Main Sync 3 OS package is a bit different, because the .img is copied on the Sync 3, and extracted in a specific OS.

Main Page

2024-05-27T09:35:36Z

Admin:

== Welcome to the FMods.net Ford Sync 3 Community Wiki! == 
Welcome to our community-driven wiki dedicated to sharing technical information and resources related to Ford Sync 3. Whether you're a Ford vehicle owner, enthusiast, or technician, this wiki serves as a collaborative platform where members can share their expertise, tips, tricks, and troubleshooting guides for maximizing the functionality and performance of Ford's Sync 3 infotainment system.

[https://www.fmods.net/community/ucp.php?mode=register Join us] in exploring the latest features, updates, and hacks for Sync 3, and contribute your own knowledge to help fellow members make the most out of their Ford driving experience. Together, let's build a comprehensive repository of Sync 3 resources for the benefit of the entire Ford community!

== Content list == 
* [[Hardware_Info]]
* [[Disk subsystem]]
* [[Graphics subsystem]]
* [[Logging subsystem]]
* [[USB subsystem]]
* [[Unpacking firmware]]
* [[Updating process]]
* [[Software Info]]

Reformat package

2024-05-27T00:58:18Z

Admin: Created page with "To Do"

To Do

Software Info

2024-05-27T00:57:24Z

Admin: Created page with "To Do"

To Do

Main Page

2024-05-27T00:56:44Z

Admin:

== Welcome to the FMods.net Ford Sync 3 Community Wiki! == 
Welcome to our community-driven wiki dedicated to sharing technical information and resources related to Ford Sync 3. Whether you're a Ford vehicle owner, enthusiast, or technician, this wiki serves as a collaborative platform where members can share their expertise, tips, tricks, and troubleshooting guides for maximizing the functionality and performance of Ford's Sync 3 infotainment system.

Join us in exploring the latest features, updates, and hacks for Sync 3, and contribute your own knowledge to help fellow members make the most out of their Ford driving experience. Together, let's build a comprehensive repository of Sync 3 resources for the benefit of the entire Ford community!

== Content list == 
* [[Hardware_Info]]
* [[Disk subsystem]]
* [[Graphics subsystem]]
* [[Logging subsystem]]
* [[USB subsystem]]
* [[Unpacking firmware]]
* [[Updating process]]
* [[Software Info]]

Main Page

2024-05-27T00:54:07Z

Admin:

== Welcome to the Ford Sync 3 Community Wiki! == 
Welcome to our community-driven wiki dedicated to sharing technical information and resources related to Ford Sync 3. Whether you're a Ford vehicle owner, enthusiast, or technician, this wiki serves as a collaborative platform where members can share their expertise, tips, tricks, and troubleshooting guides for maximizing the functionality and performance of Ford's Sync 3 infotainment system.

Join us in exploring the latest features, updates, and hacks for Sync 3, and contribute your own knowledge to help fellow members make the most out of their Ford driving experience. Together, let's build a comprehensive repository of Sync 3 resources for the benefit of the entire Ford community!

== Content list == 
* [[Hardware_Info]]
* [[Disk subsystem]]
* [[Graphics subsystem]]
* [[Logging subsystem]]
* [[USB subsystem]]
* [[Unpacking firmware]]
* [[Updating process]]
* [[Software Info]]

MediaWiki:Mainpage

2024-05-27T00:53:05Z

Admin:

Main Page

MediaWiki:Mainpage

2024-05-27T00:52:44Z

Admin:

Main

MediaWiki:Mainpage

2024-05-27T00:52:07Z

Admin:

Main Page

FMods.net:General disclaimer

2024-05-27T00:44:34Z

Admin:

All information presented on this wiki is obtained through personal <code> SYNC 3 OS</code> research and is intended for entertainment purposes only. While we strive to provide accurate and up-to-date content, we make no representations or warranties of any kind, express or implied, about the completeness, accuracy, reliability, suitability, or availability with respect to the wiki or the information, products, services, or related graphics contained on the wiki for any purpose. Any reliance you place on such information is therefore strictly at your own risk.

By using this wiki, you acknowledge and agree that no one involved in the creation, production, or maintenance of this wiki is responsible or liable for any direct, indirect, incidental, consequential, or any other damages arising out of or in connection with your use of or inability to use this wiki or the information contained within it.

We reserve the right to make changes and updates to the information on this wiki without prior notice.

Please note that this website, and its members, are not affiliated with or represent <code>Ford Motor Company</code> in any way.

FMods.net:General disclaimer

2024-05-27T00:43:15Z

Admin:

All information presented on this wiki is obtained through personal SYNC 3 OS research and is intended for entertainment purposes only. While we strive to provide accurate and up-to-date content, we make no representations or warranties of any kind, express or implied, about the completeness, accuracy, reliability, suitability, or availability with respect to the wiki or the information, products, services, or related graphics contained on the wiki for any purpose. Any reliance you place on such information is therefore strictly at your own risk.

By using this wiki, you acknowledge and agree that no one involved in the creation, production, or maintenance of this wiki is responsible or liable for any direct, indirect, incidental, consequential, or any other damages arising out of or in connection with your use of or inability to use this wiki or the information contained within it.

We reserve the right to make changes and updates to the information on this wiki without prior notice.

Please note that this website, and its members, are not affiliated with or represent Ford Motor Company in any way.

FMods.net:General disclaimer

2024-05-27T00:38:04Z

Admin: Created page with "All information obtained during the Ford SYNC3 OS research and presented for entertainment purposes only. No one is responsible for the reliable of the information provided here. Use it at your own risk."

All information obtained during the Ford SYNC3 OS research and presented for entertainment purposes only.

No one is responsible for the reliable of the information provided here. Use it at your own risk.

Updating process

2024-05-27T00:34:46Z

Admin: Created page with "== Update process ==  === APP_SUM ===  <pre> /fs/mp/apps/APP_SUM /fs/mp/apps/usr/lib/libNS_ExtractVerifyCore.so </pre> === NS_ExtractVerify ===  {{#fas:circle-info}} Present only in reformat OS <pre> Usage: SS_HashSpeedTest <certificate File Path> <src file> <dst Dir Path> <Particular file name to be extracted [Optional]> </pre> Example: <pre> NS_ExtractVerify /fs/mp/usr/share/ford_prod_ca_certs.pem PU5T-14G386-BB_1690840002000.TAR.GZ ...."

== Update process == 
=== APP_SUM === 

<pre>
/fs/mp/apps/APP_SUM
/fs/mp/apps/usr/lib/libNS_ExtractVerifyCore.so
</pre>

=== NS_ExtractVerify === 
{{#fas:circle-info}} Present only in reformat OS
<pre>
Usage: SS_HashSpeedTest <certificate File Path> <src file> <dst Dir Path> <Particular file name to be extracted [Optional]>
</pre>

Example:
<pre>
NS_ExtractVerify /fs/mp/usr/share/ford_prod_ca_certs.pem PU5T-14G386-BB_1690840002000.TAR.GZ ./
</pre>

=== Certificates path === 
<pre>
/fs/mp/usr/share/FmcIVSUInternalProdPublicCerts.pem
/fs/mp/usr/share/ford_prod_ca_certs.pem
/fs/mp/usr/share/prod-sync-modenc-g3-a2.pem
/fs/mp/usr/share/www.cloud-sync.ford.com.pem
/fs/mp/etc/AppLink/prodappissuingcatls.pem
/fs/mp/etc/AppLink/prodapproottls.pem
</pre>

USB subsystem

2024-05-27T00:32:20Z

Admin:

== USB subsystem == 
=== usblauncher === 

<pre>
/fs/mp/etc/usblauncher/
├── iap2ea.lua
├── iap2.lua
├── iap2ncm.lua
├── netstart.sh
├── netstop.sh
├── override.lua
├── rules.lua
├── rules_otg.lua
├── startncm-molex.sh
├── startncm.sh
├── stopncm.sh
└── umass.lua
</pre>

Useful commands:
<code>usb -vvv -N /dev/otg/io-usb-otg</code>

== USB-LAN ethernet == 
List of supported NICs in <code>/fs/mp/etc/usblauncher/rules_otg.lua</code>

<pre>
nic_devices = {
device(0x0b95, 0x7720); -- CISCO linksys USB300M ethernet dongle
device(0x0b95, 0x772b); -- Insignia NS-PU98505 ethernet dongle
device(0x2001, 0x3c05); -- D-Link DUB-E100 (revB1) ethernet dongle
device(0x2001, 0x1a02); -- D-Link DUB-E100 (revC1) ethernet dongle
}

foreach (nic_devices) {
start"/fs/mp/etc/usblauncher/netstart.sh busnum=$(busno),devnum=$(devno),path=$(USB_PATH),ign_remove /fs/mp/lib/dll/devnp-asix.so";
removal"/fs/mp/etc/usblauncher/netstop.sh";
}
</pre>

Content of <code>/fs/mp/etc/usblauncher/netstart.sh</code>

<pre>
#!/bin/sh

IFACE=ax0
IPADDR=192.168.1.26
mount -T io-pkt -o $1 $2
ifconfig $IFACE $IPADDR netmask 255.255.255.0
echo "debug $IFACE done."
</pre>

{{#fas:circle-info}} To get a working usb network on "production" OS, copy <code>devnp-asix.so</code> from [[reformat package]] to <code>/fs/mp/lib/dll/devnp-asix.so</code>

<pre>
1. pidin ar | grep usblauncher_otg
2. usblauncher_otg -S1 -c /fs/mp/etc/usblauncher/rules_otg.lua -M /fs/mp/etc/mcd.mnt -s /fs/mp/lib/dll/pubs/ -n/dev/otg/io-usb-otg -vvvv -b -eErtl

/fs/mp/etc/usblauncher/netstart.sh busnum=0x01,devnum=0x2,path=/dev/otg/io-usb-otg,ign_remove /fs/mp/lib/dll/devnp-asix.so
</pre>

== USB-HID == 
Run USB HID server:

<pre>
io-hid -d devh-usb.so
</pre>

{{#fas:circle-info}} You should get <code>devh-usb.so</code> lib from QNX SDP.

<code>io-hid</code> usage:

<pre>
# use io-hid
io-hid - HID Server ( Human Interface Device )

Usage:
io-hid [options] &

Options:
-d dll [opts] Device DLL to load and options to pass to the DLL.
-n name Set server name. default "/dev/io-hid/io-hid"
-v Be verbose
-V Display server version

Examples:

USB HID devices, PS/2 mouse, Serial mouse on COM1 directly, PS/2 keyboard

io-hid -dusb -dps2ser ps2mouse:mousedev:msoft:uart,1:kbd:kbddev &
</pre>

{{#fas:circle-info}} After launch <code>io-hid</code> all HID events will be grabbed by libscreen.

Use <code>[https://openqnx.com/static/neutrino/utilities/h/hidview.html hidview]</code> tool for get info about connected HID devices.

USB subsystem

2024-05-27T00:30:45Z

Admin:

== USB subsystem == 
=== usblauncher === 

<pre>
/fs/mp/etc/usblauncher/
├── iap2ea.lua
├── iap2.lua
├── iap2ncm.lua
├── netstart.sh
├── netstop.sh
├── override.lua
├── rules.lua
├── rules_otg.lua
├── startncm-molex.sh
├── startncm.sh
├── stopncm.sh
└── umass.lua
</pre>

Useful commands:
<code>usb -vvv -N /dev/otg/io-usb-otg</code>

== USB-LAN ethernet == 
List of supported NICs in <code>/fs/mp/etc/usblauncher/rules_otg.lua</code>

<pre>
nic_devices = {
device(0x0b95, 0x7720); -- CISCO linksys USB300M ethernet dongle
device(0x0b95, 0x772b); -- Insignia NS-PU98505 ethernet dongle
device(0x2001, 0x3c05); -- D-Link DUB-E100 (revB1) ethernet dongle
device(0x2001, 0x1a02); -- D-Link DUB-E100 (revC1) ethernet dongle
}

foreach (nic_devices) {
start"/fs/mp/etc/usblauncher/netstart.sh busnum=$(busno),devnum=$(devno),path=$(USB_PATH),ign_remove /fs/mp/lib/dll/devnp-asix.so";
removal"/fs/mp/etc/usblauncher/netstop.sh";
}
</pre>

Content of <code>/fs/mp/etc/usblauncher/netstart.sh</code>

<pre>
#!/bin/sh

IFACE=ax0
IPADDR=192.168.1.26
mount -T io-pkt -o $1 $2
ifconfig $IFACE $IPADDR netmask 255.255.255.0
echo "debug $IFACE done."
</pre>

To get a working usb network on "production" OS, copy <code>devnp-asix.so</code> from [[reformat package]] to <code>/fs/mp/lib/dll/devnp-asix.so</code>

<pre>
1. pidin ar | grep usblauncher_otg
2. usblauncher_otg -S1 -c /fs/mp/etc/usblauncher/rules_otg.lua -M /fs/mp/etc/mcd.mnt -s /fs/mp/lib/dll/pubs/ -n/dev/otg/io-usb-otg -vvvv -b -eErtl

/fs/mp/etc/usblauncher/netstart.sh busnum=0x01,devnum=0x2,path=/dev/otg/io-usb-otg,ign_remove /fs/mp/lib/dll/devnp-asix.so
</pre>

== USB-HID == 
Run USB HID server:

<pre>
io-hid -d devh-usb.so
</pre>

You should get <code>devh-usb.so</code> lib from QNX SDP.

<code>io-hid</code> usage:

<pre>
# use io-hid
io-hid - HID Server ( Human Interface Device )

Usage:
io-hid [options] &

Options:
-d dll [opts] Device DLL to load and options to pass to the DLL.
-n name Set server name. default "/dev/io-hid/io-hid"
-v Be verbose
-V Display server version

Examples:

USB HID devices, PS/2 mouse, Serial mouse on COM1 directly, PS/2 keyboard

io-hid -dusb -dps2ser ps2mouse:mousedev:msoft:uart,1:kbd:kbddev &
</pre>

{{#fas:circle-info}} After launch <code>io-hid</code> all HID events will be grabbed by libscreen.

Use <code>[https://openqnx.com/static/neutrino/utilities/h/hidview.html hidview]</code> tool for get info about connected HID devices.

Logging subsystem

2024-05-27T00:24:13Z

Admin:

== QNX system logs == 

<code>/bin/sloginfo</code> - [https://openqnx.com/static/neutrino/utilities/s/sloginfo.html print system log]

<code>/proc/boot/slogger</code> - [https://openqnx.com/static/neutrino/utilities/s/slogger.html system logger]

== PASA (Panasonic) tools == 

=== nslogutil === 

<code>/fs/mp/apps/usr/sbin/nslogutil</code>
<pre>
Help: nslogutil -q QUEUENAME [-m MASKVALUE(hex)] | [-l "slogger|msgq|console"] [-p "log message"] [-s severity] [-g "mask|outopt|severity"] [-t "rxontxoff, rxofftxon, rxontxon, rxofftxoff"] [-d Debug Dump Request]
</pre>

Examples:
<code>nslogutil -q IPC_MID -l "slogger" -m 0xefffffff</code>
<code>nslogutil -q IPC_MID -m 0xFFFFFF -t rxontxon -s 1</code>

=== CustomCommandLineOption() === 
Sync 3 common cmdline options (<code>CustomCommandLineOption()</code>)

<pre>
optstr: "l:m:t:c:p:qr:s"

-l (log output option)
Allowed values: "slogger", "console", "shmem" (And always to fs/rwdata/fordlogs/)
This vales may be combined with '|' Ex: -l "slogger|console"

-m (mask value) This log level masks(Up to 16 masks). Each mask represent certain subsystem.
Ex: -m "0xFFFFFFFF,0xFFFFFFFF,0xFFFFFFFF,0xFFFFFFFF"

-r [plog output option (byte)] Enable PLOG
-s Enable sys event log
-q queue name <%s>
-p (set priority) <??? %s>
-c (set config file) <filepath %s>
-t (set transmit logging) <??? %s>
</pre>

== Log paths == 
Please keep in mind that this list contains only logs enabled by default on the system.

<pre>
/fs/rwdata/fordlogs/pas_debug.log
/fs/rwdata/fordlogs/BTLogs/NET_BT_Service.log
/fs/rwdata/logs/sys_error.log.0
/fs/rwdata/logs/96.bmetrics_data.log
/fs/rwdata/logs/96.ns_perf.log
/fs/rwdata/slogs/96.slog
/fs/rwdata/logs/sys_slog_info
/fs/rwdata/NAV/gnss/96-MSL_Log.txt
/fs/rwdata/NAV/gnss/96-CL_Log.txt
/fs/rwdata/NAV/unifiedsearch.log
/fs/rwdata/BEZEL_DIAGNOSTICS_LOG.txt
/fs/mp/NAV/Job2/resource/config/log.xml
/fs/mp/etc/AppLink/log4cxx.debug.properties
/fs/mp/etc/AppLink/log4cxx.properties
/fs/mp/etc/BT_HCILogSize.cfg
/fs/mp/etc/firmware/NS_SLog_config.cfg
/fs/mp/diagnostics/etc/quip/log_silver_config
/fs/mp/diagnostics/scripts/filter-btlog.sed
/fs/mp/diagnostics/scripts/filter-nuancelog.sed
/fs/mp/diagnostics/scripts/filter-osapilog.sed
/fs/mp/diagnostics/scripts/filter-slog.sed
/fs/mp/diagnostics/scripts/quip-log-silver.sh
/fs/images/ivsu_cache/Encoded_Interrogator_Log.xml
/dev/shmem/fts_log1.tmp
/dev/shmem/osapi.log
/dev/shmem/animamtion.log
/dev/shmem/NavMiniApplog.txt
/dev/shmem/NavAccellog.txt
</pre>

== Other == 
<pre>
/usr/sbin/tracelogger
/apps/NS_PasLogCapture
/fs/mp/apps/RCN_DiagnosticsLog
/fs/mp/apps/SS_SLogMonitor
/fs/mp/apps/VCA_Logger_Enable

/proc/boot/libPlog.so.1
/fs/mp/apps/usr/lib/libArtLog.so
/fs/mp/apps/usr/lib/liblog4cxx.so.10
/fs/mp/apps/usr/lib/libNS_Logger.so
/fs/mp/apps/usr/lib/libresource_logger.so
/fs/mp/usr/lib/liblogging.so.1
/fs/mp/NAV/libclientlogger.so
/fs/mp/NAV/libNAV_TI_Log.so

/fs/mp/qt5/qml/QtTest/testlogger.js
/fs/mp/fordhmi/test/alsim_loglevelset
/fs/mp/fordhmi/test/HmiLogScript.sh
</pre>

USB subsystem

2024-05-27T00:23:20Z

Admin: /* USB-HID */

== USB subsystem == 
=== usblauncher === 

<pre>
/fs/mp/etc/usblauncher/
├── iap2ea.lua
├── iap2.lua
├── iap2ncm.lua
├── netstart.sh
├── netstop.sh
├── override.lua
├── rules.lua
├── rules_otg.lua
├── startncm-molex.sh
├── startncm.sh
├── stopncm.sh
└── umass.lua
</pre>

Useful commands:
<code>usb -vvv -N /dev/otg/io-usb-otg</code>

== USB-LAN ethernet == 
List of supported NICs in <code>/fs/mp/etc/usblauncher/rules_otg.lua</code>

<pre>
nic_devices = {
device(0x0b95, 0x7720); -- CISCO linksys USB300M ethernet dongle
device(0x0b95, 0x772b); -- Insignia NS-PU98505 ethernet dongle
device(0x2001, 0x3c05); -- D-Link DUB-E100 (revB1) ethernet dongle
device(0x2001, 0x1a02); -- D-Link DUB-E100 (revC1) ethernet dongle
}

foreach (nic_devices) {
start"/fs/mp/etc/usblauncher/netstart.sh busnum=$(busno),devnum=$(devno),path=$(USB_PATH),ign_remove /fs/mp/lib/dll/devnp-asix.so";
removal"/fs/mp/etc/usblauncher/netstop.sh";
}
</pre>

Content of <code>/fs/mp/etc/usblauncher/netstart.sh</code>

<pre>
#!/bin/sh

IFACE=ax0
IPADDR=192.168.1.26
mount -T io-pkt -o $1 $2
ifconfig $IFACE $IPADDR netmask 255.255.255.0
echo "debug $IFACE done."
</pre>

To get a working usb network on "production" OS, copy <code>devnp-asix.so</code> from [[reformat package]] to <code>/fs/mp/lib/dll/devnp-asix.so</code>

<pre>
1. pidin ar | grep usblauncher_otg
2. usblauncher_otg -S1 -c /fs/mp/etc/usblauncher/rules_otg.lua -M /fs/mp/etc/mcd.mnt -s /fs/mp/lib/dll/pubs/ -n/dev/otg/io-usb-otg -vvvv -b -eErtl

/fs/mp/etc/usblauncher/netstart.sh busnum=0x01,devnum=0x2,path=/dev/otg/io-usb-otg,ign_remove /fs/mp/lib/dll/devnp-asix.so
</pre>

== USB-HID == 
Run USB HID server:

<pre>
io-hid -d devh-usb.so
</pre>

You should get <code>devh-usb.so</code> lib from QNX SDP.

<code>io-hid</code> usage:

<pre>
# use io-hid
io-hid - HID Server ( Human Interface Device )

Usage:
io-hid [options] &

Options:
-d dll [opts] Device DLL to load and options to pass to the DLL.
-n name Set server name. default "/dev/io-hid/io-hid"
-v Be verbose
-V Display server version

Examples:

USB HID devices, PS/2 mouse, Serial mouse on COM1 directly, PS/2 keyboard

io-hid -dusb -dps2ser ps2mouse:mousedev:msoft:uart,1:kbd:kbddev &
</pre>

After launch <code>io-hid</code> all HID events will be grabbed by libscreen.

Use <code>[https://openqnx.com/static/neutrino/utilities/h/hidview.html hidview]</code> tool for get info about connected HID devices.

Unpacking firmware

2024-05-27T00:22:29Z

Admin: /* QNX-IFS */

== OS update package == 
All commands and tools described here work on Linux

=== Top layer archive === 

<pre>
$ tar -tf NU5T-14G381-AD_1689364279000.TAR.GZ

Version.der # Update certificate
apps.tar.gz # Apps partition
QNX-IFS # StartupIFS
MLO # Bootloader
</pre>

=== apps.tar.gz === 
<pre>
$ tar -tf apps.tar.gz
apps.img # qnx6fs image for hd0t177 or hd0t178
</pre>

This image can be mounted with:
<pre>
$ tar -tf apps.tar.gz
apps.img # qnx6fs image for hd0t177 or hd0t178
</pre>

=== QNX-IFS === 
Ifs images can be upacked and repacked with [https://github.com/bigunclemax/mkxfs mkxfs]

$ mount -t qnx6,ro -o loop apps.img /mnt/
<pre>
$ dumpifs -xr QNX-IFSremoval"/fs/mp/etc/usblauncher/netstop.sh";
}
</pre>

Unpacking firmware

2024-05-27T00:21:56Z

Admin: Created page with "== OS update package ==  All commands and tools described here work on Linux === Top layer archive ===  <pre> $ tar -tf NU5T-14G381-AD_1689364279000.TAR.GZ Version.der # Update certificate apps.tar.gz # Apps partition QNX-IFS # StartupIFS MLO # Bootloader </pre> === apps.tar.gz ===  <pre> $ tar -tf apps.tar.gz apps.img # qnx6fs image for hd0t177 or hd0t178 </pre> This image can be mounted with: <pre> $ tar -tf apps.tar...."

== OS update package == 
All commands and tools described here work on Linux

=== Top layer archive === 

<pre>
$ tar -tf NU5T-14G381-AD_1689364279000.TAR.GZ

Version.der # Update certificate
apps.tar.gz # Apps partition
QNX-IFS # StartupIFS
MLO # Bootloader
</pre>

=== apps.tar.gz === 
<pre>
$ tar -tf apps.tar.gz
apps.img # qnx6fs image for hd0t177 or hd0t178
</pre>

This image can be mounted with:
<pre>
$ tar -tf apps.tar.gz
apps.img # qnx6fs image for hd0t177 or hd0t178
</pre>

=== QNX-IFS === 
Ifs images can be upacked and repacked with mkxfs

$ mount -t qnx6,ro -o loop apps.img /mnt/
<pre>
$ dumpifs -xr QNX-IFSremoval"/fs/mp/etc/usblauncher/netstop.sh";
}
</pre>

USB subsystem

2024-05-27T00:06:32Z

Admin:

== USB subsystem == 
=== usblauncher === 

<pre>
/fs/mp/etc/usblauncher/
├── iap2ea.lua
├── iap2.lua
├── iap2ncm.lua
├── netstart.sh
├── netstop.sh
├── override.lua
├── rules.lua
├── rules_otg.lua
├── startncm-molex.sh
├── startncm.sh
├── stopncm.sh
└── umass.lua
</pre>

Useful commands:
<code>usb -vvv -N /dev/otg/io-usb-otg</code>

== USB-LAN ethernet == 
List of supported NICs in <code>/fs/mp/etc/usblauncher/rules_otg.lua</code>

<pre>
nic_devices = {
device(0x0b95, 0x7720); -- CISCO linksys USB300M ethernet dongle
device(0x0b95, 0x772b); -- Insignia NS-PU98505 ethernet dongle
device(0x2001, 0x3c05); -- D-Link DUB-E100 (revB1) ethernet dongle
device(0x2001, 0x1a02); -- D-Link DUB-E100 (revC1) ethernet dongle
}

foreach (nic_devices) {
start"/fs/mp/etc/usblauncher/netstart.sh busnum=$(busno),devnum=$(devno),path=$(USB_PATH),ign_remove /fs/mp/lib/dll/devnp-asix.so";
removal"/fs/mp/etc/usblauncher/netstop.sh";
}
</pre>

Content of <code>/fs/mp/etc/usblauncher/netstart.sh</code>

<pre>
#!/bin/sh

IFACE=ax0
IPADDR=192.168.1.26
mount -T io-pkt -o $1 $2
ifconfig $IFACE $IPADDR netmask 255.255.255.0
echo "debug $IFACE done."
</pre>

To get a working usb network on "production" OS, copy <code>devnp-asix.so</code> from [[reformat package]] to <code>/fs/mp/lib/dll/devnp-asix.so</code>

<pre>
1. pidin ar | grep usblauncher_otg
2. usblauncher_otg -S1 -c /fs/mp/etc/usblauncher/rules_otg.lua -M /fs/mp/etc/mcd.mnt -s /fs/mp/lib/dll/pubs/ -n/dev/otg/io-usb-otg -vvvv -b -eErtl

/fs/mp/etc/usblauncher/netstart.sh busnum=0x01,devnum=0x2,path=/dev/otg/io-usb-otg,ign_remove /fs/mp/lib/dll/devnp-asix.so
</pre>

== USB-HID == 
Run USB HID server:

<pre>
io-hid -d devh-usb.so
</pre>

You should get <code>devh-usb.so</code> lib from QNX SDP.

<code>io-hid</code> usage:

<pre>
# use io-hid
io-hid - HID Server ( Human Interface Device )

Usage:
io-hid [options] &

Options:
-d dll [opts] Device DLL to load and options to pass to the DLL.
-n name Set server name. default "/dev/io-hid/io-hid"
-v Be verbose
-V Display server version

Examples:

USB HID devices, PS/2 mouse, Serial mouse on COM1 directly, PS/2 keyboard

io-hid -dusb -dps2ser ps2mouse:mousedev:msoft:uart,1:kbd:kbddev &
</pre>

After launch <code>io-hid</code> all HID events will be grabbed by libscreen.

Use <code>hidview</code> tool for get info about connected HID devices.

USB subsystem

2024-05-26T23:57:32Z

Admin:

== USB subsystem == 
=== usblauncher === 

<pre>
/fs/mp/etc/usblauncher/
├── iap2ea.lua
├── iap2.lua
├── iap2ncm.lua
├── netstart.sh
├── netstop.sh
├── override.lua
├── rules.lua
├── rules_otg.lua
├── startncm-molex.sh
├── startncm.sh
├── stopncm.sh
└── umass.lua
</pre>

Useful commands:
<code>usb -vvv -N /dev/otg/io-usb-otg</code>

== USB-LAN ethernet == 
List of supported NICs in <code>/fs/mp/etc/usblauncher/rules_otg.lua</code>

<syntaxhighlight lang="lua">
nic_devices = {
device(0x0b95, 0x7720); -- CISCO linksys USB300M ethernet dongle
device(0x0b95, 0x772b); -- Insignia NS-PU98505 ethernet dongle
device(0x2001, 0x3c05); -- D-Link DUB-E100 (revB1) ethernet dongle
device(0x2001, 0x1a02); -- D-Link DUB-E100 (revC1) ethernet dongle
}

foreach (nic_devices) {
start"/fs/mp/etc/usblauncher/netstart.sh busnum=$(busno),devnum=$(devno),path=$(USB_PATH),ign_remove /fs/mp/lib/dll/devnp-asix.so";
removal"/fs/mp/etc/usblauncher/netstop.sh";
}
</syntaxhighlight>

Content of <code>/fs/mp/etc/usblauncher/netstart.sh</code>

<pre>
#!/bin/sh

IFACE=ax0
IPADDR=192.168.1.26
mount -T io-pkt -o $1 $2
ifconfig $IFACE $IPADDR netmask 255.255.255.0
echo "debug $IFACE done."
</pre>

To get a working usb network on "production" OS, copy <code>devnp-asix.so</code> from [[reformat package]] to <code>/fs/mp/lib/dll/devnp-asix.so</code>

<pre>
1. pidin ar | grep usblauncher_otg
2. usblauncher_otg -S1 -c /fs/mp/etc/usblauncher/rules_otg.lua -M /fs/mp/etc/mcd.mnt -s /fs/mp/lib/dll/pubs/ -n/dev/otg/io-usb-otg -vvvv -b -eErtl

/fs/mp/etc/usblauncher/netstart.sh busnum=0x01,devnum=0x2,path=/dev/otg/io-usb-otg,ign_remove /fs/mp/lib/dll/devnp-asix.so
</pre>

== USB-HID == 
Run USB HID server:

<pre>
io-hid -d devh-usb.so
</pre>

You should get <code>devh-usb.so</code> lib from QNX SDP.

<code>io-hid</code> usage:

<pre>
# use io-hid
io-hid - HID Server ( Human Interface Device )

Usage:
io-hid [options] &

Options:
-d dll [opts] Device DLL to load and options to pass to the DLL.
-n name Set server name. default "/dev/io-hid/io-hid"
-v Be verbose
-V Display server version

Examples:

USB HID devices, PS/2 mouse, Serial mouse on COM1 directly, PS/2 keyboard

io-hid -dusb -dps2ser ps2mouse:mousedev:msoft:uart,1:kbd:kbddev &
</pre>

After launch <code>io-hid</code> all HID events will be grabbed by libscreen.

Use <code>hidview</code> tool for get info about connected HID devices.

USB subsystem

2024-05-26T23:52:54Z

Admin:

== USB subsystem == 
=== usblauncher === 

<pre>
/fs/mp/etc/usblauncher/
├── iap2ea.lua
├── iap2.lua
├── iap2ncm.lua
├── netstart.sh
├── netstop.sh
├── override.lua
├── rules.lua
├── rules_otg.lua
├── startncm-molex.sh
├── startncm.sh
├── stopncm.sh
└── umass.lua
</pre>

Useful commands:
<code>usb -vvv -N /dev/otg/io-usb-otg</code>

== USB-LAN ethernet == 
List of supported NICs in <code>/fs/mp/etc/usblauncher/rules_otg.lua</code>

<syntaxhighlight lang="css" line>
nic_devices = {
device(0x0b95, 0x7720); -- CISCO linksys USB300M ethernet dongle
device(0x0b95, 0x772b); -- Insignia NS-PU98505 ethernet dongle
device(0x2001, 0x3c05); -- D-Link DUB-E100 (revB1) ethernet dongle
device(0x2001, 0x1a02); -- D-Link DUB-E100 (revC1) ethernet dongle
}

foreach (nic_devices) {
start"/fs/mp/etc/usblauncher/netstart.sh busnum=$(busno),devnum=$(devno),path=$(USB_PATH),ign_remove /fs/mp/lib/dll/devnp-asix.so";
removal"/fs/mp/etc/usblauncher/netstop.sh";
}
</syntaxhighlight>

Content of <code>/fs/mp/etc/usblauncher/netstart.sh</code>

<pre>
#!/bin/sh

IFACE=ax0
IPADDR=192.168.1.26
mount -T io-pkt -o $1 $2
ifconfig $IFACE $IPADDR netmask 255.255.255.0
echo "debug $IFACE done."
</pre>

To get a working usb network on "production" OS, copy <code>devnp-asix.so</code> from [[reformat package]] to <code>/fs/mp/lib/dll/devnp-asix.so</code>

<pre>
1. pidin ar | grep usblauncher_otg
2. usblauncher_otg -S1 -c /fs/mp/etc/usblauncher/rules_otg.lua -M /fs/mp/etc/mcd.mnt -s /fs/mp/lib/dll/pubs/ -n/dev/otg/io-usb-otg -vvvv -b -eErtl

/fs/mp/etc/usblauncher/netstart.sh busnum=0x01,devnum=0x2,path=/dev/otg/io-usb-otg,ign_remove /fs/mp/lib/dll/devnp-asix.so
</pre>

== USB-HID == 
Run USB HID server:

<pre>
io-hid -d devh-usb.so
</pre>

You should get <code>devh-usb.so</code> lib from QNX SDP.

<code>io-hid</code> usage:

<pre>
# use io-hid
io-hid - HID Server ( Human Interface Device )

Usage:
io-hid [options] &

Options:
-d dll [opts] Device DLL to load and options to pass to the DLL.
-n name Set server name. default "/dev/io-hid/io-hid"
-v Be verbose
-V Display server version

Examples:

USB HID devices, PS/2 mouse, Serial mouse on COM1 directly, PS/2 keyboard

io-hid -dusb -dps2ser ps2mouse:mousedev:msoft:uart,1:kbd:kbddev &
</pre>

After launch <code>io-hid</code> all HID events will be grabbed by libscreen.

Use <code>hidview</code> tool for get info about connected HID devices.

USB subsystem

2024-05-26T23:49:55Z

Admin:

== USB subsystem == 
=== usblauncher === 

<pre>
/fs/mp/etc/usblauncher/
├── iap2ea.lua
├── iap2.lua
├── iap2ncm.lua
├── netstart.sh
├── netstop.sh
├── override.lua
├── rules.lua
├── rules_otg.lua
├── startncm-molex.sh
├── startncm.sh
├── stopncm.sh
└── umass.lua
</pre>

Useful commands:
<code>usb -vvv -N /dev/otg/io-usb-otg</code>

== USB-LAN ethernet == 
List of supported NICs in <code>/fs/mp/etc/usblauncher/rules_otg.lua</code>

<syntaxhighlight lang="lua" line>
nic_devices = {
device(0x0b95, 0x7720); -- CISCO linksys USB300M ethernet dongle
device(0x0b95, 0x772b); -- Insignia NS-PU98505 ethernet dongle
device(0x2001, 0x3c05); -- D-Link DUB-E100 (revB1) ethernet dongle
device(0x2001, 0x1a02); -- D-Link DUB-E100 (revC1) ethernet dongle
}

foreach (nic_devices) {
start"/fs/mp/etc/usblauncher/netstart.sh busnum=$(busno),devnum=$(devno),path=$(USB_PATH),ign_remove /fs/mp/lib/dll/devnp-asix.so";
removal"/fs/mp/etc/usblauncher/netstop.sh";
}
</syntaxhighlight>

Content of <code>/fs/mp/etc/usblauncher/netstart.sh</code>

<pre>
#!/bin/sh

IFACE=ax0
IPADDR=192.168.1.26
mount -T io-pkt -o $1 $2
ifconfig $IFACE $IPADDR netmask 255.255.255.0
echo "debug $IFACE done."
</pre>

To get a working usb network on "production" OS, copy <code>devnp-asix.so</code> from [[reformat package]] to <code>/fs/mp/lib/dll/devnp-asix.so</code>

<pre>
1. pidin ar | grep usblauncher_otg
2. usblauncher_otg -S1 -c /fs/mp/etc/usblauncher/rules_otg.lua -M /fs/mp/etc/mcd.mnt -s /fs/mp/lib/dll/pubs/ -n/dev/otg/io-usb-otg -vvvv -b -eErtl

/fs/mp/etc/usblauncher/netstart.sh busnum=0x01,devnum=0x2,path=/dev/otg/io-usb-otg,ign_remove /fs/mp/lib/dll/devnp-asix.so
</pre>

== USB-HID == 
Run USB HID server:

<pre>
io-hid -d devh-usb.so
</pre>

You should get <code>devh-usb.so</code> lib from QNX SDP.

<code>io-hid</code> usage:

<pre>
# use io-hid
io-hid - HID Server ( Human Interface Device )

Usage:
io-hid [options] &

Options:
-d dll [opts] Device DLL to load and options to pass to the DLL.
-n name Set server name. default "/dev/io-hid/io-hid"
-v Be verbose
-V Display server version

Examples:

USB HID devices, PS/2 mouse, Serial mouse on COM1 directly, PS/2 keyboard

io-hid -dusb -dps2ser ps2mouse:mousedev:msoft:uart,1:kbd:kbddev &
</pre>

After launch <code>io-hid</code> all HID events will be grabbed by libscreen.

Use <code>hidview</code> tool for get info about connected HID devices.

USB subsystem

2024-05-26T23:23:43Z

Admin:

== USB subsystem == 
=== usblauncher === 

<pre>
/fs/mp/etc/usblauncher/
├── iap2ea.lua
├── iap2.lua
├── iap2ncm.lua
├── netstart.sh
├── netstop.sh
├── override.lua
├── rules.lua
├── rules_otg.lua
├── startncm-molex.sh
├── startncm.sh
├── stopncm.sh
└── umass.lua
</pre>

Useful commands:
<code>usb -vvv -N /dev/otg/io-usb-otg</code>

== USB-LAN ethernet == 
List of supported NICs in <code>/fs/mp/etc/usblauncher/rules_otg.lua</code>

<pre>
nic_devices = {
device(0x0b95, 0x7720); -- CISCO linksys USB300M ethernet dongle
device(0x0b95, 0x772b); -- Insignia NS-PU98505 ethernet dongle
device(0x2001, 0x3c05); -- D-Link DUB-E100 (revB1) ethernet dongle
device(0x2001, 0x1a02); -- D-Link DUB-E100 (revC1) ethernet dongle
}

foreach (nic_devices) {
start"/fs/mp/etc/usblauncher/netstart.sh busnum=$(busno),devnum=$(devno),path=$(USB_PATH),ign_remove /fs/mp/lib/dll/devnp-asix.so";
removal"/fs/mp/etc/usblauncher/netstop.sh";
}
</pre>

Content of <code>/fs/mp/etc/usblauncher/netstart.sh</code>

<pre>
#!/bin/sh

IFACE=ax0
IPADDR=192.168.1.26
mount -T io-pkt -o $1 $2
ifconfig $IFACE $IPADDR netmask 255.255.255.0
echo "debug $IFACE done."
</pre>

To get a working usb network on "production" OS, copy <code>devnp-asix.so</code> from [[reformat package]] to <code>/fs/mp/lib/dll/devnp-asix.so</code>

<pre>
1. pidin ar | grep usblauncher_otg
2. usblauncher_otg -S1 -c /fs/mp/etc/usblauncher/rules_otg.lua -M /fs/mp/etc/mcd.mnt -s /fs/mp/lib/dll/pubs/ -n/dev/otg/io-usb-otg -vvvv -b -eErtl

/fs/mp/etc/usblauncher/netstart.sh busnum=0x01,devnum=0x2,path=/dev/otg/io-usb-otg,ign_remove /fs/mp/lib/dll/devnp-asix.so
</pre>

== USB-HID == 
Run USB HID server:

<pre>
io-hid -d devh-usb.so
</pre>

You should get <code>devh-usb.so</code> lib from QNX SDP.

<code>io-hid</code> usage:

<pre>
# use io-hid
io-hid - HID Server ( Human Interface Device )

Usage:
io-hid [options] &

Options:
-d dll [opts] Device DLL to load and options to pass to the DLL.
-n name Set server name. default "/dev/io-hid/io-hid"
-v Be verbose
-V Display server version

Examples:

USB HID devices, PS/2 mouse, Serial mouse on COM1 directly, PS/2 keyboard

io-hid -dusb -dps2ser ps2mouse:mousedev:msoft:uart,1:kbd:kbddev &
</pre>

After launch <code>io-hid</code> all HID events will be grabbed by libscreen.

Use <code>hidview</code> tool for get info about connected HID devices.

USB subsystem

2024-05-26T23:23:09Z

Admin:

== USB subsystem == 
=== usblauncher === 

<pre>
/fs/mp/etc/usblauncher/
├── iap2ea.lua
├── iap2.lua
├── iap2ncm.lua
├── netstart.sh
├── netstop.sh
├── override.lua
├── rules.lua
├── rules_otg.lua
├── startncm-molex.sh
├── startncm.sh
├── stopncm.sh
└── umass.lua
</pre>

Useful commands:
<code>usb -vvv -N /dev/otg/io-usb-otg</code>

== USB-LAN ethernet == 
List of supported NICs in <code>/fs/mp/etc/usblauncher/rules_otg.lua</code>

<pre>
nic_devices = {
device(0x0b95, 0x7720); -- CISCO linksys USB300M ethernet dongle
device(0x0b95, 0x772b); -- Insignia NS-PU98505 ethernet dongle
device(0x2001, 0x3c05); -- D-Link DUB-E100 (revB1) ethernet dongle
device(0x2001, 0x1a02); -- D-Link DUB-E100 (revC1) ethernet dongle
}

foreach (nic_devices) {
start"/fs/mp/etc/usblauncher/netstart.sh busnum=$(busno),devnum=$(devno),path=$(USB_PATH),ign_remove /fs/mp/lib/dll/devnp-asix.so";
removal"/fs/mp/etc/usblauncher/netstop.sh";
}
└── umass.lua
</pre>

Content of <code>/fs/mp/etc/usblauncher/netstart.sh</code>

<pre>
#!/bin/sh

IFACE=ax0
IPADDR=192.168.1.26
mount -T io-pkt -o $1 $2
ifconfig $IFACE $IPADDR netmask 255.255.255.0
echo "debug $IFACE done."
</pre>

To get a working usb network on "production" OS, copy <code>devnp-asix.so</code> from [[reformat package]] to <code>/fs/mp/lib/dll/devnp-asix.so</code>

<pre>
1. pidin ar | grep usblauncher_otg
2. usblauncher_otg -S1 -c /fs/mp/etc/usblauncher/rules_otg.lua -M /fs/mp/etc/mcd.mnt -s /fs/mp/lib/dll/pubs/ -n/dev/otg/io-usb-otg -vvvv -b -eErtl

/fs/mp/etc/usblauncher/netstart.sh busnum=0x01,devnum=0x2,path=/dev/otg/io-usb-otg,ign_remove /fs/mp/lib/dll/devnp-asix.so
</pre>

== USB-HID == 
Run USB HID server:

<pre>
io-hid -d devh-usb.so
</pre>

You should get <code>devh-usb.so</code> lib from QNX SDP.

<code>io-hid</code> usage:

<pre>
# use io-hid
io-hid - HID Server ( Human Interface Device )

Usage:
io-hid [options] &

Options:
-d dll [opts] Device DLL to load and options to pass to the DLL.
-n name Set server name. default "/dev/io-hid/io-hid"
-v Be verbose
-V Display server version

Examples:

USB HID devices, PS/2 mouse, Serial mouse on COM1 directly, PS/2 keyboard

io-hid -dusb -dps2ser ps2mouse:mousedev:msoft:uart,1:kbd:kbddev &
</pre>

After launch <code>io-hid</code> all HID events will be grabbed by libscreen.

Use <code>hidview</code> tool for get info about connected HID devices.

USB subsystem

2024-05-26T23:22:53Z

Admin:

== USB subsystem == 
=== usblauncher === 

<pre>
/fs/mp/etc/usblauncher/
├── iap2ea.lua
├── iap2.lua
├── iap2ncm.lua
├── netstart.sh
├── netstop.sh
├── override.lua
├── rules.lua
├── rules_otg.lua
├── startncm-molex.sh
├── startncm.sh
├── stopncm.sh
└── umass.lua
</pre>

Useful commands:
<code>usb -vvv -N /dev/otg/io-usb-otg</code>

== USB-LAN ethernet == 
List of supported NICs in <code>/fs/mp/etc/usblauncher/rules_otg.lua</code>

<syntaxhighlight lang="python" line>
nic_devices = {
device(0x0b95, 0x7720); -- CISCO linksys USB300M ethernet dongle
device(0x0b95, 0x772b); -- Insignia NS-PU98505 ethernet dongle
device(0x2001, 0x3c05); -- D-Link DUB-E100 (revB1) ethernet dongle
device(0x2001, 0x1a02); -- D-Link DUB-E100 (revC1) ethernet dongle
}

foreach (nic_devices) {
start"/fs/mp/etc/usblauncher/netstart.sh busnum=$(busno),devnum=$(devno),path=$(USB_PATH),ign_remove /fs/mp/lib/dll/devnp-asix.so";
removal"/fs/mp/etc/usblauncher/netstop.sh";
}
└── umass.lua
</syntaxhighlight>

Content of <code>/fs/mp/etc/usblauncher/netstart.sh</code>

<pre>
#!/bin/sh

IFACE=ax0
IPADDR=192.168.1.26
mount -T io-pkt -o $1 $2
ifconfig $IFACE $IPADDR netmask 255.255.255.0
echo "debug $IFACE done."
</pre>

To get a working usb network on "production" OS, copy <code>devnp-asix.so</code> from [[reformat package]] to <code>/fs/mp/lib/dll/devnp-asix.so</code>

<pre>
1. pidin ar | grep usblauncher_otg
2. usblauncher_otg -S1 -c /fs/mp/etc/usblauncher/rules_otg.lua -M /fs/mp/etc/mcd.mnt -s /fs/mp/lib/dll/pubs/ -n/dev/otg/io-usb-otg -vvvv -b -eErtl

/fs/mp/etc/usblauncher/netstart.sh busnum=0x01,devnum=0x2,path=/dev/otg/io-usb-otg,ign_remove /fs/mp/lib/dll/devnp-asix.so
</pre>

== USB-HID == 
Run USB HID server:

<pre>
io-hid -d devh-usb.so
</pre>

You should get <code>devh-usb.so</code> lib from QNX SDP.

<code>io-hid</code> usage:

<pre>
# use io-hid
io-hid - HID Server ( Human Interface Device )

Usage:
io-hid [options] &

Options:
-d dll [opts] Device DLL to load and options to pass to the DLL.
-n name Set server name. default "/dev/io-hid/io-hid"
-v Be verbose
-V Display server version

Examples:

USB HID devices, PS/2 mouse, Serial mouse on COM1 directly, PS/2 keyboard

io-hid -dusb -dps2ser ps2mouse:mousedev:msoft:uart,1:kbd:kbddev &
</pre>

After launch <code>io-hid</code> all HID events will be grabbed by libscreen.

Use <code>hidview</code> tool for get info about connected HID devices.

USB subsystem

2024-05-26T23:10:17Z

Admin: Created page with "== USB subsystem ==  === usblauncher ===  <pre> /fs/mp/etc/usblauncher/ ├── iap2ea.lua ├── iap2.lua ├── iap2ncm.lua ├── netstart.sh ├── netstop.sh ├── override.lua ├── rules.lua ├── rules_otg.lua ├── startncm-molex.sh ├── startncm.sh ├── stopncm.sh └── umass.lua </pre> Useful commands: <code>usb -vvv -N /dev/otg/io-usb-otg</code> == USB-LAN ethernet ==  List of supp..."

== USB subsystem == 
=== usblauncher === 

<pre>
/fs/mp/etc/usblauncher/
├── iap2ea.lua
├── iap2.lua
├── iap2ncm.lua
├── netstart.sh
├── netstop.sh
├── override.lua
├── rules.lua
├── rules_otg.lua
├── startncm-molex.sh
├── startncm.sh
├── stopncm.sh
└── umass.lua
</pre>

Useful commands:
<code>usb -vvv -N /dev/otg/io-usb-otg</code>

== USB-LAN ethernet == 
List of supported NICs in <code>/fs/mp/etc/usblauncher/rules_otg.lua</code>

<pre>
nic_devices = {
device(0x0b95, 0x7720); -- CISCO linksys USB300M ethernet dongle
device(0x0b95, 0x772b); -- Insignia NS-PU98505 ethernet dongle
device(0x2001, 0x3c05); -- D-Link DUB-E100 (revB1) ethernet dongle
device(0x2001, 0x1a02); -- D-Link DUB-E100 (revC1) ethernet dongle
}

foreach (nic_devices) {
start"/fs/mp/etc/usblauncher/netstart.sh busnum=$(busno),devnum=$(devno),path=$(USB_PATH),ign_remove /fs/mp/lib/dll/devnp-asix.so";
removal"/fs/mp/etc/usblauncher/netstop.sh";
}
└── umass.lua
</pre>

Content of <code>/fs/mp/etc/usblauncher/netstart.sh</code>

<pre>
#!/bin/sh

IFACE=ax0
IPADDR=192.168.1.26
mount -T io-pkt -o $1 $2
ifconfig $IFACE $IPADDR netmask 255.255.255.0
echo "debug $IFACE done."
</pre>

To get a working usb network on "production" OS, copy <code>devnp-asix.so</code> from [[reformat package]] to <code>/fs/mp/lib/dll/devnp-asix.so</code>

<pre>
1. pidin ar | grep usblauncher_otg
2. usblauncher_otg -S1 -c /fs/mp/etc/usblauncher/rules_otg.lua -M /fs/mp/etc/mcd.mnt -s /fs/mp/lib/dll/pubs/ -n/dev/otg/io-usb-otg -vvvv -b -eErtl

/fs/mp/etc/usblauncher/netstart.sh busnum=0x01,devnum=0x2,path=/dev/otg/io-usb-otg,ign_remove /fs/mp/lib/dll/devnp-asix.so
</pre>

== USB-HID == 
Run USB HID server:

<pre>
io-hid -d devh-usb.so
</pre>

You should get <code>devh-usb.so</code> lib from QNX SDP.

<code>io-hid</code> usage:

<pre>
# use io-hid
io-hid - HID Server ( Human Interface Device )

Usage:
io-hid [options] &

Options:
-d dll [opts] Device DLL to load and options to pass to the DLL.
-n name Set server name. default "/dev/io-hid/io-hid"
-v Be verbose
-V Display server version

Examples:

USB HID devices, PS/2 mouse, Serial mouse on COM1 directly, PS/2 keyboard

io-hid -dusb -dps2ser ps2mouse:mousedev:msoft:uart,1:kbd:kbddev &
</pre>

After launch <code>io-hid</code> all HID events will be grabbed by libscreen.

Use <code>hidview</code> tool for get info about connected HID devices.

Logging subsystem

2024-05-26T23:03:35Z

Admin:

== QNX system logs == 

<code>/bin/sloginfo</code> - print system log
<code>/proc/boot/slogger</code> - system logger

== PASA (Panasonic) tools == 

=== nslogutil === 

<code>/fs/mp/apps/usr/sbin/nslogutil</code>
<pre>
Help: nslogutil -q QUEUENAME [-m MASKVALUE(hex)] | [-l "slogger|msgq|console"] [-p "log message"] [-s severity] [-g "mask|outopt|severity"] [-t "rxontxoff, rxofftxon, rxontxon, rxofftxoff"] [-d Debug Dump Request]
</pre>

Examples:
<code>nslogutil -q IPC_MID -l "slogger" -m 0xefffffff</code>
<code>nslogutil -q IPC_MID -m 0xFFFFFF -t rxontxon -s 1</code>

=== CustomCommandLineOption() === 
Sync 3 common cmdline options (<code>CustomCommandLineOption()</code>)

<pre>
optstr: "l:m:t:c:p:qr:s"

-l (log output option)
Allowed values: "slogger", "console", "shmem" (And always to fs/rwdata/fordlogs/)
This vales may be combined with '|' Ex: -l "slogger|console"

-m (mask value) This log level masks(Up to 16 masks). Each mask represent certain subsystem.
Ex: -m "0xFFFFFFFF,0xFFFFFFFF,0xFFFFFFFF,0xFFFFFFFF"

-r [plog output option (byte)] Enable PLOG
-s Enable sys event log
-q queue name <%s>
-p (set priority) <??? %s>
-c (set config file) <filepath %s>
-t (set transmit logging) <??? %s>
</pre>

== Log paths == 
Please keep in mind that this list contains only logs enabled by default on the system.

<pre>
/fs/rwdata/fordlogs/pas_debug.log
/fs/rwdata/fordlogs/BTLogs/NET_BT_Service.log
/fs/rwdata/logs/sys_error.log.0
/fs/rwdata/logs/96.bmetrics_data.log
/fs/rwdata/logs/96.ns_perf.log
/fs/rwdata/slogs/96.slog
/fs/rwdata/logs/sys_slog_info
/fs/rwdata/NAV/gnss/96-MSL_Log.txt
/fs/rwdata/NAV/gnss/96-CL_Log.txt
/fs/rwdata/NAV/unifiedsearch.log
/fs/rwdata/BEZEL_DIAGNOSTICS_LOG.txt
/fs/mp/NAV/Job2/resource/config/log.xml
/fs/mp/etc/AppLink/log4cxx.debug.properties
/fs/mp/etc/AppLink/log4cxx.properties
/fs/mp/etc/BT_HCILogSize.cfg
/fs/mp/etc/firmware/NS_SLog_config.cfg
/fs/mp/diagnostics/etc/quip/log_silver_config
/fs/mp/diagnostics/scripts/filter-btlog.sed
/fs/mp/diagnostics/scripts/filter-nuancelog.sed
/fs/mp/diagnostics/scripts/filter-osapilog.sed
/fs/mp/diagnostics/scripts/filter-slog.sed
/fs/mp/diagnostics/scripts/quip-log-silver.sh
/fs/images/ivsu_cache/Encoded_Interrogator_Log.xml
/dev/shmem/fts_log1.tmp
/dev/shmem/osapi.log
/dev/shmem/animamtion.log
/dev/shmem/NavMiniApplog.txt
/dev/shmem/NavAccellog.txt
</pre>

== Other == 
<pre>
/usr/sbin/tracelogger
/apps/NS_PasLogCapture
/fs/mp/apps/RCN_DiagnosticsLog
/fs/mp/apps/SS_SLogMonitor
/fs/mp/apps/VCA_Logger_Enable

/proc/boot/libPlog.so.1
/fs/mp/apps/usr/lib/libArtLog.so
/fs/mp/apps/usr/lib/liblog4cxx.so.10
/fs/mp/apps/usr/lib/libNS_Logger.so
/fs/mp/apps/usr/lib/libresource_logger.so
/fs/mp/usr/lib/liblogging.so.1
/fs/mp/NAV/libclientlogger.so
/fs/mp/NAV/libNAV_TI_Log.so

/fs/mp/qt5/qml/QtTest/testlogger.js
/fs/mp/fordhmi/test/alsim_loglevelset
/fs/mp/fordhmi/test/HmiLogScript.sh
</pre>

Logging subsystem

2024-05-26T23:02:25Z

Admin: Created page with "== QNX system logs ==  <code>/bin/sloginfo</code> - print system log <code>/proc/boot/slogger</code> - system logger == PASA (Panasonic) tools ==  === nslogutil ===  <code>/fs/mp/apps/usr/sbin/nslogutil</code> <pre> Help: nslogutil -q QUEUENAME [-m MASKVALUE(hex)] | [-l "slogger|msgq|console"] [-p "log message"] [-s severity] [-g "mask|outopt|severity"] [-t "rxontxoff, rxofftxon, rxontxon, rxofftxoff"] [-d Debug Dump Request] </pre> Ex..."

== QNX system logs == 

<code>/bin/sloginfo</code> - print system log
<code>/proc/boot/slogger</code> - system logger

== PASA (Panasonic) tools == 

=== nslogutil === 

<code>/fs/mp/apps/usr/sbin/nslogutil</code>
<pre>
Help: nslogutil -q QUEUENAME [-m MASKVALUE(hex)] | [-l "slogger|msgq|console"] [-p "log message"] [-s severity] [-g "mask|outopt|severity"] [-t "rxontxoff, rxofftxon, rxontxon, rxofftxoff"] [-d Debug Dump Request]
</pre>

Examples:
<code>nslogutil -q IPC_MID -l "slogger" -m 0xefffffff</code>
<code>nslogutil -q IPC_MID -m 0xFFFFFF -t rxontxon -s 1</code>

=== CustomCommandLineOption() === 
Sync 3 common cmdline options (<code>CustomCommandLineOption()</code>)

<pre>
optstr: "l:m:t:c:p:qr:s"

-l (log output option)
Allowed values: "slogger", "console", "shmem" (And always to fs/rwdata/fordlogs/)
This vales may be combined with '|' Ex: -l "slogger|console"

-m (mask value) This log level masks(Up to 16 masks). Each mask represent certain subsystem.
Ex: -m "0xFFFFFFFF,0xFFFFFFFF,0xFFFFFFFF,0xFFFFFFFF"

-r [plog output option (byte)] Enable PLOG
-s Enable sys event log
-q queue name <%s>
-p (set priority) <??? %s>
-c (set config file) <filepath %s>
-t (set transmit logging) <??? %s>
</pre>

== Log paths == 
<pre>
/fs/rwdata/fordlogs/pas_debug.log
/fs/rwdata/fordlogs/BTLogs/NET_BT_Service.log
/fs/rwdata/logs/sys_error.log.0
/fs/rwdata/logs/96.bmetrics_data.log
/fs/rwdata/logs/96.ns_perf.log
/fs/rwdata/slogs/96.slog
/fs/rwdata/logs/sys_slog_info
/fs/rwdata/NAV/gnss/96-MSL_Log.txt
/fs/rwdata/NAV/gnss/96-CL_Log.txt
/fs/rwdata/NAV/unifiedsearch.log
/fs/rwdata/BEZEL_DIAGNOSTICS_LOG.txt
/fs/mp/NAV/Job2/resource/config/log.xml
/fs/mp/etc/AppLink/log4cxx.debug.properties
/fs/mp/etc/AppLink/log4cxx.properties
/fs/mp/etc/BT_HCILogSize.cfg
/fs/mp/etc/firmware/NS_SLog_config.cfg
/fs/mp/diagnostics/etc/quip/log_silver_config
/fs/mp/diagnostics/scripts/filter-btlog.sed
/fs/mp/diagnostics/scripts/filter-nuancelog.sed
/fs/mp/diagnostics/scripts/filter-osapilog.sed
/fs/mp/diagnostics/scripts/filter-slog.sed
/fs/mp/diagnostics/scripts/quip-log-silver.sh
/fs/images/ivsu_cache/Encoded_Interrogator_Log.xml
/dev/shmem/fts_log1.tmp
/dev/shmem/osapi.log
/dev/shmem/animamtion.log
/dev/shmem/NavMiniApplog.txt
/dev/shmem/NavAccellog.txt
</pre>

== Other == 
<pre>
/usr/sbin/tracelogger
/apps/NS_PasLogCapture
/fs/mp/apps/RCN_DiagnosticsLog
/fs/mp/apps/SS_SLogMonitor
/fs/mp/apps/VCA_Logger_Enable

/proc/boot/libPlog.so.1
/fs/mp/apps/usr/lib/libArtLog.so
/fs/mp/apps/usr/lib/liblog4cxx.so.10
/fs/mp/apps/usr/lib/libNS_Logger.so
/fs/mp/apps/usr/lib/libresource_logger.so
/fs/mp/usr/lib/liblogging.so.1
/fs/mp/NAV/libclientlogger.so
/fs/mp/NAV/libNAV_TI_Log.so

/fs/mp/qt5/qml/QtTest/testlogger.js
/fs/mp/fordhmi/test/alsim_loglevelset
/fs/mp/fordhmi/test/HmiLogScript.sh
</pre>

Graphics subsystem

2024-05-26T22:54:20Z

Admin: Created page with "== DRM/GPU ==  https://www.qnx.com/developers/docs/8.0/com.qnx.doc.screen/topic/manual/cscreen_config_intro.html Screen configs: <pre> # cd /usr/lib/graphics/omap5430ES2_0/ # ls -l *.conf lrwxrwxrwx 1 root root 47 Jan 01 07:09 graphics.conf -> /usr/lib/graphics/omap5430ES2_0/graphics_l.conf -rwxr-xr-x 1 root root 1132 Jul 07 2023 graphics_l.conf -rwxr-xr-x 1 root root 1518 Jul 07 2023 graphics_p.conf </pre>..."

== DRM/GPU == 
https://www.qnx.com/developers/docs/8.0/com.qnx.doc.screen/topic/manual/cscreen_config_intro.html

Screen configs:

<pre>
# cd /usr/lib/graphics/omap5430ES2_0/
# ls -l *.conf
lrwxrwxrwx 1 root root 47 Jan 01 07:09 graphics.conf -> /usr/lib/graphics/omap5430ES2_0/graphics_l.conf
-rwxr-xr-x 1 root root 1132 Jul 07 2023 graphics_l.conf
-rwxr-xr-x 1 root root 1518 Jul 07 2023 graphics_p.conf
</pre>

Content of <code>omap5430ES2_0</code>

<pre>
# ls -l /usr/lib/graphics/omap5430ES2_0/
-rwxr-xr-x 1 root root 1132 Jul 07 2023 graphics_l.conf
-rwxr-xr-x 1 root root 1518 Jul 07 2023 graphics_p.conf
-rwxr-xr-x 1 root root 156128 Jul 07 2023 libGalcore.so
-rwxr-xr-x 1 root root 80160 Jul 07 2023 libIMGegl.so
-rwxr-xr-x 1 root root 622858 Jul 07 2023 libImgGLESv1_CM.so
-rwxr-xr-x 1 root root 579327 Jul 07 2023 libImgGLESv2.so
-rwxr-xr-x 1 root root 12918 Jul 07 2023 libPVRScopeServices.so
-rwxr-xr-x 1 root root 238627 Jul 07 2023 libWFDomap5430ES2_0.so
-rwxr-xr-x 1 root root 357126 Jul 07 2023 libglslcompiler.so
-rwxr-xr-x 1 root root 28319 Jul 07 2023 libpvr2d.so
-rwxr-xr-x 1 root root 260768 Jul 07 2023 libsrv_um.so
-rwxr-xr-x 1 root root 1712821 Jul 07 2023 libusc.so
lrwxr-xr-x 1 root root 14 Jul 07 2023 libwfdcfg-sync3.so -> libwfdcfg.so.0
-rwxr-xr-x 1 root root 10922 Jul 07 2023 libwfdcfg.so.0
-rwxr-xr-x 1 root root 259185 Jul 07 2023 pvrsrv.so
-rwxr-xr-x 1 root root 91225 Jul 07 2023 pvrsrvinit.so
-rwxr-xr-x 1 root root 26403 Jul 07 2023 wsegl-screen.so
</pre>

<pre>
NAME=libWFDomap5430ES2_0.so
DESCRIPTION=OpenWF Display for TI omap5430ES2_0
</pre>

Disk subsystem

2024-05-26T22:52:01Z

Admin: Created page with "== Bootloader + Startup IFS ==  https://www.qnx.com/developers/docs/7.1/#com.qnx.doc.neutrino.building/topic/intro/intro_startup_sequence.html <code>MLO</code> - ROM monitor or Multimedia card Loader. <code>Startup IFS</code> - Startup program, QNX kernel and rootfs Layout on EMMC flash: <pre> Block# Offset in bytes Name --------------------------------------------------- 0x0000 0x0000000 MBR 0x0002 0x0000400 (1024) bo..."

== Bootloader + Startup IFS == 
https://www.qnx.com/developers/docs/7.1/#com.qnx.doc.neutrino.building/topic/intro/intro_startup_sequence.html

<code>MLO</code> - ROM monitor or Multimedia card Loader.
<code>Startup IFS</code> - Startup program, QNX kernel and rootfs

Layout on EMMC flash:
<pre>
Block# Offset in bytes Name
---------------------------------------------------
0x0000 0x0000000 MBR
0x0002 0x0000400 (1024) boot bank info
0x0100 0x0020000 (131072) MLO
0x0184 0x0030800 (198656) IFS first bank
0x7cd2 0x0F9A400 (16360448) IFS second bank
</pre>

== Bootloader + Startup IFS == 
<pre>
# fdisk /dev/hd0 show -l

_____OS_____ Start End ______Number______ Size Boot
name type Block Block Cylinders Blocks

1. DOS 6 32 65535 32 65504 31 MB *
2. QNX6 177 65536 3211263 1536 3145728 1536 MB
3. QNX6 178 3211264 6356991 1536 3145728 1536 MB
4. Extd'd 5 6356992 122142719 56536 115785728 56536 MB
4.1 nonQNX 180 6357024 119595007 55292 113237984 55291 MB
4.2 BSD 181 119595040 122138623 1242 2543584 1241 MB
4.3 nonQNX 182 122138656 122142719 2 4064 1 MB
</pre>

== hd0t180 == 

Mountpoint: <code>/fs/images</code>
Called from startup script(startupIFS)

<pre>
mount -b -t qnx6 -o noatime,alignio /dev/hd0t180 /fs/images
</pre>

== hd0t177 or hd0t178 == 

Mountpoint: <code>/fs/mp</code>
Called from <code>/etc/script_mnt.sh</code> (startupIFS)

<pre>
mmc_get_act /dev/hd0 0 > /tmp/mmcinfo
mount -b -r -t qnx6 -o snapshot=0,noatime,alignio $MMC_ACT_FS_PART /fs/mp
</pre>

<pre>
# cat /tmp/mmcinfo
MMC_ACT_FS_PART=/dev/hd0t177
MMC_PAS_FS_PART=/dev/hd0t178
MMC_ACT_IFS=0
MMC_PAS_IFS=1
ACT_IFS_ERROR=0
ACT_FS_ERROR=0
STARTUP_IFS_ERROR=0
</pre>

== hd0t181 == 

Mountpoint: <code>/fs/rwdata</code>
Called from startup script (startupIFS)

<pre>
mount -b -t qnx6 -o alignio /dev/hd0t181 /fs/rwdata &
</pre>

== IFSs == 

Mountpoint: <code>/fs/mp/ifs</code>
Called from startup script

<pre>
mount_ifs -b -f /fs/mp/ifs/renderer-ifs -m / &
mount_ifs -b -f /fs/mp/ifs/quickapps-ifs -m / &
mount_ifs -b -f /fs/mp/ifs/second-ifs -m / &
</pre>

<pre>
# use mount_ifs
mount_ifs mount-ifs Utility

Syntax: mount-ifs [-f filename][-m mountpoint]

Options:
-f filename source ifs file name
-m mount point
-b daemonize before the real transfer (default is after).
-T create a separate thread to do the decompress in parallel.
</pre>

== Mount images == 

Called from <code>sh /etc/mount_all_images.sh</code>

== Some info == 

<pre>
# ls -la /fs/images/
total 41277473
drwxrwxr-x 5 root root 4096 Jan 01 1970 .
drwxr-xr-t 2 root root 10 Jan 01 1970 ..
drwx------ 2 root root 4096 Jan 01 1970 .boot
drwxrwxrwx 4 root root 4096 Jan 01 00:10 ivsu_cache
drwxrwxrwx 2 root root 4096 Jan 01 00:10 ivsu_installcache
-rw-rw-rw- 1 root root 3351511040 Jan 01 1970 map_comn.img
-rw-rw-rw- 1 root root 3456892928 Jan 01 1970 map_euc.img
-rw-rw-rw- 1 root root 3985637376 Jan 01 1970 map_eue.img
-rw-rw-rw- 1 root root 3018063872 Jan 01 1970 map_eus.img
-rw-rw-rw- 1 root root 1243611136 Jan 01 1970 map_ext.img
-rw-rw-rw- 1 root root 76283904 Jan 01 1970 station_logos.img
-rw-rw-rw- 1 root root 2072248320 Jan 01 1970 voice.img
-rw-rw-rw- 1 root root 3929800704 Jan 01 1970 voice_nav_eucpr.img
</pre>

<pre>
# df -h
/fs/rwdata/ppsp 0 0 0 100% /ppsp
/dev/blk/ram-0-allo 128M 1.2M 127M 1% /fs/tmpfs/
/fs/images/map_ext. 1.1G 1.1G 892K 100% /fs/sd/MAP/
/fs/images/map_eus. 2.8G 2.7G 14M 100% /fs/sd/MAP/
/fs/images/map_eue. 3.7G 3.6G 21M 100% /fs/sd/MAP/
/fs/images/map_euc. 3.2G 3.2G 5.7M 100% /fs/sd/MAP/
/fs/images/map_comn 3.1G 3.0G 24M 100% /fs/sd/MAP/
/fs/images/voice_na 3.6G 3.6G 35M 100% /fs/Nuance/
/fs/images/voice.im 1.9G 1.9G 8.4M 100% /fs/Nuance/
/dev/hd0t181 1.2G 849M 393M 69% /fs/rwdata/
/dev/diagscratch0 35M 30K 35M 1% /fs/rwdata/quip/
/dev/diagevents0 90M 68K 90M 1% /fs/rwdata/quip/
/dev/hd0t177 1.4G 1.3G 126M 92% /fs/mp/
/fs/images/station_ 73M 72M 432K 100% /fs/mp/resources
/dev/hd0t180 54G 22G 32G 41% /fs/images/
/var/pps 0 0 0 100% /pps
/dev/hd0 1.9M 1.9M 0 100% /dev/hd0t182
/dev/hd0 1.5G 1.5G 0 100% /dev/hd0t178
/dev/hd0 32M 32M 0 100% /dev/hd0t6
/dev/hd0 58G 58G 0 100%
</pre>

<pre>
# mount
/fs/rwdata/ppsp on /ppsp type PPS
/dev/blk/ram-0-alloc-0-tmp on /fs/tmpfs type tmp
/fs/images/map_ext.img on /fs/sd/MAP type qnx6
/fs/images/map_eus.img on /fs/sd/MAP type qnx6
/fs/images/map_eue.img on /fs/sd/MAP type qnx6
/fs/images/map_euc.img on /fs/sd/MAP type qnx6
/fs/images/map_comn.img on /fs/sd/MAP type qnx6
/fs/images/voice_nav_eucpr.img on /fs/Nuance type qnx6
/fs/images/voice.img on /fs/Nuance type qnx6
/dev/hd0t181 on /fs/rwdata type qnx6
/dev/diagscratch0 on /fs/rwdata/quip/forensics type qnx4
/dev/diagevents0 on /fs/rwdata/quip/events type qnx4
/dev/hd0t177 on /fs/mp type qnx6
/fs/images/station_logos.img on /fs/mp/resources/station_logo/Logo type qnx6
/dev/hd0t180 on /fs/images type qnx6
/var/pps on /pps type PPS
</pre>

== Commands == 

Mountpoint: <code>/fs/mp/ifs</code>
Called from startup script

<pre>
mount -uw /fs/mp/ #remount to RW
</pre>

<pre>
/fs/rwdata/dev/remount_rw.sh # Custom script (available in FMods Tools Package) to mount /fs/mp with RW permissions
/fs/rwdata/dev/remount_ro.sh # Custom script (available in FMods Tools Package) to mount /fs/mp with RO permissions
</pre>

Hardware Info

2024-05-26T22:39:20Z

Admin:

== QNX tools == 
<code>pidin</code>

https://china.qnx.com/developers/docs/6.4.1/neutrino/utilities/p/pidin.html

Display information about the system:
<pre>
# pidin info
CPU:ARM Release:6.5.0 FreeMem:683Mb/2032Mb BootTime:Mar 19 17:35:42 UTC 2023
Processes: 139, Threads: 644
Processor1: 1093648626 Cortex A15 1000MHz FPU
Processor2: 1093648626 Cortex A15 1000MHz FPU
</pre>

<code>uname</code>

https://china.qnx.com/developers/docs/6.4.1/neutrino/utilities/u/uname.html

Return the name of the operating system (POSIX):
<pre>
# uname -a
QNX localhost 6.5.0 2019/12/12-16:00:38CST TI-OMAP5432-Pasa-Ford-Sync3 armle
</pre>

== PASA (Panasonic) tools == 

<code>hwid</code>

Displays info about S3 board.
<code>hwid bt</code> - info about BT stack
<pre>
# uname -a
# hwid
MY=17
RADIO_TYPE=NAVI
NVRAM_SIZE=64GB
RAM_SIZE=2GB
DRVC=0
CPU_FREQ=1000
HW_REVISION=A
</pre>

Hardware Info

2024-05-26T22:37:59Z

Admin:

Hardware Info

2024-05-26T22:30:17Z

Admin: Created page with "== QNX tools ==  <span style="background-color: grey;">pidin</span>"

== QNX tools == 
<span style="background-color: grey;">pidin</span>

MediaWiki:Mainpage

2024-05-26T22:23:46Z

Admin:

Welcome to the FMods.net Sync 3 Wiki platform

MediaWiki:Mainpage-description

2024-05-26T22:22:37Z

Admin:

Main page

MediaWiki:Mainpage

2024-05-26T22:22:27Z

Admin:

Main Page

MediaWiki:Mainpage

2024-05-26T22:22:13Z

Admin:

Welcome to the FMods.net Sync 3 Wiki platform

MediaWiki:Mainpage-description

2024-05-26T22:21:36Z

Admin:

Welcome to the FMods.net Sync 3 Wiki platform

MediaWiki:Mainpage-description

2024-05-26T22:21:12Z

Admin: Created page with "Main page v"

Main page
v

MediaWiki:Mainpage

2024-05-26T22:16:14Z

Admin:

Main Page