| Author |
 Topic  |
|
|
halibatsuiba
USA
2 Posts |
 Posted - 09/23/2008 : 11:54:54
|
Got USB pic programmer last week, downloaded latest sw from MCUMall website.
I can succesfully program 16F84-chips but when I try to program 18F2550, it fails during verify.
I get error message saying "ROM error at 0x0000 Good 0x282B Bad 0x0001".
If I check if chip is erased, sw says EEPROM,ROM and FUSES are not erased, even after succesful erasing of the chip.
(Succesful = sw says erasing went ok)
I can read the contents of 18F2550 and if I do verify after reading, no problems.
If I write the code back to chip, verifying fails with message:
"EEPROM error at 0x001 Good 0xFF Bad 0x9e"
I have tried this with several 18F2550 chips so obviously it is not a chip problem.
Any ideas what is wrong or is my programmer defective? 
I already emailed MCUMall technical support but no answer so far. |
Edited by - halibatsuiba on 09/23/2008 15:11:05
|
|
| Reply #1
ZLM
2945 Posts |
Posted - 09/23/2008 : 16:20:51
|
As long as you can read the chip, the hardware should be fine. That because the Read and Write use same hardware configuration circuit, only the commands are different.
From the result we can see the code part is programmed and verified. Only the EEPROM not verified and you do not use that EEPROM.
You can ingor the error on EEPROM since you do not use it. Try the programmed chip. It will work if your code file is good.
This is the software bug on EEPROM.
|
 |
|
| Reply #2
halibatsuiba
USA
2 Posts |
Posted - 09/23/2008 : 16:47:47
|
quote:
Originally posted by ZLM
As long as you can read the chip, the hardware should be fine. That because the Read and Write use same hardware configuration circuit, only the commands are different.
From the result we can see the code part is programmed and verified. Only the EEPROM not verified and you do not use that EEPROM.
You can ingor the error on EEPROM since you do not use it. Try the programmed chip. It will work if your code file is good.
This is the software bug on EEPROM.
I just tested with 18F4331 and it works fine.
With 18F2550, if I write hex-file to chip and then read the contents of chip, I get totally different data.
I mean: When programming, the data does not go to chip. Every time I read the chip, I get the same hex-data out regardless what I try to program there.
I got yet another 2550-chip and tested with it without any success.
Any ideas what could be wrong? |
|
|
| Reply #3
ZLM
2945 Posts |
Posted - 09/23/2008 : 21:04:54
|
It likes programmer software bug.
Try to select 18F4331 from software but place the 18F2550 on the programmer to write.
Both chip are using same command to write.
|
|
|
| Reply #4
steve34613
3 Posts |
Posted - 12/05/2009 : 07:39:58
|
I too am having problems programming the 18F2550.
I tried you suggestion of selecting the 18F4331
then burn, but it Still Does Not work.
Any other ideas you might have? |
|
|
| |
Topic |
|
USB pic programmer not working properly (18F2550)
Forum Locked
