802500B9 while writting in battery eeprom
802500B9 while writting in battery eeprom
I have a 802500B9 error when writting at 0x14 in the battery eeprom, does someone know what this code means?
--pspZorba--
NO to K1.5 !
NO to K1.5 !
-
Dariusc123456
- Posts: 388
- Joined: Tue Aug 12, 2008 12:46 am
-
SilverSpring
- Posts: 110
- Joined: Tue Feb 27, 2007 9:43 pm
- Contact:
Do you only get errors when writing to address 0x14? All other addresses works?
There have always been problems with writing to a few addresses of the EEPROM (which is why it is not a good idea to do full writes). Just stick to writing to the serial number address. It is not fully known what the data at the other addresses do so you may risk some damage to the operation of the battery.
About the error codes, I don't know the meaning of that one but error codes in the range of 0x80250080 - 0x802500FF are errors returned by the SYSCON µC itself. There is a char value of the RX packet to indicate the return status and if the value is < 0 (ie. from 0x80-0xFF) then there is an error. The SYSCON driver formats it into a nice kernel error code by adding the 0x802500xx bit to it to get the final error code.
You might have a newer battery which is supposed to disable writing to its EEPROM but if writing to other addresses worked ok then I don't think you have one.
@Dariusc123456: if you have a newer PSP with an updated SYSCON µC which disabled raw writes to the EEPROM you would get a 0x80250084 error which means "invalid command" (the WRITE_EEPROM command: 0x73 was taken out).
There have always been problems with writing to a few addresses of the EEPROM (which is why it is not a good idea to do full writes). Just stick to writing to the serial number address. It is not fully known what the data at the other addresses do so you may risk some damage to the operation of the battery.
About the error codes, I don't know the meaning of that one but error codes in the range of 0x80250080 - 0x802500FF are errors returned by the SYSCON µC itself. There is a char value of the RX packet to indicate the return status and if the value is < 0 (ie. from 0x80-0xFF) then there is an error. The SYSCON driver formats it into a nice kernel error code by adding the 0x802500xx bit to it to get the final error code.
You might have a newer battery which is supposed to disable writing to its EEPROM but if writing to other addresses worked ok then I don't think you have one.
@Dariusc123456: if you have a newer PSP with an updated SYSCON µC which disabled raw writes to the EEPROM you would get a 0x80250084 error which means "invalid command" (the WRITE_EEPROM command: 0x73 was taken out).
No, actually, I can since I am able to write at all the other adresses from 0x0 to 0x79 but not at 0x14, and I can change it in a Pandora battery or set it in auto boot mode.
edit: I've just seen your post SilverSpring, you might be right, it's just that I can't write at this address for any reason (damaged part of the eeprom ?)..
edit: I've just seen your post SilverSpring, you might be right, it's just that I can't write at this address for any reason (damaged part of the eeprom ?)..
--pspZorba--
NO to K1.5 !
NO to K1.5 !
Protected part of the eeprom..? From the first tool that did full writes 0x14 was never writeable, and (at least) the last two bytes of the prom are never what you wrote there on the next read. If you didn't know already, the batteries actually have a decent processor of some sort in them that does all sorts of "mysterious stuff."
-
Pirata Nervo
- Posts: 409
- Joined: Tue Oct 09, 2007 4:22 am
