I do apologize for my self-centered comments from earlier. I now have the cable back.
I messed around with the RDF and the checksum and it works now, not exactly sure how. But in any case, I now have a good working 1K RDF. Now there's a new problem.
I've tried making some modifications to the 8811 3.1 extender (which means I'm just messing around with the order of the upgrade and keymove memory areas) and making a new RDF. So far, that works. But, when I upload it, I get the usual two blinks and then one long blink, so the upload failed. My question is what are some things that might cause such a thing to happen? Because I'm at a loss at where to start searching for answers.
Long Blink After JP1 Connection
Moderator: Moderators
How did you make the extender and its RDF compatible with a 1K eeprom? The symptoms you report say its RDF isn't compatible with a 1k eeprom (you didn't get far enough for it to matter if the extender was compatible).
I'll guess you made the obvious changes. But did you know about the part of the RDF that is
[FixedData]
$023 = $14
for a 2K eeprom, vs.
[FixedData]
$023 = $13
for a 1k eeprom.
I'll guess you made the obvious changes. But did you know about the part of the RDF that is
[FixedData]
$023 = $14
for a 2K eeprom, vs.
[FixedData]
$023 = $13
for a 1k eeprom.
-
The Robman
- Site Owner
- Posts: 21945
- Joined: Fri Aug 01, 2003 9:37 am
- Location: Chicago, IL
- Contact:
I think you should also post what checksum range you are using.
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!
-
ti83programmer
- Posts: 60
- Joined: Mon Oct 13, 2003 10:16 pm
I took the 1K RDF and made changes to it so that it would point to the new keymove and upgrade memory areas, so I never had the fixed data problem you mentioned.
I re-assembled the 3.1 extender with the new (same as RDF) addresses and combined it with an empty save using that RDF with extinstall.
So, you have the TV power macro in the old area (not viewable in IR), and anything new (like device selection macros) that do show up in IR. I believe I used the same checksum range and I get zero errors from the PC, it buys all this. But the remote doesn't. Double blink, then one long one. No power macro.
I re-assembled the 3.1 extender with the new (same as RDF) addresses and combined it with an empty save using that RDF with extinstall.
So, you have the TV power macro in the old area (not viewable in IR), and anything new (like device selection macros) that do show up in IR. I believe I used the same checksum range and I get zero errors from the PC, it buys all this. But the remote doesn't. Double blink, then one long one. No power macro.
-
Mark Pierson
- Expert
- Posts: 3018
- Joined: Sun Aug 03, 2003 12:13 am
- Location: Connecticut, USA
- Contact:
-
ti83programmer
- Posts: 60
- Joined: Mon Oct 13, 2003 10:16 pm
Just to get it to execute code, I removed all of the extender code and just put a RET at the end of the EEPROM (just before $400). The device and protocol to load it go in the new upgrade area, and the keymove to load it goes in the old keymove area. It couldn't be any simpler...I assemble it, extinstall it, and upload it with IR, and I get double blinks then one long blink.