topic Re: 9s12xDT512 will not program; P&E mulitlink USB V2.0 in CodeWarrior for MCU

9s12xDT512 will not program; P&E mulitlink USB V2.0

blewis — Wed, 31 May 2006 20:53:18 GMT

We are using version V5.7 of CW which is supposted to support the 9s12x parts. We have a board that uses the 9s12DG128B with a Pierce oscillator which works perfectly.

We mounted a 9s12xDT512 on the board and it talks to the BDM but will not program the 9s12xDT512 part. Support suggested the part was bad so we changed it but the new part behaves exactly the same. We can write memory using NoICE, but CW will not write the memory. CW thinks the part is secured, but running the UnSecure program from P&E indicates the part is not secured.

I am beginning to think that this may be a P&E mulilink pod problem. I noted that some one else thought the pod might be a problem. NoICE does not support the programing algorithms yet for the 9s12x part but will in the future so we can't even check if the problem is CW. We only have the P&E prob.

Has anyone experience this sort of problem, and are there any work arounds?

Thanks in advance.

Bob Lewis

Re: 9s12xDT512 will not program; P&E mulitlink USB V2.0

rhinoceroshead — Wed, 31 May 2006 21:10:41 GMT

What crystal frequency are you using? Is it possible that the timing is not correct for the Flash module? My home-made DP512 board uses a 4 MHz crystal and I've never had problems writing to the Flash. I chose that crystal because the DEMO DT512 board used it. I know when you write the Flash run-time in your program you have to ensure the FCLK is within a certain range of frequencies. The programming software may be assuming you are using one crystal and you may be using something different. Just a thought.

Re: 9s12xDT512 will not program; P&E mulitlink USB V2.0

mke_et — Wed, 31 May 2006 21:11:47 GMT

I fail to see how it could be the pod, but I susspose anything is possible.

I'd look to make sure you have the processor type set up right first. When I did my first project, I did all the developement with the 9S12DP256B with a 9S12Badge attached to a wirewrap board. Then chose that part for my project, even though it was overkill.

My second 9S12 project I used the the 9S12DG128 in an 80-pin package. This project was a 'redesign' of an existing project that had a 68HC11 part on it with a WaferScale expansion part. To develope the project, I pulled the CPU and WaferScale parts off an existing and known working board and mounted a 9S12Badge board right next to it, then 'wirewrapped' the two together. However, when my new design board samples came in, I tried to program the DG part and ran into a similar situation to what you described. Eventually I figured out I had to change my CPU type in the ICD-12 'Set Derivative' option and things started falling together.

Re: 9s12xDT512 will not program; P&E mulitlink USB V2.0

blewis — Wed, 31 May 2006 21:18:34 GMT

Thanks for the reply; we are using a 16Mhz crystal. We use CW project expert to build the system, and in there we have specified the freq to be 16Mhz. I think that CW adjusts the programing clocks based on those numbers. I know what you are referring to however, the eeprom has to be also adjusted correctly or it will not program. We used to have that problem with another tool set.

Re: 9s12xDT512 will not program; P&E mulitlink USB V2.0

rhinoceroshead — Wed, 31 May 2006 22:43:39 GMT

Well, I agree with mke - it can't be the POD, otherwise you wouldn't be able to write to RAM either. And with two devices showing the same issue, it's not very likely that both of the chips have bad Flash. Also - a secure chip should not be the problem either - because the BDM can erase a secure chip. Since only the Flash module itself appears to be having problems, that is why I suspected the timing.

I thought the processor expert only wanted to know the crystal frequency so that it could write the proper dividers in software for PLL, ADC, SCI, FLASH, etc. I'm not so sure that it has any relation to timing for the BDM and programming the Flash during development - but I could easily be wrong here. What happens if you open the Hiwave debugger and go to the ICD-12 drop down and select 'Set Communication Speed'. I doubt this will help because it is clearly already communicating. Perhaps someone else on this forum can confirm that it works with a non-4MHz crystal without changing any settings...

You are certain that all of the power pin traces on the board are correct, yes? And also the reset pin is connected to the BDM port? When I built mine, it just worked immediately with no fuss, and still works almost a year later. I've reprogrammed it hundreds of times without the slightest hint of a problem.

Re: 9s12xDT512 will not program; P&E mulitlink USB V2.0

rhinoceroshead — Wed, 31 May 2006 23:24:13 GMT

