PCBs & IC PROGRAMMING / BUILD REQUIREMENTS
The board behind
your next release.
Start with the target platform, project file and save requirements. Define the board and programming scope before choosing a sample build.

01 / A USEFUL TECHNICAL BRIEF
Specify the build.
Then select the board.
There is no single board specification for every project. Review the following items with the project team before production.
- 01Target platform
Console or handheld model, region and intended test hardware.
Identify the hardware on which the sample needs to run.- 02Board features
Mapper or board requirements, project-file size and any additional features.
Flag special requirements early for feasibility review.- 03Memory & programming
Approved project-file version, proposed ICs and programming scope.
Agree the file handover and verification requirements.- 04Save requirements
Whether saving is needed and the behavior expected from the finished cartridge.
Confirm the proposed save method and sample checks.- 05Electrical interface
Supply voltage, logic levels and interface requirements.
Component selection and any level shifting depend on the build.- 06Mechanical fit
Shell format, board outline, connector geometry and assembly scope.
Review physical fit with the agreed shell and sample.
02 / DEFINE THE DELIVERY SCOPE
Boards. Programming.
Or a complete build.
Make the quotation clear about what arrives and what still needs assembly.
Explore a complete cartridge build ↗Board scope
Confirm whether the project needs PCB manufacture, populated boards, component sourcing or a specific assembly service.
Programming scope
Define the approved files, IC programming, verification and functional checks required for the build.
Final assembly
Specify shells, labels, screws and retail packing separately if they are part of the order.
THE QUOTE STARTS HERE
A clear brief.
A better starting point.
Share what you know. We can review the open questions together. No project files are needed for the first inquiry.
- 01Platform, hardware & region
- 02Project-file size & board features
- 03Memory, save & sample test needs
Include your delivery country and target date if known.
BEFORE YOU COMMIT
Good questions.
Clearer decisions.
Can you confirm compatibility from the platform name alone?
The platform is a starting point. The target hardware, file, board features and save requirements must be reviewed before a board and sample plan are confirmed.
Do I need to upload my project files with the first inquiry?
No. Describe the platform, quantity and technical requirements first. File transfer can be arranged after the initial project review.
How should I validate the sample?
Agree the console or handheld, boot and gameplay checks, save behavior where applicable, and shell fit. Document changes and approve the final file and sample before bulk production.
BOARDS & PROGRAMMING / PROJECT REVIEW
Define the
hardware inside.
Start with the platform, board reference and work you need. We will review the design, programming and acceptance requirements with you.
Or email sales@retroforgesupply.com