JP1 Remotes

Perhaps some insight as to just what is this JP1 port.
"JP1" idenifies a plug used to define a port defined by the 'Joint Test Access Group' known as JTAG. A reduced serial pin configuration is called 'BDM' background debug module.
Manufacturers of JP1 remotes us this port to load and troubleshoot the firmware that makes these remotes tick. URC, Radio shack and such.
Wat this means for the remote tinkerer is this gives a gateway to reprogram codes and protocols not already on the remote.
The early interface was simple, connecting certain paralell port pins to JP1, then running software like remote master.
Newer interfaces use USB with a controller to into a USART, buffered to JP1
There are many such BDM interfaces to be found, from USB dongles, to more complex interfaces, usually available from a few dollars to as much as $30 that will work with JP1 remotes, these will need their certain drivers installed for your OS, then you are free to use all the remote software available.
Been quite a wile since playing with remotes and they have come a long way with BDM. Worst case is JTAG has no set standards for pinout functions, so up to the maker of the remote to define that, the signals and functions are all there though.
Once you understand this, it is really rather simple. Gets a bit more complicated when you work with smart oled UHDYV.

What is the point of this post?

This post hurts my brain. Seriously, it may be dangerous to read.

Is this access group going to ask for royalties?

Applying for the position of "secretary of JP1" at the White House?

boxnut wrote:"JP1" idenifies a plug used to define a port defined by the 'Joint Test Access Group' known as JTAG.

I don't think JP1 remotes are programmed using JTAG.

The Robman wrote:What is the point of this post?

Back when I first started playing with remotes, I had no clue "what"JP1 was, what it did, and how it worked. This site taught me the basics, and taken it on my own from there. Learned the entire scope of joint test access group and its kin, Come a long ways and can at least give something to the forums.

MaskedMan wrote:Is this access group going to ask for royalties?

No, just a group of engineers that forme some level of standardizing the 'tap' found on many of todays processors. Makes for a much faster testing method than visual or the "bed of nails" troublshooting PC boards or programming firmware.

ckeays wrote:

boxnut wrote:"JP1" idenifies a plug used to define a port defined by the 'Joint Test Access Group' known as JTAG.

I don't think JP1 remotes are programmed using JTAG.

The folks like URC are a marketing for many programmable remotes made in Kore or China.
Off the assembly line they are a bunch of parts. The brain in these has a "TAP" test access port the makers DO program with JTAG and OEM SDK for the specific processor. The outside world is a 6 pin header labled 'JP1'.
Software such as found on this site gives access to to remote codes and protocols, and programming or adding to the factory codes.

Hi, I know this is an old post, but may be of some help.
The chip in this remote is what I take as overkill being an 'SOIC"
The radio just part of the system makes it a good radio remote.
Your JP1 is obviously working given you have any access to memory space.
A look at your file doesn't look like RDF, Possibly protocols for existing remotes(TVs)
RM/IR looks to eeprom space, internal or external for anything like RDF data.
Probably why this won't save as an RDF , but should save as a binary.
The core of this chip is 8051 with a few variants for eeprom and e2 space.
The 'TAP' called proprietary 2 wire in the data sheet still complies with JTAG and 2 of the needed 5 pin minimum for reading/writing to memory space and debugging.
Take a step up with JTAG software, should give yo every thing on and off chip. I played with a predecessor to this with a dish network remote with wireless. One would have to disassemble and trace the firmware to see just what your code does.
Hope this sheds a bit of light here.