Hi !
I have soldered 64k EEPROM, JMP2 wire and JP1 connector on my URC-6011 remote. When I am trying to upload/download from the remote, it gives bunch of errors using simple JP1 hardware cable. It is able to pass check interface test. Since the cable works with my RCA-810 remote, that is not the problem. Also, the connections of EEPROM, JMP2 and JP1 are quite good.
The errors it generates are something like :
"No data found in signature"
"Bad checksum at addr $0000"
"There is a conflict at data addr $0023"
Is there anything else that needs to be done after installing EEPROM/JMP2/JP1 ?
Please let me know if you have any idea about what could be wrong.
Thanks in advance,
-vekman
URC-6011B not programming !
Moderator: Moderators
-
jamesgammel
- Exile Island Resident
- Posts: 394
- Joined: Sun Aug 03, 2003 2:48 pm
- Location: Gillette, Wyoming
Extra steps are required for an eeprom larger than 2K bytes. I uploaded a .zip long ago with instructions and helpful files. It's been long enough that I don't remember many details.
I think a 981 reset won't work exactly right with a larger eeprom unless some data is stored in the eeprom first by IR.EXE using the special address found by one of the tools in the zip I uploaded. However, a 981 reset before that won't hurt and may make it easier to start using IR.EXE and confirm the eeprom is working and IR.EXE understands it. If done in that sequence you'll still need another 981 reset later in the process.
I think a 981 reset won't work exactly right with a larger eeprom unless some data is stored in the eeprom first by IR.EXE using the special address found by one of the tools in the zip I uploaded. However, a 981 reset before that won't hurt and may make it easier to start using IR.EXE and confirm the eeprom is working and IR.EXE understands it. If done in that sequence you'll still need another 981 reset later in the process.
-
The Robman
- Site Owner
- Posts: 21890
- Joined: Fri Aug 01, 2003 9:37 am
- Location: Chicago, IL
- Contact:
Also, just FYI, I suspect that the "64k" chip he's using is really an "8k" chip.
64k bits = 8k bytes
We generally refer to chip sizes here by the number of bytes.
64k bits = 8k bytes
We generally refer to chip sizes here by the number of bytes.
Rob
www.hifi-remote.com
Please don't PM me with remote questions, post them in the forums so all the experts can help!
www.hifi-remote.com
Please don't PM me with remote questions, post them in the forums so all the experts can help!
That .zip is in this folder
http://groups.yahoo.com/group/jp1/files/Programs/
I haven't looked at it in quite a while. I hope it's still compatible with the other tools. Anyway, you do need it for an 8K byte eeprom, so if it doesn't work ask again.
A long press of the Set key followed by 981 is a full reset of the remote. That is one of the steps required when you have added a new eeprom.
http://groups.yahoo.com/group/jp1/files/Programs/
I haven't looked at it in quite a while. I hope it's still compatible with the other tools. Anyway, you do need it for an 8K byte eeprom, so if it doesn't work ask again.
A long press of the Set key followed by 981 is a full reset of the remote. That is one of the steps required when you have added a new eeprom.
RCU-4011B uses 0x1e0a with 24C64 EEPROM !
Hi !
Thanks to jonsfire and everybody else for replying to my queries.
I have been able to run the programs in the zip file. Since my laptop OS is w2k, I had to run it thro' allowio.exe. It returned address 0x1e0a. Since none of the RDF files were suitable for this address, I edited one of the existing files and adjusted all offsets to comply to this address. Using newly generated RDF file, I uploaded to remote twice with 981 sequence in between. This got rid of all of the error messages and now I am able to upload/download from the remote alright. I still have a long way to go to customize the remote to properly control all of my devices.
Thanks everybody for the help extended.
-vekman
Thanks to jonsfire and everybody else for replying to my queries.
I have been able to run the programs in the zip file. Since my laptop OS is w2k, I had to run it thro' allowio.exe. It returned address 0x1e0a. Since none of the RDF files were suitable for this address, I edited one of the existing files and adjusted all offsets to comply to this address. Using newly generated RDF file, I uploaded to remote twice with 981 sequence in between. This got rid of all of the error messages and now I am able to upload/download from the remote alright. I still have a long way to go to customize the remote to properly control all of my devices.
Thanks everybody for the help extended.
-vekman