I'm trying to do the exact same thing with a DEMO9S08QG8 board and a MC9S08SH16CWL (soic-28). I use a 15 inch long ribbon cable from the "BDM-PORT" connector to the controller, connecting to the respective Reset, Bkgd, Vcc and Vss pins of the DEMO board and the processor (Yes, I'm mindful of two extra pins between Vcc and Vss in the MC9S08SH16CWL soic-28 package). This cable/comnnection works fine with the QG8's in soic-8 and dip-16 packages I've used.
I'm using Codewarrior 6.2 for the new chip. I've loaded in a QG8 project into 6.2 and did a make and debug with a QG8 to make sure everything is still working, and it is. Based on a suggestion in this thread, I tried loading a QG8 project into the SH16, on the second attempt it asked me if I wanted to program the flash as usual, then said "The trim value could not be set." At least it looks like it connected to the controller.
I stumbled onto these demo boards for the S08SH series:
http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=DEMO9S08SH&fsrch=1The 16/32 demo board is $79, and I'm willing to go for the $99 for the USBMULTILINKBDM, except for the concern already expressed that it's "the same thing" as on the demo boards - specifically, page 26 of this:
http://dkc1.digikey.com/us/en/tod/Freescale/IntroMC9S08QGSeriesMCUs_NoAudio/MC9S08QG_NoAudio.htmlsays the USBMULTILINKBDM is "integrated into DEMO9S08QG8 at no additional cost." But of course if it's truly the same thing as on the DEMO9S08QG8 board then I don't want it, because I know what I've got doesn't work.
But from this thread and my experience, I have no doubt the BDM interfaces on the DEMO boards are
crippled "device-specific," and the USBMULTILINKBDM will operate with the SH16. Perhaps to be technically correct, the wording on that Digikey page should be "device-specific version integrated into DEMO9S08QG8 at no additional cost."