Flashing with a Button (and a Magic Wand)


In eclipse and CodeWarrior for MCU10 the usual thing I do is:

  1. I have a project in my eclipse workspace
  2. I compile and build it
  3. I download and flash it to the target for debugging

If I need to program another board with the same binary, then I download it to that board too. Fine. But what if I want to skip point 1 and 2? What if I do not have or want a project? All what I have (and need) is a binary file, and I want is to flash that file to my boar. By pressing a button.

No project, just the naked workspace

Eclipse is very project oriented. But with the release of MCU10.2 it is possible: I can program my boards without a project . All what I need is the binary file I want to flash. Really? Well, close. Some setup is still required.

In the following steps I’m using a new and blank workspace. The same thing can be used with projects in the workspace too. Then things are even easier as I can re-use settings. But here I’m going to do the heavy metal stuff naked, without a project, but with a Magic Wand. Actually, it is a Magic Blue Flash Bolt :-).

To start, I use the ‘Flash File To Target‘ menu:

Flash File To Target Menu

Flash File To Target Menu

This gets me the following dialog:

Flash File To Target Dialog

Flash File To Target Dialog

Oh, and here is it: it ask to create a ‘System’….. OMG!

System, Connection, Target or what the ….?

System? Yeah, that’s a very overloaded term (like many others). I would explain an MCU10 ‘System’ as a combination of ‘Connection’ and ‘Target':

  • The ‘Target‘ specifies the CPU used (e.g. MCF51JM128), with its initialization script (if any) and the memory configuration needed (if any).
  • The ‘Connection‘ references a the target, plus it holds the settings how I connect to the target, with the Interface and settings for it, e.g. P&E USB Universal Multilink.
System with Connection and Target

System with Connection and Target

Both the Target and the Connection are listed in the Remote Systems view:

Remote Systems View

Remote Systems View

The Flash File to Target needs a Connection. So we need to create a Connection and a Target.

Creating a Connection

Pressing the ‘New…’ button in the Flash File to Target dialog gives me:

Hardware or Simulator Connection Dialog

Hardware or Simulator Connection Dialog

Ok this is the Connection. Here I can configure the connection settings, and create a new Target.

Creating the Target

To create the ‘Target’, I’m pressing ‘New…’ in the New Connection dialog:

New TARGET Dialog

New TARGET Dialog

This is the Target (don’t get confused by the dialog title!!!). Ok, you are confused. But this is really the Target. Here I specify the CPU (MCF51JM128 in my case). Having this defined, it allows me to change further settings:

New Target with Initialization Part

New Target with Initialization Part

I do not need any Initialization or Memory configuration, so I keep these with the defaults.

Back to the Connection dialog, I choose to use the P&E connection:

Selecting P&E Connection

Selecting P&E Connection

This expands the dialog for the run control specific settings:

New Connection with Run Control Specific Settings

New Connection with Run Control Specific Settings

Now I have my connection and target created from the ground up.

Next I’m browsing for my binary file to be programmed to the board:

Ready to flash the file

Ready to flash the file

The file is an ELF/Dwarf file or an S19 one.

Pressing the ‘Erase and Program’ button does what it says: it does a mass erase of my device and programs it with the file. If I need to erase/protect only part of my device, then Programming part of Flash provides the needed information.

Time to wave the wand (or flash bolt): Progress is reported in a dialog window, and as well in the console view.

Executing flash programming

Executing flash programming

At the end, the dialog closes automatically (why? what if I would like to flash the file again?). The completion of the operation is reported in the Console view:

Flash Programmer Console

Flash Programmer Console

Dissection of what is behind

Ok, things are working. Time to check out what is behind. As there is no project, the settings have to be *somewhere*. I notice that I have an LC for Simple Flash in the list of Launch/Debug configuration:

LC for Simple Flash

LC for Simple Flash

CodeWarrior is using a pseudo ‘Connect’ configuration to store the information.

Note: While this looks like a normal ‘CodeWarrior Connect’ launch configuration, it will not work as such (if I want to use it directly), as it has no project folder associated.

This launch configuration is stored inside the workspace as a normal file:

.metadata\.plugins\org.eclipse.debug.core\.launches\LC for Simple Flash.launch

So while this is not really a normal launch configuration, it is still useful to know about it.

Summary

Using the Flash File to Target menu and button makes it really easy to flash a file to the board without the need for a project. Still, for a naked workspace, some settings are required which take a little time to set up. With knowing the things behind, no magic wand is needed, as long as it creates systems, connections, targets or whatever their names might be ;-)

Happy Button Flashing :-)

