Problem | Possible causes | Possible solutions | Reference Section |
The newly added application screen is not seen on the display. | ‘REGISTER_APPLICATION’ macro is missing. ‘REGISTER_APPLICATION’ macro has incorrect arguments. | Make sure the REGISTER_APPLICATION macro is defined in the screen view and has correct arguments and callback functions defined. | |
The newly added parameter is not seen on the configuration screen. | The screen name argument in the REGISTER_PARAMETER macro is not specified correctly. | Fix the screen name argument in the REGISTER_PARAMETER macro to reflect the correct screen name, specified in the REGISTER_APPLICATION macro. | |
The display does not come up, after downloading the new firmware. | There is a crash or lock up with the new firmware. | Use IAR Embedded Workbench to download the code and debug the issue. In order to revert to the older firmware, set the attribute “2266” to 0 and download the initial firmware version using C# Sample App | |
Creating applications using the Invoke command takes a long time and does not return, after the code regeneration process. | Possible deadlock in the script within TouchGFX, waiting on resource availability. | Use any key to return to the command prompt, delete the Generated folder inside the TouchGFX directory, launch the TouchGFX designer and regenerate the code by clicking Generate Code. | |
The newly added application screen is not displayed in the correct order on the UI. | The Priority argument in the REGISTER_APPLICATION macro is not specified correctly. | Specify the correct number (order) in the Priority argument in the REGISTER_APPLICATION macro. | |
The newly added configuration is not displayed in the correct order on the UI. | The Priority argument in the REGISTER_PARAMETER macro is not specified correctly. | Specify the correct number (order) in the Priority argument in the REGISTER_PARAMETER macro. | |
Code changes are not being reflected in the binary. | The build was not started with a clean operation. | Do a clean followed by a build operation. | |
C# sample app is not displaying any canopy parameters. | The system timed out waiting for the canopy response. This could happen when the canopy code execution starts on the debugger, after the system comes up, especially when there are breakpoints. | Ensure that the canopy responses to messages are completed before placing breakpoints. Once the canopy code is downloaded, reboot and check if the C# sample app is displaying canopy parameters. | |
Bluetooth status icon and battery status icon not showing. | The system timed out waiting for the canopy response. This could happen when the canopy code execution starts on the debugger, after the system comes up, especially when there are breakpoints. | Ensure that the canopy processes all system messages before placing any breakpoints. Once the canopy code is downloaded, reboot and check if the icons are showing correctly. | |
TouchGFX Designer is trying to reload the code updates and is in a state where it cannot be closed. | TouchGFX Designer was open when running the invoke command. | Try closing the TouchGFX Designer If that does not work using the Task Manager, select TouchGFX Designer process and end task. | |
For new Parameters added, the initial values are not consistent with that in REGISTER_PARAMETER definition. | Scanners that are not factory reset will use values that were left behind in flash during prior use. | Perform a factory reset to ensure any old values in flash are erased. | |
While installing the new firmware, after the firmware upgrade, using the C# sample app, missing Red LED activity or continuous Red LED blink for more than 5 minutes, is observed on the scanner. | Firmware installation did not complete successfully. | Repeat the firmware upgrade operation after removing and re-inserting the scanner battery. |