I just re-read your original post and I think I misunderstood the problem. Are you saying that you had a demo board for an S12 chip and you removed that chip and replaced it with an S12X chip? I'm assuming that you have confirmed already that it is a pin compatible replacement part. Then you say that it does NOT work if you do use CW and the P&E USB programmer that is built onto the S12 demo board? However, it works when you use the 6 pin BDM port on the demo board and program it with a separate BDM programmer and non-CW software? But you say that the built in P&E programmer worked fine with the chip that was there previously?

I would make sure that your application is not taking too much power from the USB host. Maybe you could try going through a powered USB hub instead of taking power from your PC's motherboard.

I can confirm with 100% certainty that CW5.7 and the P&E USB programmer is capable of programming the S12X chips.

Message Edited by rhinoceroshead on 05-31-2006 11:46 AM

Re: 9s12xDT512 will not program; P&E mulitlink USB V2.0

blewis — Thu, 01 Jun 2006 00:21:41 GMT

"Then you say that it does NOT work if you do use CW and the P&E USB programmer that is built onto the S12 demo board?"

No, this is a board we have designed and built; it runs from a 9v powersupply and is regulated down to 5.0v with an internal DC-DC convertor.

I guess I could build another board with a dg128 part, test it and then remove the dg128 and put on a DT512. That would verify the board, just incase we had a problem with the board... I'll try that next week and post. I hope it was a single faulty board, because we have to change the board over to 3.3v operation and I can't do that before we get the DT512 part to work at 5v on the same board.

Thanks to everyone for the suggestions.

Bob

Re: 9s12xDT512 will not program; P&E mulitlink USB V2.0

laser — Thu, 01 Jun 2006 15:10:02 GMT

Hi,

I have exactly the same problem using a 9S12DP512 part on three prototype boards, 16Mhz Pierce and mulitilink v2.0. I can program the device, debug the device if XCLCKS is high but i can not attach and debug with XCLKS low i.e. using the 16Mhz clk the P&E cannot detect the speed. The device works fine with XCLKS low and boots and runs code as it should with out the BDM attached i.e. the 16 Mhz clk is ok and the PLL locks as code would halt waiting for lock. Not sure if its a P&E thing or a 512 device thing as i have a 256 demo board which works fine. Will try today to run my board with 4Mhz clk (as per the demo) and se what happens, also i have orderd samples of the 256 devices to put on my boards. Let me know if you find anything out, i will do like wise.

Cheers

Adam

Re: 9s12xDT512 will not program; P&E mulitlink USB V2.0

laser — Thu, 01 Jun 2006 17:14:13 GMT

changed xtal to 4mhz and everything is fine!!!!! tool or mask problem with 512 devices running with 16mhz pierce

Re: 9s12xDT512 will not program; P&E mulitlink USB V2.0

blewis — Thu, 01 Jun 2006 19:16:15 GMT

I don't think my post went through so here it is again.

I think you are right about this being related to the tools. I can try tying xclks high again but I don't think it will all the Pierce oscillator to run; I think I tried that and the BDM would not connect.

I don't have a 4mhz crystal or all the components for the oscillator cct at 4mhz. I am not even sure of the values; did you just solder a 4mhz crystal inplace of the 16?

We are sending the dt512 board to someone in Freescale support at the end of the week with another project. Suppoert is supposed to look at this and get back to us. I will let you know what happens but I think it will take a couple of weeks.

Best Regards

Bob

Re: 9s12xDT512 will not program; P&E mulitlink USB V2.0

laser — Thu, 01 Jun 2006 19:21:57 GMT

Hi,

I just replaced the 16Mhz device with the 4Mhz device i desolderd fro my demo board. I did not change any other components and every thing nows works as it should, but IT will not work at 16Mhz

Cheers

Adam

Re: 9s12xDT512 will not program; P&E mulitlink USB V2.0

mke_et — Thu, 01 Jun 2006 23:09:39 GMT

Have you tried telling it to do it's resync and recalculate the io_delay_cnt? I seem to recall you set a check to recalculte connection speed, but I'm not infront of the system right now.

Re: 9s12xDT512 will not program; P&E mulitlink USB V2.0

rhinoceroshead — Fri, 02 Jun 2006 02:20:16 GMT

Is the BDM not connecting at all with 16 MHz or is it connecting, but not writing to Flash?

I believe they usually recommend 10-30pF capacitors on each end of the crystal to ground. You probably can use the same ones that are already there and just replace the crystal.

Message Edited by rhinoceroshead on 06-01-2006 02:22 PM

Re: 9s12xDT512 will not program; P&E mulitlink USB V2.0

