Support for OSBDM Incorporated into CodeWarrior

[RockyRoad]

CodeWarrior 5.1 is being upgraded to directly support flash programming and debugging using the Open Source BDM (OSBDM08) for the S08 family. Until now, users of the OSBDM08 pod had to manually add the connection during their debugging session. With the release of the CodeWarrior OSBDM service pack, the OSBDM is now available in the selection of connections built into CodeWarrior.

The original OSBDM08 only supported flash programming for a limited number of S08 microcontroller derivatives. The service pack now expands the S08 microcontrollers that can be programmed with the OSBDM08 to include all S08’s currently supported by CodeWarrior 5.1. And future S08 derivatives will be immediately supported when the derivative service pack is released.

The new OSBDM connection in CodeWarrior 5.1 also supports the EValue8 demo board. This low cost tool contains an upgraded OSBDM interface that adds hardware to support programming the RS08 microcontrollers.

In order to use this new service pack, a new version of OSBDM firmware must be installed. The firmware is included in this post and should be programmed into the 908JB16 of your pod. This firmware can be installed on the OSBDM08 hardware that has previously been posted in the 8-bit MCU Forum Downloads or on the EValue8 hardware for the RS08. 

The method for upgrading the firmware of the OSBDM08 pod is outlined in the OSBDM08 manual included in the original download. The method for upgrading the firmware of the EValue8 hardware was in the documentation accompanying that product. For your convenience, all relevant materials and documents for upgrading the firmware in both BDM pods is duplicated in the download for the new firmware. This download can be found with this message.

The OSBDM service pack for CodeWarrior 5.1 can be found at the link Updates and Patches - CodeWarrior for HC08 at www.freescale.com/codewarrior/downloads.

Firmware Upgrade for CW OSBDM patch.zip

Message Edited by RockyRoad on 2006-11-09 09:54 AM

Message Edited by t.dowe on 2009-09-01 09:39 AM

[markslFS]

Hello All,

Can anyone tell me how to get integrated support of OSBDM/USBDM for the RS08KA8 in Code Warrior?
I am using CW 6.1 with the KA8 patch installed.

I can choose KA8 as a device, but the Open Source BDM only appears as a connection for the KA1 and KA2. It does not appear for the KA4 and KA8.

If I use Full Chip Simulation, I can use "set gdi" or "set connection..." (within the debugger) to select osbdm_rs08.dll, and then everything works fine.

I've been able to implement a workaround, by saving the Full Chip Simulation configuration, after manually changing the connection to RS08 Open Source BDM, within the debugger.

Thanks in advance,
Kevin

[glennp]

Should the firmware upgrade also be applied to the DEMO9S08QG8  for example

glenn

[peg]

Hi Glenn,

No!

This demoboard contains a P&E designed BDM (NOT an OSBDM).

The latest firmware for this is within CW. (or perhaps from P&E direct).

Regards

David

[glennp]

Hi

I must say i find this all very confusing after the relative simplicty of PE Micro IDE for HC05 parts.

Anyway, I selected "P&E Mulitlink/Cyclone Pro" in CW5.1

after your reply, and CW updated the firmware in the DEMO board, then connected OK. I was not aware that I had to use the above.

CW then asked if I want to program the Flash, so it's working now.

At this stage, I elected not to program my initial simple  LED on/off code into the DEMO board but I can see I have progressed somewhat.  Finally.

I also have an Evalu8 board, so for that I must upgrade the firmware. There are THREE  S19 files in the ZIP file for OSBDM firmware upgrade.  Do you know which one is for the Evalu8 board?

many thanks

Glenn

[peg]

Hi Glenn,

At first glance the answer seems obvious. The S19 in the Evalue8 folder!

But then I find that this one is IDENTICAL to the S19 in the bin directory under the OSBDM Upgrade folder at 22k and the S19 in the release files folder under the OSBDM upgrade is different at 19k!

I thought maybe the source is the same and there is a switch somewhere to produce code for either type and the Evalu8 version was done last but I can't find the switch after a quick look. But if there is no switch why is source only provided for one type?

Think this is best left for Rocky to enlighten us.

Regards

David

[RockyRoad]

The correct .s19's are the ones in the EValu-8\Firmware folder (opensourcebdm_r6.s19) and in the bin folder of the OSBDM Development_Files tree (opensourcebdm.abs.s19). These are really the same files - the same firmware works on both boards.

The opensourcebdm.abs.s19 in the OSBDM Release Files tree is wrong. The easiest way to see this is by the date (Feb). The correct file should have been copied from the Development Files area before zipping, but didn't. I didn't catch it before posting.

The zip file attached to the original post has been corrected.

Thanks for pointing it out. My apologies for missing it in the first place.

