Long Blink After JP1 Connection

ti83programmer · Post by **ti83programmer** » Wed Oct 13, 2004 10:00 pm

Got an OFA-upgraded 6012 here and whenever I upload or download to it, it gives one long blink instead of the usual two blinks. Is that normal? I'm developing a special protocol and it does absolutely nothing when uploading it to the remote, but I did something as simple as changing the TV device code and uploading, then downloading, and apparently the link does work, so I don't know if it's unstable or it just blinks differently and I should leave it at that.

Short question: why does it long blink once? Is that normal? Ever heard of it?

Post by **The Robman** » Thu Oct 14, 2004 6:25 am

One long blink means the upload didn't work, so you need to investigate why.

ti83programmer · Post by **ti83programmer** » Thu Oct 14, 2004 12:23 pm

I thought that's what it was, but why does changing a device code work? Have I screwed up the RDF or something? I had to change the checksum area, do you think the remote's getting the wrong checksum from IR and it's complaining or something? If not, I'm clueless.

johnsfine · Post by **johnsfine** » Thu Oct 14, 2004 12:27 pm

Sounds like the checksum range is wrong or the byte specifying eeprom size is wrong, but I haven't experimented for exact symptoms of those errors.

You changed the checksum range specified by thr RDF? Why? From what to what?

ti83programmer · Post by **ti83programmer** » Thu Oct 14, 2004 12:39 pm

I made a post a while back about having a 1K EEPROM 6012 and couldn't get IR to work with it. The checksum in the 1K RDF ranges from ^$000:$002..$3FF. It was throwing that inverted checksum message (it doesn't say that word for word, but that's what we figured out it was) and I kept reducing the size of that range and it started working at $3FD. I've never gotten a double blink with this remote.

johnsfine · Post by **johnsfine** » Thu Oct 14, 2004 1:07 pm

3FD is correct and someone ought to change the official RDF "6_806_80 (URC-881x_801x_601x 1k).rdf"

I've never used a 1K eeprom so there may be some behavioral symptom I'm missing.

Once a 6102 becomes unhappy about eeprom contents, downloading new contents and the hardware reset done by the JP1 cable might not be enough. The remote might retain data in registers that conflicts with data in the eeprom.

Try a 981 reset on the remote. That discards whatever it thought it knew about the eeprom and redetects it. I think you should get a double blink, then pause, then another double blink. That would verify the remote's CPU can talk to the eeprom.

If that works, try downloading to IR and check that IR is happy about the checksum and fixed data (that they match the 1K rdf).

Finally, reupload the eeprom contents you want and maybe the remote will like them.

ti83programmer · Post by **ti83programmer** » Thu Oct 14, 2004 1:39 pm

I don't have my cable with me right now, I'll be getting it back in the next couple of days, but what I CAN tell you as of now is that I've done the 981 reset and I DO get four blinks, however there is no pause. I know what the pause looks like because I have an 8811 that does it when you 9-8-1 it, but this remote doesn't do that. I don't know what I can say about it...is this some kind of hardware upgrade we don't know about yet? I have another 6012 with a 2K EEPROM that I think does the pause.

Or maybe I'm just blind. I do have the remote, so when I get home I'll reset it again and stare at the LED.

Mark Pierson · Post by **Mark Pierson** » Thu Oct 14, 2004 1:47 pm

I think the 4 blinks is enough proof of a valid reset. My 8810w's don't appear to pause after the first 2, but all my other JP1 remotes do.

johnsfine · Post by **johnsfine** » Thu Oct 14, 2004 1:48 pm

I think the pause is the time it takes to read the entire EEPROM and verify that the checksum is correct. With an eeprom half the size you'd expect the pause to be half as long. (note for those with 8K or larger eeproms, only 4K is included in the checksum so you won't get an absurdly long pause).

But Mark is right that the pause isn't important. 4 blinks is enough to tell the CPU likes the eeprom.

Post by **The Robman** » Thu Oct 14, 2004 2:07 pm

And just to make one thing totally clear, regardless of what results you think you are seeing after doing an upload, if you get 2 short blinks and 1 long blink, it means the upload hasn't worked.

A bad checksum would definitely cause this, but there are other factors that could also cause it.

