TEP Arduino V4.0 Proteus models - feedback on a PlatformIO-to-simulation workflow

Hello everyone,

We’re the team at The Engineering Projects (TEP). We’ve developed a collection of AVR-based Arduino board models for Proteus and would welcome feedback on using them with firmware built in PlatformIO.

The collection includes:

  • ATmega328P boards: Arduino UNO R3, Nano, Pro Mini and Mini.
  • ATmega2560 board: Arduino Mega 2560.
  • ATmega1280 board: Arduino Mega 1280.

Downloads and documentation:

These models use Labcenter’s existing AVR simulation cores to execute firmware. Our additions include board graphics and header connections, interactive reset, activity LEDs, and an integrated UART monitor with plotting.

For an initial UNO example, the PlatformIO configuration would be:

[env:uno]
platform = atmelavr
board = uno
framework = arduino

The proposed workflow is to build with pio run -e uno, then select .pio/build/uno/firmware.hex in the Proteus board’s “Upload Hex File” property, with its clock set to 16 MHz.

These are Proteus libraries installed into Proteus; they are not C/C++ dependencies for lib_deps. The workflow uses a manual firmware-file handoff rather than an integrated PlatformIO upload or debugging connection.

Scope and limitations:

  • Our shipped examples were tested in Proteus 8.5 with Arduino-generated HEX files. We have not yet validated this complete PlatformIO workflow.
  • MCU peripheral behaviour depends on the underlying Proteus AVR model.
  • USB controllers, voltage-regulator behaviour and supply-current limits are not simulated.
  • Reset indicators and startup delays do not constitute a complete bootloader programming simulation.
  • The Pro Mini model represents the 5 V, 16 MHz board.
  • Our ATmega328P tests in Proteus 8.5 showed a pin-change interrupt issue; we have not established its behaviour across other versions.
  • Proteus with the appropriate AVR simulation support is required and is not included.

For anyone already using PlatformIO with Proteus, does this HEX-file workflow work reliably in your setup? Reports including PlatformIO platform/framework versions, Proteus version and a minimal example would help us document compatibility accurately.

These are independently developed TEP models, without endorsement from PlatformIO, Arduino, Microchip or Labcenter.