blewis — Fri, 02 Jun 2006 03:15:24 GMT

The BDM will connect fine, and I can write and read RAM if I use NoICE. I can not read or write RAM with CW, but if I write the RAM with NoICE then start CW, I can see that the RAM is written correctly. CW will have nothing to do with the device because it thinks the part is secured and as I said previously I think, we have run all the unsecure programs and it is not secured.

No we can not flash the device. That is where the BDM fails. I don't have a 4mhz crystal, I might have an 8mhz I could try. I will look and see.

The oscillator caps are 22pf and 1nf to ground across the xtal. That configuration works on three other boards that we have so I think the values are ok. We have a 1M resistor as per the doc set.

Regards

Bob

Re: 9s12xDT512 will not program; P&E mulitlink USB V2.0

Sten — Fri, 02 Jun 2006 11:56:33 GMT

I haven't had this problem because I have a 4 MHz oscillator on my target board, but just a perhaps stupid question; have you checked that the CLKDIV is correct in the CW debugger command file (..\cmd\P&E_Multilink_CyclonePro_Erase_unsecure_hcs12.cmd)?

Re: 9s12xDT512 will not program; P&E mulitlink USB V2.0

burra — Fri, 02 Jun 2006 13:17:32 GMT

Hi,

I have experience the same problems. We have a softec evo card (SK-S12XDP512-A) and we can program that one with no problem with both 4 and 16 Mhz crystal / clock. The softec card has silicon mask 0L15Y cpu. We also have a KOPF s12x card that one have the same cpu but with the silicon mask 0L14V and only a 16 Mhz crystal. We are using the P&E USB-ML-12 V2. to program the KOPF evo card. The project is made with Codewarrior for HC12 v.4.1

The project is working ok on the softec card but when we connenct the KOPF card we can program it but when we try to run the code we get illegal brake point even when we don't have any brake points.

The softec card have the possibility to dissconect the onbord USB->BDM an connect a external. So I have tried to connect the P&E to the softec card. That works without problem in 16 Mhz.

I have also tried to run a singel core project using codewarrior and P&E in 16 MHz on the KOPF card. That works ok. But if I make a dual core project with codewarrior, P&E, 16 Mhz and KOPF card. It don't work.

I have also tried to use the onboard USB->BDM from the softec card to debug and program the KOPF card and that gives the same errors as with the P&E tool.

Can it be that it is some differance between the 0L15Y and 0L14V. That or that Codewarrior writes code that is not compatible with the older chip.

Anybody that can verify my thoughts ?

//Bertil Bäck

Re: 9s12xDT512 will not program; P&E mulitlink USB V2.0

Steve — Fri, 02 Jun 2006 15:05:29 GMT

Burra, there are a few differences between the L15Y and the L40V mask sets so it is likely that is where your problem lies. Most importantly the XGATE configuration and initialisation is different and code for the L15Y probably won't work for L40V. Other differences include: XGATE access to flash is only on L15Y; XGATE instruction set changes; RAM is larger on L15Y; unused pins on EBI can be used as I/O on L15Y; the API uses smaller step sizes; chip selects are different.

If I remember correctly the CW 4.1 release is only for maskset L15Y and later and 4.0 is required for L40V.

Message Edited by Steve on 06-02-2006 09:12 AM

Re: 9s12xDT512 will not program; P&E mulitlink USB V2.0

burra — Fri, 02 Jun 2006 17:08:23 GMT

Hi,
found the same as you wrote in the Codewarrior help aswell (RTFM). The big problem now is where I can get hold of the Codewarrior HC12 v.4.0 Can't find it anywere.

Would be grateful for help.

//Bertil Bäck

Re: 9s12xDT512 will not program; P&E mulitlink USB V2.0

CrasyCat — Fri, 02 Jun 2006 19:49:31 GMT

Hello

Can you send me a private message with your email address and I will place a self extractable exe file with V4.0 on FTP for you.

CrasyCat

Re: 9s12xDT512 will not program; P&E mulitlink USB V2.0

bigmac — Sat, 03 Jun 2006 08:32:30 GMT

Hello Bob,

blewis wrote:

The oscillator caps are 22pf and 1nf to ground across the xtal. That configuration works on three other boards that we have so I think the values are ok. We have a 1M resistor as per the doc set.

Are you actually saying that there is a 1nF capacitor between one end of the crystal and ground? I would suggest 22pF for both capacitors, assuming a Pierce oscillator configuration.

Regards,
Mac