[Quantumcross]

Ok, thanks for interpreting that for me, I don’t quite understand it yet. I will desolder the IR receiver and R33 and do the tests again.

Today I received a busted OSSC (failed HDMI upgrade) that I’m hoping to repair tonight as well. If I can get that one working I will feel much more comfortable doing more invasive diagnostics with the first one 🙂

[Quantumcross]

Removed R33

Resistance test:

- on IR_RX, + on VCCIO: 19.2kOhm
- on IR_RX, + on GND  : 19.2kOhm
+ on IR_RX, - on VCCIO: 39.2kOhm
+ on IR_RX, - on GND  : 40.2kOhm

Diode test:

- on IR_RX, + on VCCIO: 0.829V
- on IR_RX, + on GND  : 0.460V
+ on IR_RX, - on VCCIO: 0.727V
+ on IR_RX, - on GND  : 0.820V

[Quantumcross]

Thanks, I’ll try this tonight.

[Quantumcross]

Since the settings are already gone, I flashed the latest jtag version and it still doesn’t work.

For what it’s worth, our datapath vision capture card is reporting that the test pattern is 59.94 hz.

[Quantumcross]

Hi marqs, I just reflowed the FPGA and reflashed the same version of the firmware over JTAG, and it seems to have reverted the settings to default.

The IR reciever is still not working, so now the OSSC is stuck in 2x mode 🙁

Do you have any more ideas for me to try…?

[Quantumcross]

Thank you so much for the response.

I do have a USB blaster, I am worried that if I reflash the firmware I will lose my current settings with no way to dial in new ones. This OSSC is currently used nearly daily in a streaming setup and I would not want it to be stuck at a generic 2x mode.
— Is the state of all the settings stored in the eeprom? If I dump it first before reflashing, can I reflash a dump to get it back exactly in the same state it is in now? Can I dump the current state of the eeprom with the usb blaster or should I use an external dumper?

I don’t have a device that can measure the Y1 frequency, but everything else on the device is working fine, the 4x scale mode that it was stuck on when the IR stopped working, hdmi audio (with the addon board), etc.

I did get the FPGA from aliexpress, so maybe it actually could be a bum chip?

[Quantumcross]

So I’ve done some diagnostics and I still can’t figure out what’s wrong here.

Here is the list of things I did:

• checked VccIO on IR ~ 3.25V
• checked GND on IR connected
• checked R33 connected to VccIO and IR pin 1
• checked IR pin 1 and R33 connected to pin 23 on FPGA
• Signals are shown on oscilloscope in Vout of IR when remote is pressed ( I don’t understand the signal but there are definitely pulses there
• Completely replaced IR receiver module
• Tried 3 different working remotes

It still does not work and I am out of ideas. Please help me!!! This OSSC is used in a streaming setup and we would like to get it working as soon as possible!!!

[Quantumcross]

Thanks. Any chance of a third input? My switcher address bus is 3 bits. Otherwise I might just add a chip and maybe tap into the i2c bus. It looks like the easiest place to get to the i2c bus is via the LCD panel pins?

[Quantumcross]

Ok, my Cyclone finally came in and I completed my OSSC. After spending an hour trying to find a basically invisible short on one of the 3.3v lines (thanks for the pictures of the PCB traces, they were very helpful!!!), my OSSC is working great!

I’ve now realized how stupidly easy it is to program the OSSC to the remote, so you’re right, this is basically useless! I just used my tv remote to find a code set that the OSSC responds to, then I used that to program my L336 remote button by button.

[Quantumcross]

Maybe that will work then, I don’t have my OSSC complete yet. I just got the HDMI chip today, just waiting on the cyclone… Then I will be able to mess around with it. It was fun to screw around with the remote while I’m anxiously waiting 🙂

[Quantumcross]

OK sorry for the delay in these instructions.

1. Remove remote batteries
2. Use some kind of spudger or plastic tool to go around the edge and open the remote (all plastic clips, careful not to break them)
3. There are 2 chips, locate the flash, it should be a 24C16N (If it’s not a 16 we can probably still dump it just different command)
4. Take your pi, turn on the i2c bus in sudo rasbpi-config, reboot.
5. Get the i2c tools: sudo apt-get install i2c-tools
6. Pinout is:
   • 4 – GND
   • 5 – SDA
   • 6 – SCL
   • 8 VCC
7. Hook up 4 wires to pi with a clip or by solder
8. pi pinout: https://pinout.xyz/
9. pin 1 is 3.3V, pin 3 is SDA, pin 5 is SCL, pin 6 is GND on pi
10. run sudo i2cdetect -y 0, you should see addresses 50 through 57 light up in the output.
11. dump the flash: for i in 50 51 52 53 54 55 56 57; do sudo ./eeprog /dev/i2c-0 0x$i -r 0:256 -f -o 0x$i-2.bin; done
12. zip up all the 0x5*.bin files, upload em somewhere, and I’ll let you know if it works!

Edit: Here’s a datasheet: http://pdf1.alldatasheet.com/datasheet-pdf/view/175224/ATMEL/AT24C16N-10SA-2.7C.html

[Quantumcross]

Awesome!!! I’ll post some instructions later tonight.

[Author]

Posts