- Rocky

[glennp]

Thanks Rocky

Thanks for clearing up and correcting the .S19 files for upgrade.

I am a little confused also re the directories you mention, here and in the Read_me files. Where are they?

The ZIP file just contains a list of many files.

glenn

"The correct .s19's are the ones in the EValu-8\Firmware folder (opensourcebdm_r6.s19) and in the bin folder of the OSBDM Development_Files tree (opensourcebdm.abs.s19). These are really the same files - the same firmware works on both boards. "

[peg]

Hi Glenn,

This is probably a problem where when you unzip the files you are not specifying to reproduce the original directory structure.

InWinZip:

Click Extract

Then in the extract dialogue be sure to tick "Use Folder Names"

This should fix it

Regards

David

[baddad]

Is anyone else having trouble with this?

When I program a device, it's programming a different memory range than the original OSBDM files and the debugger can not find my hardware.

BadDad

[eckhard]

Hello,

I´m having the same problem. My OSBDM works with the old firmware and setting the GDI, with the new Firmware I only get the message that no BDM hardware is found.

Eckhard

[peg]

Hi all,

Does anybody have this new version going?

I installed it today and it does nothing. No bo bong from Windoze on power up. Put the original version back in and it works as before.

Regards

Peg

[baddad]

It seems to be a problem with the USB driver no longer matching the firmware.

BadDad

[RockyRoad]

I have it working on 2 OSBDM boards here. I've tried a couple of things to see if I can duplicate other people's results.

I pulled the s19 file back from my post (to see if it got corrupted on the web) and reprogrammed my boards. They both still work.

I must admit that I've personally only used a Cyclone Pro to change firmware. So I've gone through the USB ICP process on one of the boards. It worked after that method, too.

I did see that the OSBDM did not get recognized by the PC without R20 connected back after the ICP programming.

I've attached the s19 that I programmed successfully to this post. It should be the same as in the earlier post, but...

Any more info on the failures. David was pretty clear that even Windows wasn't seeing the OSBDM. BadDad, what did you mean about programming a different range of memory?

- Rocky

opensourcebdm_abs_s19.zip

Message Edited by t.dowe on 2009-10-26 05:27 PM

[peg]

Hi Rocky,

My biggest problem was that I forgot that I had modified the old firmware to enable the internal D- pullup.

Once I fitted a temporary external pullup, Windoze now sees a device.

Then my internet connection went down so I went to bed.

While looking in usb.c I also found that you have changed the Vendor IdroductId from 0425:1000 to 15A2:0021.

This is why it doesn't work! We don't have an updated driver to match this.

This morning I tried to hack the existing .inf file and change the ids. This worked in that Windoze now finds a OSBDM thingy but hiwave won't have a bar of it!

Any reason for not using the internal pullup?

Regards

Peg

[RockyRoad]

Peg -

The new drivers are part of the CodeWarrior OSBDM service pack. The new id's should get recognized after the service pack is installed.

- Rocky

[peg]

Hi Rocky,

I am still on CW5.0 so I have not done this yet.

I presume I need 5.1 first.

Perhaps the windows driver should be excluded from the download so as to avoid confusion.

And maybe some instructions rather than referring back to the old (now wrong) version.

I guess if I already had the patch installed it might have happened automatically but we don't know to do this. I think Baddad is just referring to the fact that the JB code used to start at $DC00 and now it starts at the bottom of flash $BA00.

Regards

Peg

[RockyRoad]

Peg -

Yes, you're right. The service pack is for CodeWarrior 5.1. That's the environment that I've been doing the testing.

I'm not sure what advantage there is for using the new firmware with CW 5.0. The changes in the firmware were only there to support CW 5.1 integration of OSBDM and were mostly minor (like the change to the ID -- it was a duplicate of the TBDML id).

The code does take up almost all of the flash now. It has support for the RS08 with the proper external Vpp hardware. (Someday, I may actually get time to layout that board. For now, the RS08 support is only through the EValue8 board.)

- Rocky

[peg]

Hi all,

I now have the OSBDM with update functioning perfectly!

Just fire up hiwave and your online!

It appears that had my hardware been original and had I already had a OSBDM patched version of CW5.1 it would have gone as smooth as silk.

I updated my OSBDM by USBICP by the way.

I wonder what other peoples problems are?

Thanks Rocky

Regards

Peg

[admin]

Hi,
Does anyone know the cause of Port: Undetected in the ICD-Connection manager? shown in the link below

http://img136.imageshack.us/img136/2096/cw2sl6.png

What can I do to make it port detect??

Thanks!

[peg]

Hi Learner,
If you are using a P&E USB Multilink device then this post is irrelevant to both this thread and this forum!
This forum relates to the OSBDM device only!