Recent Posts

Hi - For years I've been using Proteus to simulate PIC firmware and hardware by using the MPLAB/MPLABX Proteus plugin. It's been a useful tool in my development workflow. Proteus simulation isn't perfect, but it's saved me a lot of time and solder...

I recently started doing the same with the Arduino IDE and the AVR processors in Proteus. Since there is no plugin to tie the Arduino IDE (or any other Arduino IDEs, like VSCode, PlatformIO, etc.) to Proteus, I generate .elf files from the GCC-AVR compiler and load them directly into the AVR processor on Proteus.

I encountered a number of frustrating issues doing this, but eventually worked through them. I'd like to share my workflow to assist others who may want to do the same, perhaps save someone time or trouble.

Proteus has the ability to set up a firmware project itself. However, I encountered a number of issues when using this. You can set up Proteus to directly use the Arduino IDE compiIer toolchain but I found sometimes sketches would compile in the Arduino IDE but not the Proteus IDE, and I was not able to figure out why (sometimes Proteus couldn't find libraries that were right there). The Proteus system compiles to a hard-to-locate temp directory unless the project settings "Embed Files" box is unchecked, which dumps all the compiler output into the project folder. I also found the Proteus editor and IDE user interface to be awkward. I prefer to develop code in the Arduino IDE, VSCode, or more sophisticated editor suites, and let Proteus do the simulation, not the code building.

Because of these issues, I decided to avoid using the Proteus firmware development environment, and to use the Arduino IDE toolchain directly. Here is the way I've set up my system:

1) Create the hardware schematic in Proteus, using one of the AVR processors.

2) Create the firmware project in the IDE of choice. I prefer to write code using VSCode as my editor and to use the VSCode Arduino Extension to compile the code using the Arduino IDE toolchain. That way I can easily switch from the Arduino IDE to VSCode as desired for different purposes. Some prefer to use the PlatformIO extension in VSCode or Eclipse, that's fine, but I prefer to avoid creating a separate toolchain from the default Arduino IDE toolchain.

3) Edit the Arduino preferences.txt file. This text file is referenced in the Arduino IDE preferences window. Add the line "build.path=(path)", setting the path to wherever you prefer the Arduino build output to be placed (* if anyone knows how to make this path dynamic rather than static so you could place the output in the project folder, I'd appreciate a how-to...*)

4) If you are using VSCode to edit and build the Arduino firmware, edit the arduino.json project file to include the line, "output": "../VSCode_output", to place the Arduino build output into the specified VSCode_output folder.

5) When building for Proteus simulation, instruct the compiler to turn off optimization. If this isn't done, the resulting .elf file will display incomplete code addresses in Proteus, and sometimes even fail to provide a .ino file for debugging purposes.

To do this, preface the Arduino sketch with:

Code:

#pragma GCC optimize ("-O0")
#pragma GCC push_options

...and terminate the Arduino sketch with:

Code:

#pragma GCC pop_options

This will tell the compiler not to perform any optimization. This will result in larger firmware files, so these #pragma lines can be commented out when building and uploading the firmware to the actual hardware.

6) Build the file in the Arduino IDE, VSCode or (your choice). The .elf file will be written to the output folder specifed in item #3 or #4 above.

7) In Proteus, add the .elf file to the processor properties (control-i, "Properties"). Simulate using the Proteus system debugger, as described in the Proteus documentation.

Works well for me. Hope it's helpful for someone else too.

Now if only there were a similar firmware/hardware simulation environment for the ESP8266/ESP32... Wink

	Welcome, Guest. Please login or register. Did you miss your activation email?	August 11, 2020, 08:35:08 20:35
		Login with username, password and session length

11 Electronics / Projects / Re: nanoVNA V2 - a low cost 3GHz open source network analyzer on: August 09, 2020, 09:40:26 09:40
Started by an007_rld - Last post by bobcat1
Hi For most VNA toy's isolation is the main issue , isolating the main circuit and cuplers are essential to accuracy and sensitivity. And isolation require putting the circuit in a farady cage metal box who will increase the total cost Al the best Bobi

12 Electronics / Projects / Developing a self-regulating soldering iron based on induction heating on: August 09, 2020, 02:06:07 02:06
Started by an007_rld - Last post by an007_rld
Very interesting paper; see here: http://www.scielo.org.co/pdf/dyna/v83n196/v83n196a22.pdf

