Do you want to use Codewarrior for MobileGT 9.2 under Linux for debugging/developing to MPC5125?

The stock installation of the CW did not supports the MPC5125 and the MPC5123. You can download an upgrade to support these CPUs, but it is available for windows only. No problemo, after running some cabextract I was able to extract the upgrade contents. After some directory renaming and restructuring I had created the same directory structure as my Linux CW installation has.

The next archive could be extracted to the CodeWarrior main folder. (In my case this was the
/opt/Freescale/MGT-9.2/CodeWarriorIDE/CodeWarrior)

It will overwrite two files. Backup them before doing it this.
http://dl.dropbox.com/u/4295670/crio/Co ... PC5125.rar

Good luck to everyone who is using this stuffs!

The Freeescale support was very gently, so they are provided a free replacement for my dead USB-TAP. Of course I have disassembled it to check that did they added ESD protection to the USB lines.
Yes they did:

Let's get started with two pictures of the Freescale Codewarrior USB-TAP's PCB:




Read more...

1.Add the folowing to pro file:


OBJECTS_DIR = build
MOC_DIR = build
UI_DIR = build
RCC_DIR=build

DESTDIR = bin

and the binaries won't mess up your sorce code directory

2. Make the following modifications in the main.cpp:


#include <QtGui/QApplication>
#include <QtCore/QTextCodec>
#include "mainwindow.h"

int main(int argc, char *argv[])
{
QTextCodec::setCodecForCStrings(QTextCodec::codecForName("UTF-8");
QTextCodec::setCodecForLocale(QTextCodec::codecForName("UTF-8");

QCoreApplication::setOrganizationName("MM";
QCoreApplication::setApplicationName("Mikrotik data miner";
QCoreApplication::setApplicationVersion("0.1";

QApplication a(argc, argv);
MainWindow w;
w.show();
return a.exec();
}


Why?
The QTextCodec trick is neccessary because the sourcecode is UTF-8 encoded, and if I want to put a string from the code to somewhere I would need to use QString::fromUtf8(). If you do not believe check a generated ui_*.h file.

Always give set the name to your application and the application domain. This is useful when you are using QSettings, you do not need to give constructor arguments when creating a settings object. The settings object constructed in this way always use a separate data area specified by the platform. (.config/QCodeApplication::applicationDomain/QCoreApplication:applicationName.ini on Linux and registry on Windows)

Recently I had a project which was based on a 18F series PIC.
According to the "The well known ecosystem improves the productivity" motto I have decided to do the development on my Linux box.

After a while I have noticed that there are not any usable enviroment for 18F development on Linux. I have tried the MPLAB on windows too, but the "ignore all well known gui actions (doubleclick on code makes breakpoint for e.g.)" idiot behaviour driven me crazy. The Piklab is an unstable stuff, the MPLAB X is a java based slow bullshit, which does not supports ICD2, Piklab2.

I have decided to setup an enviroment using GNU make. The Makefile below can be used with the Linux version of MCC18 compiler.

Read more...