Home/Microchip

Products designed on Microchip silicon.

★★★★★ 4.9 Rated on Google Inc. 5000 honoree · ISO 9001:2015

PIC, AVR, SAM, and dsPIC firmware and hardware on one team. From MPLAB X projects to populated boards, our engineers have deep experience designing with Microchip microcontrollers, and they take real products through to assembly.

  • PIC18, PIC32, ATSAM, dsPIC33 expertise
  • MPLAB X and Harmony 3 framework
  • Microchip-recommended toolchains
  • Schematic to firmware to assembly
They trust us Tesla NASA Raytheon Virgin Intel Universal
Certifications & Awards ISO 9001:2015 THEA Award Inc. 5000 Growth Badge
What we deliver

Hardware and firmware on one team.

Microchip-based products from concept to mass production, with one accountable engineering group.

MCU selection

PIC18, PIC32, AVR, ATSAM, or dsPIC33. We pick the right family for your power, peripheral, and cost targets.

Firmware in MPLAB X

Production firmware in C, using MCC, Harmony 3, or bare-metal. Driver code, RTOS integration, and OTA updates.

PCB around the chip

Microchip reference schematics adapted to your product. Layout, DFM review, and prototype fab in 5 to 12 days.

Bring-up & production

Bench bring-up, SMT line, programming fixtures, and functional test. From 10 prototype units to 100K production runs.

How we work

Spec to shipped product.

Four stages, no surprises. Every milestone has a deliverable you can review.

01

MCU and architecture

We map peripherals, memory, and power against your spec. The Microchip family choice falls out of the requirements, not the other way around.

1 week
02

Schematic and firmware kickoff

Reference designs become production schematics. The firmware skeleton is set up in MPLAB X, with peripheral drivers in place before the board returns from fab.

2–3 weeks
03

Prototype and bring-up

Five to twelve day prototype turn. The same engineers who routed the board run bring-up and bench validation.

2 weeks
04

Production and programming

SMT assembly, in-circuit programming via PICkit or ICD4, and functional test on every board before ship.

3–6 weeks
Microchip stack

Families and tooling we run.

If it ships in a Microchip catalog, we have probably designed with it. Here is where each family typically lands.

Chip familyTypical use
PIC (8-bit: PIC10/12/16/18)Cost-sensitive control, simple sensors, and low-pin-count embedded tasks
AVR (ATmega, ATtiny)Fast 8-bit control, Arduino-lineage designs, and tight code-space projects
PIC24 / dsPIC33 (16-bit)Motor control, digital power, and DSP-heavy signal processing
PIC32 (MX/MZ/CM, MIPS & Cortex-M)High-performance MCU work: connectivity, graphics, and data logging
SAM / ATSAM (Cortex-M0+/M4/M7)Arm-based products, higher throughput, and richer peripheral sets
Toolchain & programmersMPLAB X, XC8/XC16/XC32, Harmony 3, MCC, PICkit 4/5, ICD4, Atmel-ICE
FAQ

Common questions about Microchip projects.

Toolchain, support, and what to expect when you start a project with Jaycon.

Which Microchip families do you specialize in?

PIC32MX and PIC32MZ for high-performance MCU work, PIC18 and AVR for cost-sensitive 8-bit, and dsPIC33 for motor control and signal processing. ATSAM Cortex-M parts are also in regular use.

Do you write firmware in MPLAB X?

Yes. MPLAB X with XC compilers is our default. We use the Harmony 3 framework for complex peripheral code and bare-metal C when footprint matters.

Can you migrate firmware between Microchip families?

Yes. We have ported between PIC18 and PIC32, and between AVR and ATSAM. The peripheral abstraction usually allows a clean migration with bounded effort.

How do you program parts in production?

In-circuit programming via PICkit, MPLAB ICD4, or Atmel-ICE during functional test. We also build custom programming fixtures for high-volume runs.

Have a Microchip project?

Upload your spec or schematic and get a quote in minutes.

Get an Instant Quote