Unable to erase and program 3233B

[bbbodekar]

Posted on September 13, 2004 at 11:17

Unable to erase and program 3233B

[wdcai]

Posted on May 17, 2011 at 11:59

I also encountered this problem ,the chip is only used several times. I thinks it maybe a bug in upsd. it seems doen't work and breakdown . after a wrong hex file is programmed!

[hg-chen]

Posted on May 17, 2011 at 11:59

What is the final caue to the unable to erase and program 3233B?

[bbbodekar]

Posted on May 17, 2011 at 11:59

Well Kuni, I am still wondering why the chip 3233B should fail if all the necessary precautions regarding the programming have been taken. I am taking similar precautions for 3234A, and it does not fail. I must have reprogrammed it more than 70 times by now.

I had to, unfortunately, switch over to 3234A from 3233B as I lost 3 of the chips in the similar manner, and has taken up considerable amount of time of my project development. If the ST could look into this matter, it would be lot helpful to me, as I still have around 10 good 3233B chips with me. I would also like to know how many members of this forum are using 3233B chips without any problems. Maybe they could put some light on this issue, and tell us what all precautions they are taking while programming them. Bhushan.

[jdaniel]

Posted on May 17, 2011 at 11:59

I've seen this problem with a uPSD3254A as well. I've never had it get to the point where I couldn't recover a chip, however. I seemed to be able to get around the problem by performing a hardware reset (with a wired-in switch) and starting the Program All cycle from flashlink immediately after that. I'd have to fiddle around a bit with it before I finally caught it in time. Also, I determined that it ALWAYS had something to do with my firmware, because I identified certain object files that would cause this problem after programming and others that just wouldn't.

One of my theories at the time was that the chip might malfunction if the watchdog timer was resetting it frequently. Other than that, once I was past the problem myself I didn't have much motivation to look into it further. I suspect, as it seems others do as well, that this is a bit of a glitch with the chip and it's somehow possible to be using/abusing resources within it that it needs for JTAG programming. At the very least, I would say that this is not isolated to the 3233.