I’m maintaining and hosting now more than 100 different Processor Expert components on GitHub. Instead to deal with CDE (Component Development Environment, that’s the SDK to create your own components), most users simply download and install the PEupd files. If you deal with normal source files, and if spot something you want (or need to change), then you can easily do this. But what if you want or need to change something in that code which comes with the PEupd file(s)?
The thing is: You can easily make changes in the component source code yourself too. It is just that you need to know where the files are installed.
User Working Directory
The *.PEupd files are kind of ‘self extracting zip files’. Importing the *.PEupd will place the sources files in a special ‘working directory’. That directory might depend on the Processor Expert version used. For my CodeWarrior version (10.5) it is in
User working directory = C:\ProgramData\Processor Expert\CWMCU_PE5_00
as reported in the Console view. See “Locating the User Working Directory” for details.
has folders for each component (aka Beans). So you know what has been installed. It has files for interfaces (*.int) and other things. I recommend to have a look at “CDE Hacking: Where is my stuff? A dissection…” to get an overview about all the different files and folders. In the beans file you need to deal more with XML files. If you are familiar with this, you can make easily changes or extensions here.
The source files are inside
For ‘simple’ Processor Experts, the source code driver is inside
The source code is inside the *.drv file for each component (e.g. RingBuffer.drv is the driver for the RingBuffer component). The driver is written in C with some Processor Expert specific extensions. So you can make easily small changes in the driver.
More complex components like FreeRTOS or the USB stack which consist of multiple files are using ‘external’ files. The files are located in folders like
These are pretty much normal C files with some very small stuff added for Processor Expert. You should be able to spot the right file very easily.
💡 If you are interested in how these files get copied into your project by the component, have a look at the *.prg files inside the ‘Drivers’ folder.
Make sure you are using a normal text editor (aka Notepad or similar) to edit the files. In general you can use any text editor (as the driver files are normal text files), including Eclipse.
The above instructions are for ‘user’ components as I offer them, as all the files are open and easily accessible. It does not work for the components delivered by Processor Expert as they are ‘closed’ and not accessible. But with the above steps, if you run into a small (or larger problem) you can easily experiment or make a fix yourself. Just make sure you have a backup if you screw things up (but you still have my GitHub site 😉
💡 If you see something which needs to be fixed or changed, then let me know (if you prefer to contact me by email, see the About page). Otherwise post a comment 🙂
Happy Modifying 🙂