Er01 on Jynxbox v14. Can't load serial either

[dcapper]

My Jynxbox v14 was sitting on the shelf for a bit, so I decided to hook it up today and it went straight to Er01. I get no video. I tried removing the module and still no go. I tried reloading the allchunks file via serial and no go. My box a brick? I attached a picture of the serial fail.

[hutch]

are you using crossover or straight thu serial cable? should be crossover(null modem) I believe...

[dcapper]

I tried a null modem and a straight thru. Both give the same error.

[hutch]

gotta ask the obvious then...did you unzip the file?

[dcapper]

Yuppers. I just reloaded a v5 but it uses the 1/8" jack to serial. The v14 doesn't. I'm at a loss. I think it's pooched.

[Anubis]

Try loading factory file not all chunk. Once that takes (may take a few tries) then load all chunk or a standard clone file.

[iq180]

Yuppers. I just reloaded a v5 but it uses the 1/8" jack to serial. The v14 doesn't. I'm at a loss. I think it's pooched.
You can open the receiver and unplug the 3 wire serial port and use the serial port from another receiver or just use 3 single wires
to the serial port of the computer, only 3 wires used/ RX/TX/GND/ its not that hard.
BTW, when you turn on the receiver what do you see on the VFD.

[dcapper]

You can open the receiver and unplug the 3 wire serial port and use the serial port from another receiver or just use 3 single wires
to the serial port of the computer, only 3 wires used/ RX/TX/GND/ its not that hard.
BTW, when you turn on the receiver what do you see on the VFD.

No matter what I do, I get Er01. I have tried loading the factory firmware and it does the same thing. I'll keep trying but I have a feeling it's done. I'm having a rough week with receivers. Blew up my Viewsat 9000, now this Jynxbox and my buddies Jynxbox v5 doesn't respond using the remote.

[jvvh5897]

well, remotes are easy to test, just point it at a camera or cell phone and grab a video frame or two. If working normally a remote IR LED should be VERY bright to a camera.

[dcapper]

well, remotes are easy to test, just point it at a camera or cell phone and grab a video frame or two. If working normally a remote IR LED should be VERY bright to a camera.

I have 4 Jynxbox remotes, none worked. Probably an ir problem in the v5. Unless Im using the wrong factory file for it. Or maybe there is different Jynxbox remotes? I'm using my v14 remote to test.

[jvvh5897]

Remotes are easy to test. If you want to see if they have the same protocol, you can hook a photocell or photo diode or photo transistor to the input of a standard audio port line-in on a PC and use something like Audacity to record a small portion of the output. Most STB use NEC1 format remotes and they send 32 bits in a pulse-length modulation method using a 22kHz carrier--the specifications are easily found on the web.

I've used photocells like you might find on a lawn light and photo transistors like you can by at about any electronics store (they don't have a good response to the 22kHz modulation but you get the envelope of the response and that is all you need). Photo diodes work best and are cheap and easy to use. I seem to recall a little program over at jp1 hifi site that is supposed to capture details of the remotes to a file as you press buttons (usb IRscope but you could use a cheap atmel usb board with an ir sensor too).

Inside the jynxbox is likely an integrated IR sensor that outputs a TTL level pulse pattern like the envelope of the IR signal that is fed to the processor to be decoded. I've got older boxes that I modified the code to output info to me about what the sensor in those boxes get. Many boxes have a factory test screen that give you some of the info and can be modified at the code level to tell you more.

The models often use different remotes in my experience--more options need more buttons and so they use a diff remote. The NEC1 format lets you send 8 bits or 16 bit custom code that identifies the remote to the box and will be tested to see if they match what is expected.

[jvvh5897]

If you open up a jynx file, extract the main sw, use lzma to un-pack it, you can find a fairly standard Ali remote table called g_itou_key_tab:
2CF460 61 67 65 21 00 00 00 00-11 00 1E 80 00 00 00 00
2CF470 11 00 B6 80 01 00 00 00-11 00 36 80 02 00 00 00
2CF480 11 00 CC 80 03 00 00 00-11 00 8E 80 04 00 00 00
2CF490 11 00 0E 80 05 00 00 00-11 00 EC 80 06 00 00 00
2CF4A0 11 00 AE 80 07 00 00 00-11 00 2E 80 08 00 00 00
2CF4B0 11 00 DC 80 09 00 00 00-11 00 66 80 0A 00 00 00
2CF4C0 11 00 7C 80 0B 00 00 00-11 00 AC 80 0C 00 00 00
2CF4D0 11 00 B4 80 0D 00 00 00-11 00 8C 80 0E 00 00 00
2CF4E0 11 00 44 80 26 00 00 00-11 00 CE 80 27 00 00 00
2CF4F0 11 00 C4 80 13 00 00 00-11 00 C6 80 14 00 00 00
2CF500 11 00 AB 80 15 00 00 00-11 00 4C 80 4B 00 00 00
2CF510 11 00 3E 80 1D 00 00 00-11 00 5C 80 10 00 00 00
2CF520 11 00 AF 80 2E 00 00 00-11 00 E6 80 16 00 00 00
2CF530 11 00 4E 80 2D 00 00 00-11 00 3C 80 3C 00 00 00
2CF540 11 00 6C 80 3F 00 00 00-11 00 76 80 43 00 00 00
2CF550 11 00 0C 80 44 00 00 00-11 00 8F 80 45 00 00 00
2CF560 11 00 0B 80 47 00 00 00-11 00 2B 80 3D 00 00 00

The table start is 11 00 1E 80 00 00 00 00--that has the custom code 0x80 button code 0x1e and the function code that ap_hk_to_vk will return 0x00.

You can find this table just after the "birthday" wishes ascii string (just search for 'day' and you should find that area).

The above was from JX_NA_Firmware_v251_dual.bin and I used the 3606 source code as reference for finding stuff. You should be able to find something similar in v4 and v5 files and see if the custom code looks the same and if the table generally agree.

Oh, and looking at the NA v251 file I find that the ER01 message is displayed if the system_hw_init routine in the main code fails (about the same place as the 3606 source code has the Neowine init fail message in AppInit routine). But to get to that code lots of stuff has to be working! Flash, processor, front panel for sure--the box has to boot up and extract the main sw. It may be that there is a serial message from another routine to tell you what failed, so you might want to plug in the serial port and see if there is any output.

[dcapper]

Wow! Lots to comprehend here. I'll play with it some more later on tonight. I have two junkboxes now to play with. I'm getting a Dreamlink T4 cause I'm fed up with these crappy units. I hope to resurrect both of them and dump them.

[dcapper]

Tired again for a while last night and still no go. I figured out the ir board on the v5 is toast so I might just pull the chip on the v14 and solder it onto the v5.