|
Hi,
I am having difficulty programming a new target board using MC9S12DP256B processor. This is the first time I have used this particular processor, but for using it on an axiom EVB, which programmes fine. I have been using MC9S12E128CPV in an number of target boards successfully. I use Cosmic C Zap with P&E multilink12. In Zap - Connect I have selected 9S12xx256, and the BDM connection is made ok. The problem is that Zap repeatedly reports Error writing to memory...... When I get through acknowedging the error many times and the flash completes, my target application seems run ok. After I have reprogrammed a few times the target application fails to run, althouth the BDM connection is fine. I made another target board and this seems to show the same fault. It is as if the flash is faulty. I have not had this difficulty with any of my other target boards using MC9S12E128 with Zap - Connect set to 9S12xx128. My circuit is much the same for both processors, but for pin out, the addition of a reset MAX803 and pull-up resistor, and VREGEN connected to 5V on the "DP" processor. Have I got a doggy batch of processors - seems unlikely, what could I had done wrong? -- Andrew Lohmann AIIE Design Engineer PLEASE NOTE NEW EMAIL ADDRESS IS: Bellingham + Stanley Ltd. Longfield Road, Tunbridge Wells, Kent, TN2 3EY, England. Tel: +44 (0) 1892 500400 Fax: +44 (0) 1892 543115 Website: www.bs-ltd.com -----------------------------Disclaimer----------------------------- This communication contains information which is confidential and may also be privileged. It is for the exclusive use of the addressee. If you are not the addressee please note that any distribution, reproduction, copying, publication or use of this communication or the information is prohibited. If you have received this communication in error, please contact us immediately and also delete the communication from your computer. We accept no liability for any loss or damage suffered by any person arising from use of this e-mail. -----------------------------Disclaimer----------------------------- |
Cant program MC9S12DP256B
Started by ●March 8, 2005
Reply by ●March 8, 20052005-03-08
|
I'm new to this, but as a TA for an Atmel based Micro course I've seen similar problems when students changing chips with different flash sizes and forgeting to set the development (codevision AVR) software accordingly. I would check that if you haven't already. Taggart6 --- In , Andrew Lohmann <andrew.lohmann@b...> wrote: > Hi, > I am having difficulty programming a new target board using MC9S12DP256B > processor. This is the first time I have used this particular processor, > but for using it on an axiom EVB, which programmes fine. I have been > using MC9S12E128CPV in an number of target boards successfully. > > I use Cosmic C Zap with P&E multilink12. In Zap - Connect I have > selected 9S12xx256, and the BDM connection is made ok. The problem is > that Zap repeatedly reports Error writing to memory...... When I get > through acknowedging the error many times and the flash completes, my > target application seems run ok. After I have reprogrammed a few times > the target application fails to run, althouth the BDM connection is > fine. I made another target board and this seems to show the same fault. > It is as if the flash is faulty. > > I have not had this difficulty with any of my other target boards using > MC9S12E128 with Zap - Connect set to 9S12xx128. My circuit is much the > same for both processors, but for pin out, the addition of a reset > MAX803 and pull-up resistor, and VREGEN connected to 5V on the "DP" > processor. > > Have I got a doggy batch of processors - seems unlikely, what could I > had done wrong? > > -- > Andrew Lohmann AIIE > Design Engineer > > PLEASE NOTE NEW EMAIL ADDRESS IS: > andrew.lohmann@b... > > Bellingham + Stanley Ltd. > Longfield Road, Tunbridge Wells, Kent, TN2 3EY, England. > Tel: +44 (0) 1892 500400 > Fax: +44 (0) 1892 543115 > Website: www.bs-ltd.com > -----------------------------Disclaimer----------------------------- > > This communication contains information which is confidential and may also be privileged. It is for the exclusive use of the addressee. If you are not the addressee please note that any distribution, reproduction, copying, publication or use of this communication or the information is prohibited. If you have received this communication in error, please contact us immediately and also delete the communication from your computer. We accept no liability for any loss or damage suffered by any person arising from use of this e- mail. > > -----------------------------Disclaimer----------------------------- > |
Reply by ●March 9, 20052005-03-09
|
Taggart6
I think the settings are fine, Cosmic have looked at the Zap connect, linker and map file for me. The first time I ran Zap it was not set correctly. My EVB programmes fine, as does Cosmic's target which they tried for me since my first email. Also voltages look reasonable around my target. Andrew Lohmann taggart62004 wrote: > > I'm new to this, but as a TA for an Atmel based Micro course I've > seen similar problems when students changing chips with different > flash sizes and forgeting to set the development (codevision AVR) > software accordingly. I would check that if you haven't already. > Taggart6 > --- In , Andrew Lohmann <andrew.lohmann@b...> > wrote: > > Hi, > > > > > > I am having difficulty programming a new target board using > MC9S12DP256B > > processor. This is the first time I have used this particular > processor, > > but for using it on an axiom EVB, which programmes fine. I have > been > > using MC9S12E128CPV in an number of target boards successfully. > > > > I use Cosmic C Zap with P&E multilink12. In Zap - Connect I have > > selected 9S12xx256, and the BDM connection is made ok. The problem > is > > that Zap repeatedly reports Error writing to memory...... When I > get > > through acknowedging the error many times and the flash completes, > my > > target application seems run ok. After I have reprogrammed a few > times > > the target application fails to run, althouth the BDM connection is > > fine. I made another target board and this seems to show the same > fault. > > It is as if the flash is faulty. > > > > I have not had this difficulty with any of my other target boards > using > > MC9S12E128 with Zap - Connect set to 9S12xx128. My circuit is much > the > > same for both processors, but for pin out, the addition of a reset > > MAX803 and pull-up resistor, and VREGEN connected to 5V on the "DP" > > processor. > > > > Have I got a doggy batch of processors - seems unlikely, what could > I > > had done wrong? > > > > -- > > Andrew Lohmann AIIE > > Design Engineer > > > > PLEASE NOTE NEW EMAIL ADDRESS IS: > > andrew.lohmann@b... > > > > Bellingham + Stanley Ltd. > > Longfield Road, Tunbridge Wells, Kent, TN2 3EY, England. > > Tel: +44 (0) 1892 500400 > > Fax: +44 (0) 1892 543115 > > Website: www.bs-ltd.com > > > > > > -----------------------------Disclaimer----------------------------- > > > > This communication contains information which is confidential and > may also be privileged. It is for the exclusive use of the addressee. > If you are not the addressee please note that any distribution, > reproduction, copying, publication or use of this communication or > the information is prohibited. If you have received this > communication in error, please contact us immediately and also delete > the communication from your computer. We accept no liability for any > loss or damage suffered by any person arising from use of this e- > mail. > > > > -----------------------------Disclaimer----------------------------- > > > > > > > > * > click here > <http://www.netflix.com/Default?mqso`190075" target="_blank" rel="nofollow">http://us.ard.yahoo.com/SIG9su0c4g/M)8184.6018725.7038619.3001176/D=groups/S06554205:HM/EXP10388643/A%93423/R=0/SIGel9gslf/*http://www.netflix.com/Default?mqso`190075 > > > *>. -----------------------------Disclaimer----------------------------- This communication contains information which is confidential and may also be privileged. It is for the exclusive use of the addressee. If you are not the addressee please note that any distribution, reproduction, copying, publication or use of this communication or the information is prohibited. If you have received this communication in error, please contact us immediately and also delete the communication from your computer. We accept no liability for any loss or damage suffered by any person arising from use of this e-mail. -----------------------------Disclaimer----------------------------- |
Reply by ●March 9, 20052005-03-09
|
Taggart6
I think the settings are fine, Cosmic have looked at the Zap connect, linker and map file for me. The first time I ran Zap it was not set correctly. My EVB programmes fine, as does Cosmic's target which they tried for me since my first email. Also voltages look reasonable around my target. Additionally (since I sent the email above) I have tried programming an MC9S12DG128B using code and settings for another target based on MC9S12E128, but the programming failed repeatedly, but the application runs a bit (it should not run more than a bit anyway because it is meant for another target). I conclude that my circuit is at fault, but what have I missed that is different to an MC9S12E128? Andrew Lohmann taggart62004 wrote: > > I'm new to this, but as a TA for an Atmel based Micro course I've > seen similar problems when students changing chips with different > flash sizes and forgeting to set the development (codevision AVR) > software accordingly. I would check that if you haven't already. > Taggart6 > --- In , Andrew Lohmann <andrew.lohmann@b...> > wrote: > > Hi, > > > > > > I am having difficulty programming a new target board using > MC9S12DP256B > > processor. This is the first time I have used this particular > processor, > > but for using it on an axiom EVB, which programmes fine. I have > been > > using MC9S12E128CPV in an number of target boards successfully. > > > > I use Cosmic C Zap with P&E multilink12. In Zap - Connect I have > > selected 9S12xx256, and the BDM connection is made ok. The problem > is > > that Zap repeatedly reports Error writing to memory...... When I > get > > through acknowedging the error many times and the flash completes, > my > > target application seems run ok. After I have reprogrammed a few > times > > the target application fails to run, althouth the BDM connection is > > fine. I made another target board and this seems to show the same > fault. > > It is as if the flash is faulty. > > > > I have not had this difficulty with any of my other target boards > using > > MC9S12E128 with Zap - Connect set to 9S12xx128. My circuit is much > the > > same for both processors, but for pin out, the addition of a reset > > MAX803 and pull-up resistor, and VREGEN connected to 5V on the "DP" > > processor. > > > > Have I got a doggy batch of processors - seems unlikely, what could > I > > had done wrong? > > > > -- > > Andrew Lohmann AIIE > > Design Engineer > > > > PLEASE NOTE NEW EMAIL ADDRESS IS: > > andrew.lohmann@b... > > > > Bellingham + Stanley Ltd. > > Longfield Road, Tunbridge Wells, Kent, TN2 3EY, England. > > Tel: +44 (0) 1892 500400 > > Fax: +44 (0) 1892 543115 > > Website: www.bs-ltd.com > > > > > > -----------------------------Disclaimer----------------------------- > > > > This communication contains information which is confidential and > may also be privileged. It is for the exclusive use of the addressee. > If you are not the addressee please note that any distribution, > reproduction, copying, publication or use of this communication or > the information is prohibited. If you have received this > communication in error, please contact us immediately and also delete > the communication from your computer. We accept no liability for any > loss or damage suffered by any person arising from use of this e- > mail. > > > > -----------------------------Disclaimer----------------------------- > > > > > > > > * > click here > <http://www.netflix.com/Default?mqso`190075" target="_blank" rel="nofollow">http://us.ard.yahoo.com/SIG9su0c4g/M)8184.6018725.7038619.3001176/D=groups/S06554205:HM/EXP10388643/A%93423/R=0/SIGel9gslf/*http://www.netflix.com/Default?mqso`190075 > > > *>. -----------------------------Disclaimer----------------------------- This communication contains information which is confidential and may also be privileged. It is for the exclusive use of the addressee. If you are not the addressee please note that any distribution, reproduction, copying, publication or use of this communication or the information is prohibited. If you have received this communication in error, please contact us immediately and also delete the communication from your computer. We accept no liability for any loss or damage suffered by any person arising from use of this e-mail. -----------------------------Disclaimer----------------------------- |
Reply by ●March 10, 20052005-03-10
|
I changed the BDM to a P&E Multilink12 parallel BDM instead of my USB
BDM, and the all three target's program fine. I can understand that my E128 does not have a problem as its said to have a better BDM interface, but it is strange that the older EVB seems ok, but not to worry. I will now need to get another BDM interface cable. Andrew Andrew Lohmann wrote: > Taggart6 > I think the settings are fine, Cosmic have looked at the Zap connect, > linker and map file for me. The first time I ran Zap it was not set > correctly. My EVB programmes fine, as does Cosmic's target which they > tried for me since my first email. Also voltages look reasonable > around my target. > > Additionally (since I sent the email above) I have tried programming > an MC9S12DG128B using code and settings for another target based on > MC9S12E128, but the programming failed repeatedly, but the application > runs a bit (it should not run more than a bit anyway because it is > meant for another target). I conclude that my circuit is at fault, but > what have I missed that is different to an MC9S12E128? > >Andrew Lohmann > > taggart62004 wrote: > >> >> I'm new to this, but as a TA for an Atmel based Micro course I've >> seen similar problems when students changing chips with different >> flash sizes and forgeting to set the development (codevision AVR) >> software accordingly. I would check that if you haven't already. >> >> >> Taggart6 >> >> >> --- In , Andrew Lohmann <andrew.lohmann@b...> >> wrote: >> > Hi, >> > >> > >> > I am having difficulty programming a new target board using >> MC9S12DP256B >> > processor. This is the first time I have used this particular >> processor, >> > but for using it on an axiom EVB, which programmes fine. I have >> been >> > using MC9S12E128CPV in an number of target boards successfully. >> > >> > I use Cosmic C Zap with P&E multilink12. In Zap - Connect I have >> > selected 9S12xx256, and the BDM connection is made ok. The problem >> is >> > that Zap repeatedly reports Error writing to memory...... When I >> get >> > through acknowedging the error many times and the flash completes, >> my >> > target application seems run ok. After I have reprogrammed a few >> times >> > the target application fails to run, althouth the BDM connection is >> > fine. I made another target board and this seems to show the same >> fault. >> > It is as if the flash is faulty. >> > >> > I have not had this difficulty with any of my other target boards >> using >> > MC9S12E128 with Zap - Connect set to 9S12xx128. My circuit is much >> the >> > same for both processors, but for pin out, the addition of a reset >> > MAX803 and pull-up resistor, and VREGEN connected to 5V on the "DP" >> > processor. >> > >> > Have I got a doggy batch of processors - seems unlikely, what could >> I >> > had done wrong? >> > >> > -- >> > Andrew Lohmann AIIE >> > Design Engineer >> > >> > PLEASE NOTE NEW EMAIL ADDRESS IS: >> > andrew.lohmann@b... >> > >> > Bellingham + Stanley Ltd. >> > Longfield Road, Tunbridge Wells, Kent, TN2 3EY, England. >> > Tel: +44 (0) 1892 500400 >> > Fax: +44 (0) 1892 543115 >> > Website: www.bs-ltd.com >> > >> > >> > -----------------------------Disclaimer----------------------------- >> > >> > This communication contains information which is confidential and >> may also be privileged. It is for the exclusive use of the addressee. >> If you are not the addressee please note that any distribution, >> reproduction, copying, publication or use of this communication or >> the information is prohibited. If you have received this >> communication in error, please contact us immediately and also delete >> the communication from your computer. We accept no liability for any >> loss or damage suffered by any person arising from use of this e- >> mail. >> > >> > -----------------------------Disclaimer----------------------------- >> > >> > >> > >> >> >> >> >> * >> click here >> <http://www.netflix.com/Default?mqso`190075>" target="_blank" rel="nofollow">http://us.ard.yahoo.com/SIG9su0c4g/M)8184.6018725.7038619.3001176/D=groups/S06554205:HM/EXP10388643/A%93423/R=0/SIGel9gslf/*http://www.netflix.com/Default?mqso`190075> >> >> >> >> >> *>. >> >> -----------------------------Disclaimer----------------------------- This communication contains information which is confidential and may also be privileged. It is for the exclusive use of the addressee. If you are not the addressee please note that any distribution, reproduction, copying, publication or use of this communication or the information is prohibited. If you have received this communication in error, please contact us immediately and also delete the communication from your computer. We accept no liability for any loss or damage suffered by any person arising from use of this e-mail. -----------------------------Disclaimer----------------------------- |