ti83programmer · Post by **ti83programmer** » Fri Oct 15, 2004 9:19 pm

Still don't have the cable, but just to update, I did a 9-8-1 reset and it does blink four times and it even has a little pause. I guess I'm just insane.

After doing this and trying to download from the remote, IR's General tab is full of default settings (which makes sense for a 9-8-1 reset). I change one of the device codes (for example, CBL 0476 to CBL 0477), then upload that to the remote. One long blink. I close IR and then reopen it, and download from the remote. What I see next to CBL is 0477. I don't know how to explain that. Does the remote maybe not care if the checksum's right to load the device codes?

Post by **The Robman** » Sat Oct 16, 2004 9:52 am

ti83programmer wrote:Still don't have the cable, but ...{snip} ... I change one of the device codes (for example, CBL 0476 to CBL 0477), then upload that to the remote. One long blink.

OK, you've got me curious, how are you able to upload without a cable?

ti83programmer · Post by **ti83programmer** » Sat Oct 16, 2004 8:39 pm

I don't. The second paragraph was a response to what you said that a long blink must indicate a bad upload. I was explaining step-by-step what I did to produce a different characteristic in the remote by connecting to it with one long blink. When I get my cable back, I will repeat this and do what has been suggested.

Sorry for the confusion, I don't know how to quote people on boards like these and I also didn't want to seem like I was calling you a liar.

I'm sensing a little friction between me and maybe some others, and if so, I want to apologize if I was a turd in the past. I know I was with that special protocol I wrote, I let my excitement get the better of me.

Post by **The Robman** » Sun Oct 17, 2004 8:01 am

ti83programmer wrote:I don't. The second paragraph was a response to what you said that a long blink must indicate a bad upload. I was explaining step-by-step what I did to produce a different characteristic in the remote by connecting to it with one long blink. When I get my cable back, I will repeat this and do what has been suggested.

Let's wait until you get the cable back so you can totally verify what's happenning. It sounds like you don't believe me when I say that a long blink indicates a bad upload, and that's fine, but it's true. Now maybe it will accept the setup code changes as you seem to indicate, and maybe there's a logical reason for that, but I can 100% guarantee you that it won't accept your upgrades if you get a long blink.

ti83programmer wrote:Sorry for the confusion, I don't know how to quote people on boards like these and I also didn't want to seem like I was calling you a liar.

To quote a message, you use the QUOTE button in the upper right hand corner of the message that you want to quote. I'm not calling you a liar either, I'm just telling you how the remote works, and I'll take no offense whatsoever if you chose to reject what I tell you, after all it's your remote.

ti83programmer wrote:I'm sensing a little friction between me and maybe some others, and if so, I want to apologize if I was a turd in the past. I know I was with that special protocol I wrote, I let my excitement get the better of me.

When I read this I went back over the previous replies in this thread and I'm not seeing the friction you're talking about. Furthermore, I for one don't remember what you may have posted in the past, so there's no carry over friction either. Sorry if what we're saying is annoying you, but we either have the choice of telling you how the remote works (as I believe you requested by posting this thread) or we can chose to ignore the thread completely.

johnsfine · Post by **johnsfine** » Sun Oct 17, 2004 8:25 am

ti83programmer wrote:Got an OFA-upgraded 6012 here and whenever I upload or download to it, it gives one long blink instead of the usual two blinks. Is that normal? I'm developing a special protocol and it does absolutely nothing when uploading it to the remote, but I did something as simple as changing the TV device code and uploading, then downloading, and apparently the link does work,

Maybe some of the confusion in this thread is over the definition of "work".

IIUC, you uploaded, then downloaded, then checked some of the eeprom contents and found that what you downloaded matched what you had uploaded.

As you concluded, that is strong evidence that the link is changing eeprom contents and at least some of it correctly.

I believe the long blink is telling us the the remote doesn't like the new eeprom contents. That is further evidence that the link is changing the eeprom, and casts doubt on whether it is doing so perfectly (making every byte of eeprom match every byte IR has for raw data before the upload). But we don't really know whether something is wrong with the raw data you're uploading vs. something wrong with the process of getting it into the eeprom.

JP1 Remotes

Long Blink After JP1 Connection

Long Blink After JP1 Connection

Re: Long Blink After JP1 Connection