13 Electronics / Projects / Using Proteus to simulate Arduino uising extenally generated .elf file on: August 08, 2020, 11:12:58 23:12
Started by chicowood - Last post by chicowood
Hi - For years I've been using Proteus to simulate PIC firmware and hardware by using the MPLAB/MPLABX Proteus plugin. It's been a useful tool in my development workflow. Proteus simulation isn't perfect, but it's saved me a lot of time and solder... I recently started doing the same with the Arduino IDE and the AVR processors in Proteus. Since there is no plugin to tie the Arduino IDE (or any other Arduino IDEs, like VSCode, PlatformIO, etc.) to Proteus, I generate .elf files from the GCC-AVR compiler and load them directly into the AVR processor on Proteus. I encountered a number of frustrating issues doing this, but eventually worked through them. I'd like to share my workflow to assist others who may want to do the same, perhaps save someone time or trouble. Proteus has the ability to set up a firmware project itself. However, I encountered a number of issues when using this. You can set up Proteus to directly use the Arduino IDE compiIer toolchain but I found sometimes sketches would compile in the Arduino IDE but not the Proteus IDE, and I was not able to figure out why (sometimes Proteus couldn't find libraries that were right there). The Proteus system compiles to a hard-to-locate temp directory unless the project settings "Embed Files" box is unchecked, which dumps all the compiler output into the project folder. I also found the Proteus editor and IDE user interface to be awkward. I prefer to develop code in the Arduino IDE, VSCode, or more sophisticated editor suites, and let Proteus do the simulation, not the code building. Because of these issues, I decided to avoid using the Proteus firmware development environment, and to use the Arduino IDE toolchain directly. Here is the way I've set up my system: 1) Create the hardware schematic in Proteus, using one of the AVR processors. 2) Create the firmware project in the IDE of choice. I prefer to write code using VSCode as my editor and to use the VSCode Arduino Extension to compile the code using the Arduino IDE toolchain. That way I can easily switch from the Arduino IDE to VSCode as desired for different purposes. Some prefer to use the PlatformIO extension in VSCode or Eclipse, that's fine, but I prefer to avoid creating a separate toolchain from the default Arduino IDE toolchain. 3) Edit the Arduino preferences.txt file. This text file is referenced in the Arduino IDE preferences window. Add the line "build.path=(path)", setting the path to wherever you prefer the Arduino build output to be placed (* if anyone knows how to make this path dynamic rather than static so you could place the output in the project folder, I'd appreciate a how-to...) 4) If you are using VSCode to edit and build the Arduino firmware, edit the arduino.json project file to include the line, "output": "../VSCode_output", to place the Arduino build output into the specified VSCode_output folder. 5) When building for Proteus simulation, instruct the compiler to turn off optimization. If this isn't done, the resulting .elf file will display incomplete code addresses in Proteus, and sometimes even fail to provide a .ino file for debugging purposes. To do this, preface the Arduino sketch with: Code: #pragma GCC optimize ("-O0") #pragma GCC push_options ...and terminate the Arduino sketch with: Code: #pragma GCC pop_options This will tell the compiler not to perform any optimization. This will result in larger firmware files, so these #pragma lines can be commented out when building and uploading the firmware to the actual hardware. 6) Build the file in the Arduino IDE, VSCode or (your choice*). The .elf file will be written to the output folder specifed in item #3 or #4 above. 7) In Proteus, add the .elf file to the processor properties (control-i, "Properties"). Simulate using the Proteus system debugger, as described in the Proteus documentation. Works well for me. Hope it's helpful for someone else too. Now if only there were a similar firmware/hardware simulation environment for the ESP8266/ESP32...

16 Others / Invitation Request / Re: [Req] Invite nomi <HELP> on: August 08, 2020, 10:29:21 10:29
Started by nomi <HELP> - Last post by pickit2
Quote from: nomi <HELP> on July 31, 2012, 04:56:51 16:56 I made a donation: 36452389Y1550234M You only bought a door key. you must be Active to Stay. This is a forum not a Hotel.

18 Computers / Graphics and CAD / Re: Solidworks - SolidCAM - CamWorks - 20xx/13/14 ... 32 + 64 bit All Versions on: August 08, 2020, 01:52:35 01:52
Started by jesse - Last post by hosmis
sw2020.sp4.0 torrent and catia2018