Saldali
Forum Replies Created
-
AuthorPosts
-
…and as all hope was about to be abandoned, the OSSC found its way to my door, after 2 months in transit.
Thank you BuckoA51. Just sent an email.
I was able to solve my problem using a JTAG programmer and some very appreciated help from marqs and others in the forum.
See the whole story here.
Best regards and thanks to all.Thank you marqs and all who helped, you were first class.
I now have a working OSSC clone again.My new unit from VGP is on its way. The old one that’s back to working state – although stuck on fw 0.86 – I’ll try to find a buyer for it.
I’ll be posting on the 0.88 thread, to let the other guy with same issue know about my case development.
Thank you for a great product.
Best regards to allA.Salvador
My thanks to marqs for the new file.
I tried it, but ended up with the same error. 🙁
megari, I took a look at the link you gave me. I understand you suggest, that I could somehow hack the code for my chip? I completely lack the skills for that 🙁I don’t expect marqs to support devices made with different specs from his own, but I’d be very happy – and some other people too – to at least get my device back to working condition, even with some backward firmware version that will never be upgraded again.
…if such thing is possible.If I can’t go anywhere with the JTAG programmer and help from the forum, will try to invoke warranty from micomputer.es, but I suspect they’ll argue that this was my fault, for “messing up” with firmware upgrades.
I tried to downgrade my OSSC using JTAG, but ran into an error message.
Described in this threadmarqs, if you could take a look into this error, I’d appreciate.
So, my €13 Altera USB Blaster JTAG programmer arrived.
This was my attempt at fixing my OSSC by downgrading via JTAG, since the SD card reader went bad after the upgrade to 0.88
I now know that my OSSC uses different parts from the one sold by VGP, which seems to account for the “accident”.I had previously updated from the original version (don’t know) to 0.86, and that went fine, using the SD card method.
Since I couldn’t find 0.86 as a .jic file to get back to it, I followed the JTAG programming guide to try and download this file:
ossc_0.85-aud.jic (EDIT: and also ossc_0.76-aud.jic)
But then I got this error message:Info (209060): Started Programmer operation at Thu Dec 17 17:39:54 2020
Info (209016): Configuring device index 1
Info (209017): Device 1 contains JTAG ID code 0x020F20DD
Info (209007): Configuration succeeded — 1 device(s) configured
Error (209025): Can’t recognize silicon ID for device 1. A device’s silicon ID is different from its JTAG ID. Verify that all cables are securely connected, select a different device, or check the power on the target system. Make sure the device pins are connected and configured correctly.
Error (209012): Operation failed
Info (209061): Ended Programmer operation at Thu Dec 17 17:40:00 2020So, if anyone has an idea what’s going on, I’d very much appreciate some help. I’ve never used this tool before.
EDIT: the OSSC was powered up when I tried this.
I got my OSSC from micomputer.es.
The wiki at junkerhq.net lists them as source of pre assembled boards, along with others. I chose them for geographic proximity and for being in the EU.
I thought I was getting the real deal.Anyway I’ve bitten the bullet and ordered a new one from you. I hope I can fix mine with a JTAG programmer and then try to sell it, to try minimize the damage.
This is because I don’t want to be left out of the firmware improvement train.accidentally double posted…
marqs, hope the quality is good enough:
Bottom sideThank’s for your reply marqs. I realize you are the developer of the OSSC?
It’s such a great product, it’s the only way I found to get acceptable video quality out of my euro TI99. I’m hooked.I upgraded from 0.86 to 0.88
The printed manual that came with the unit mentions Revision 1B
I bought it March or April this year, from this seller:
https://www.micomputer.es/es/inicio/396-ossc-open-source-scan-converter.html
It came with a remote, multi region PSU and a quality printed manual, which referred to VideogamePerfection.com/ACEL in the last pageI’m thinking… if I downgrade using the JTAG socket, maybe I can get back to normal operation again?
I’ve ordered a USB-Blaster compatible programmer to try that. I saw that you have the 0.85 .jic file in the firmware folder. Then, use the SD to go back to 0.86?…BR
A.Salvadorhoshikawa, I had exactly the same problem. Have you found a solution?
-
AuthorPosts