MCU EOL REQUIREMENTS DEFINITION SERVICE
Just Submit Your Source Code.
Get a Requirements Definition Document in as Little as Two Weeks.
MIRAXIA offers a specialized requirements definition service for EOL microcontroller software replacement.When legacy microcontrollers near end-of-life, migration projects often stall because key engineers are overloaded with preparation work. Our service removes that bottleneck.Using only the existing source code as input, MIRAXIA combines microcontroller domain expertise with AI-driven analysis to generate clear, high-quality requirements definition documents.We also provide visibility into design, risks, and WBS, helping teams address both lack of requirements definition know-how and shortage of skilled personnel.
Are You Having Trouble With Any of These Issues?
- The design documents are no longer available, so we don't know where the changes were made.
- The person in charge at the time is no longer with us, so the intent behind the specifications is unclear.
- We're spending so much time dealing with EOL issues that we can't make progress on new development
- The source code is outdated and differs so much from current conventions that it takes time to understand
Miraxia Provides Solutions Like These
By combining Miraxia’s extensive practical expertise in microcontroller domains with its proprietary AI, we achieve “standardization and acceleration.” This enables rapid replacement even with limited personnel, allowing teams to move on to strategy development, while also significantly reducing lead times for subsequent design and migration.
-
Standardization and acceleration of initial response
We can visualize the requirements definition and planning phases—which traditionally took several months—in as little as two weeks.
-
Effective use of resources
This will reduce the internal man-hours required for requirements definition and documentation, enabling engineers to focus on high-value-added tasks and new product development.
-
Reducing development lead time
By identifying the scope of impact and potential replacement microcontrollers early on, it becomes easier to accelerate the design and migration processes
-
Support for a stable supply and long-term maintenance
For long-life products, we mitigate the risk of supply disruptions caused by end-of-life (EOL) status and enable planned product renewal and cost management.
Items to Bring
Please provide only the source code prior to the changes.
- *We also have the user manual for the microcontroller in question available.
Deliverables for the “Item Definition” Service
1. Microcontroller Replacement Development Plan
2. Microcontroller Replacement Resource Allocation Design Document
3. Proposed Microcontroller Models
-
Microcontroller Replacement Development Plan: Sample Content
- Structure of existing source code (directory structure, module structure, list of functions and variables, etc.)
- Identification of microcontroller-specific components (ports, interrupts, timers, memory map, communication interfaces, etc.)
- Definition of the scope of changes and work items, along with an estimate of man-hours and a tentative schedule
-
Sample Content for Microcontroller Replacement Resource Allocation Design Document
- Summary of hardware resources currently used by the existing microcontroller (number of ports, timer/ADC/clock conditions, memory capacity, etc.)
- Proposed resource allocation for the new microcontroller (register mapping table, configuration values, peripheral I/O assignment policy, etc.)
-
Sample Content for the Microcontroller Recommended Varieties Proposal
- Compilation of a list of candidate replacement microcontrollers based on existing source code and the current usage of microcontroller pins
- Comparison of multiple models from major manufacturers (features, resources, package types, etc.)
- Proposal of candidates with future expandability in mind
Price
Starting at JPY 800,000 (excluding tax)
*This may vary depending on the amount of source code and other factors.
Main Areas of Practice
If you are facing difficulties due to the end-of-life (EOL) of microcontrollers used in fields with long product lifecycles that support critical social infrastructure—such as the absence of the original engineers or a lack of documentation—please feel free to contact us.