21 thoughts on “Flashing with a Button (and a Magic Wand)

  1. Pingback: USB CDC goes medical | MCU on Eclipse

  2. Pingback: Standalone Flash Programmer | MCU on Eclipse

  3. Pingback: Changing the CPU with Processor Expert | MCU on Eclipse

  4. Pingback: Hot-Sync: Attach, Connect & Download | MCU on Eclipse

  5. Pingback: Copy my CodeWarrior Project | MCU on Eclipse

  6. Pingback: Unsecuring the KL25Z Freedom Board | MCU on Eclipse

  7. Pingback: How (not) to Secure my Microcontroller | MCU on Eclipse

  8. Just to experiment, I created a project and wrote a program to blink an LED on TWR-KL25z board. The code works fine and I see the LED blinking. Then I removed the project from my workspace and followed the steps in the post. Target is KL25z128m4 with no memory or target initialization. Connection is openSDA.
    For the file to flash I chose the .elf file from the project and clicked on erase and program but I’m getting an error”Executing task KL25Z128M4 has encountered a problem” and “an internal error occured during executing task KL25Z128M4″… So can you please help in programming/button flashing?

    Like

    • Uff! I’m sorry. The problem this code warrior creates!!
      I restarted the codewarrior. Now it is programming. But the new issue is I have to press the reset button after programming successfully once to start LED blinking. Any light you can throw why this is happening

      Like

  9. Hello Erich,

    I have a question Regarding Flash Button Programming.
    I tried the above method to program MC9S08RN8 Freescale Controller , it is successful but the problem is the default value of Trim Register ICS_C3 and Fine Trim ICS_C4 , i am not getting correctly, i don’t know why, Here what i did

    1) First i programmed controller using Debugger method , without controlling Trim register in my code and i got the Total time of PWM of 11 msec (For the PWM code which i have written using Timer) , after POR (Power on Reset) i got Total PWM time of 12 msec.I posted the question on Freescale community and got the suggestion that may be Debugger is writing the Trim Register.
    2) So i added Trimming Register control code in my main code the problem is solved . The following code i added for Trim register

    if ( NV_ICSTRM_INIT != 0xFFU) { // 0xFF6FU Test if the device trim value is stored on the specified address

    // ICS_C3 = *(uint8_t*)0xFF6FU; // Initialise ICS_C3 register from a non volatile memory
    // ICS_C4 = (uint8_t)((*(uint8_t*)0xFF6EU) & (uint8_t)0x01U); // Initialise ICS_C4 register from a non volatile memory

    ICS_C3 = NV_ICSTRM_INIT;
    ICS_C4 = ((NV_FTRIM_INIT) & 0x01U); // Trim the internal clock :((NV_FTRIM_INIT) & 0x01U);

    }

    After adding the above Trim register control code i got the same PWM Total timiming of 11msec before and after the Power on Reset.

    3) Actually i wanted to program the controller without Trim register control code so i used your method , but with your code also i am getting the Total PWM timing of 12msec with and without Trim Register Control code.

    can you please suggest me do i need that Trim register control code or not in both the programming cases and Which method is correct for programming on Timing delay point of view?

    Thanks and Kind Regards,
    Robin

    Like

    • Hi Robin,
      I have not checked your device, but from what I can tell is that the TRIM values are loaded from a special location in FLASH and then stored in a RAM register.
      If so, then you need to make sure that these values are copied from FLASH to RAM at runtime (in your application). It looks like you are doing that (with the copy from 0xFF6F). This means that you need in your application the flash programmed at that location with the value you need.
      Erich

      Like

      • Hello Erich,

        one more Question:- Why trimming value with flash button programming is 31250 hz instant of 39062 hz which is factory trim value, even though i am not changing the trim value in “RUN CONFIGURATION” ?

        can i see somewhere µC Bus frequency while programing using flash button , like in Debugger programming it shows me in console.

        I am using Codewarrior 10.5
        µC : MC9S08RN8
        Progrommer : PE Micro USB Multilink

        Thanks and Kind regards,
        Robin

        Like

      • I’m not sure, but I would say that this value comes from the run configuration which you have selected for the flash button programming.

        Like

      • Respected sir
        I have question related to flash code in XBEE SMT module have MC9S08QE32 microcontroller.

        Sir, ‘Flash File To Target‘ menu can not be show in Code warrior 10.2 with XBEE SDK.

        I have use directly use sample code of give in CodeWarrior 10.2 with XBEE SDK . I am select “Xbee sample application project ” in that next select my device Xbee 865/868 lp S8 module next i have have to select GPIOs project in that i have select blink_led project. Then i have to build that project. After that i have go to run configure then in connection type i have select “P & E HSS08 Multilink \ Multilink Universal \ Cyclone Pro \ OSBDM ” then i run that project but i got “POWER CYCLE DIALOG” after click ok then i get this window “p&e connection ” .

        please give me solution of my problem.

        Like

      • Hello,
        CodeWarrior 10.2 is very, very old. The current version is 10.6. It could be that this menu item has been added later, so I highly recommend that you move to version 10.6.

        Like

  10. I also think so but when i am doing changes in trim frequency for run configuration for selected flash it’s not taking the changed trimmed value, don’t know why?

    Like

  11. Pingback: Unlocking and Erasing FLASH with Segger J-Link | MCU on Eclipse

  12. Pingback: Tutorial: How to Erase the FLASH with the GNU debugger | MCU on Eclipse

What do you think?

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s