Is it time to relabel the JP2 remotes with JP2.x ids?

[The Robman]

The x in JP1.x remotes indicates which processor it uses:

JP1.1 SST
JP1.2 HCS08
JP1.3 S3F8

So, is it time to do something similar for JP2 remotes, and maybe re-label JP1.4 as JP2 in the process, as they are all "segment" remotes? It would also help from JP1.4 remotes being confused with JP1.x remotes.

If yes, I see 2 choices, either number them according to the order in which they came out (if known), like:

JP2.1 S3F8
JP2.2 TI25xx
JP2.3 MAXQ6xx
JP2.4 GP5xx

Alternatively, we could use the signature as a clue for the x value, like:

JP2.2 MAXQ6xx (2xxxxx sigs)
JP2.3 S3F8 (3xxxxx sigs)
JP2.6 TI25xx (6xxxxx sigs)
JP2.8 GP5xx (68xxxx sigs)

[mathdon]

RMIR interface types already indicate the processor:

JP1.4, JP1.4N -> S3F80
JP2, JP2N -> MAXQ610
JP3 -> MAXQ612
JPS, JPUSB (not XSight Touch/Color) -> MAXQ622
JP3.1 -> TI25xx (2541, 2530, 2533)
JP2.2 -> GP541
JP3.2 -> GP565

All these interface types have a segment structure to their E2 area. The entire flash may or may not have a block structure in which each block starts with a two-byte checksum followed by a four-byte (32-bit) block length. Remotes with an S3F80 (JP1.4) or MAXQ610 (JP2) interface can have either structure. Those with a block structure have an N (for New) appended to the interface type.

JPS and JPUSB interfaces have a USB connector rather than the usual 6-pin (or 5-hole in some cases) connector. The difference is that SimpleSet (JPS) remotes (URC-6440, OARUSB04G and similar) have a distinctive structure to the flash. XSight Lite/Plus have the same processor and use a JPUSB interface. XSight Touch/Color are also labelled with a JPUSB interface as they have a USB connector but they have a different internal structure. They do not have an E2 area in the usual sense but instead have an internal file system. RMIR represents the user files of this system by a simulated E2 area. These remotes use S3F80 protocols but their main processor is an ARM one with 256Kb of flash.

Interface types starting JP1 or JP2 have 64Kb of flash or less. Those starting JP3 have more than 64Kb of flash.

This labelling has simply grown up as new interfaces appeared and so is not particularly systematic, but it does identify the processor as well as some other aspects of the memory structure of the remote.

Edit: It would be confusing to re-label JP1.4 as JP2 as many JP1.4 remotes have JP1.4 printed on the PCB. I think some early JP2 remotes have JP2 printed on the PCB, but I am not sure about that.

[The Robman]

Where did all these interface names come from? I've only ever heard JP2 used for all remotes post-JP1.4. I've not seen UEI get this specific in their type labeling before.

[mathdon]

Where did all these interface names come from? I've only ever heard JP2 used for all remotes post-JP1.4. I've not seen UEI get this specific in their type labeling before.

The clue comes in the name "Interface type". For remotes with 6-pin (or 5-hole) connectors other than JP1, the interface between the remote and the PC is provided by jp12serial, which is therefore handling remotes with many different processors and internal structures that use differing algorithms for their interface. The jp12serial code has to identify the appropriate algorithm. It assigns a numeric code to the required one when downloading or uploading the remote and this code is passed to RMIR, which translates it into a more readable interface name. The interface name is shown, along with the processor name, on the Raw Data tab in RMIR. In order that it can show the interface name when the remote is not connected to the PC, RMIR uses the processor and other data to determine which interface type is required for any particular remote, so the name can be displayed even when the current setup comes from loading a .rmir or even a .ir file.

Why haven't you seen these interface names being used? For most purposes they not relevant, the only significant fact being that their E2 area has a segment structure, so they are usually collectively referred to as JP2. This is similar to the fact that JP1 remotes use a number of different processors but all that is usually needed is the collective name JP1. For the same reason you may not be aware that UEI has used three different MAXQ processors each needing a different interface type, three TI processors which all use the same interface type, and two GreenPeak/Qorvo processors which again need different interfaces. The differences are hidden from RMIR by jp12serial as an intermediary.