Programmable Display Volatile Memory Debugging
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Debugging of screen data on programmable displays is inefficient due to the need to repeatedly transfer and verify data between nonvolatile and volatile memory, requiring connection to a screen data creation device and taking significant time, especially when errors need to be corrected.
Innovation Solution
A programmable display that allows direct storage of control screen data for debugging in volatile memory, eliminating the need for transfer from nonvolatile memory, enabling independent debugging without the screen data creation device.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If screen data is transferred to nonvolatile memory for debugging, then data can be stored persistently, but debugging time increases due to repeated write and load operations
Solution Approach 1:
The patent applies preliminary action by pre-loading screen data into volatile memory before debugging operations begin. The controller loads screen data from nonvolatile memory into volatile memory in advance, so that subsequent debugging operations can access data directly from volatile memory without repeated write-load cycles, thus reducing debugging time while maintaining data persistence
2Manufacturing precision
If screen data is repeatedly written to and loaded from nonvolatile memory during debugging, then verification can be performed, but the process becomes time-consuming
Solution Approach 1:
The patent introduces another dimension by implementing a dual-memory architecture where screen data can exist in both nonvolatile memory (for persistence) and volatile memory (for rapid access). This dimensional separation allows the system to maintain verification accuracy through persistent storage while achieving higher debugging efficiency through fast volatile memory access, effectively solving the contradiction between verification accuracy and debugging efficiency
3Stability of the object's composition
If screen data is stored in nonvolatile memory, then data retention is ensured, but access speed during debugging decreases
Solution Approach 1:
The patent applies segmentation by dividing the storage system into two distinct segments: nonvolatile memory for data retention and volatile memory for fast access. Screen data is segmented between these two storage types, with the controller managing which segment is used for which purpose. This segmentation allows the system to simultaneously achieve data retention through nonvolatile memory and high access speed through volatile memory, resolving the contradiction between stability and speed
Data Source
AI summary
A programmable display includes a display, a volatile memory, a nonvolatile memory that stores control screen data containing screen data, and a controller that loads the control screen data from the nonvolatile memory into the volatile memory at startup and displays a screen on the display on the basis of control screen data loaded into the volatile memory. The controller has a function to store the control screen data received from a screen data creation device in the nonvolatile memory and a function to store the control screen data received from the screen data creation device directly in the volatile memory.