Have I broken my OSSC?

[tieelo]

I see. That might be just the case. Although it’s quite hard for me rn to get ahold of only one of the S25FL216K. The only source I checked I could get ahold of without paying like 20€ because of shipping was Aliexpress but I really don’t wanna buy stuff there.
If I manage to get ahold of one of these I will try it.
I bought mine from Amazon btw because of easier shipping. If I break it, I just know where to buy the real stuff now…

[Francesco]

Hello, i’m reading this thread and i don’t know if i can update my ossc with actual 0.86a to the last firmware released.
This is the ic that i have on my ossc:
https://i.postimg.cc/9QfDnvq4/PXL-20210209-162116766-MP.jpg

What do you think? Is it a sure brick or not with Winbond W25Q16JV?

EDIT:i would take the “risk” and i have updated from 0.86a to 0.88a with success and without any above problems of the other users. So definitively the winbond flash is good.

[mexiace]

Marqs,

Seems I’m having the same issues and am getting the error “Can’t recognize silicon ID for device 1” when attempting a JTAG firmware update. Chose this USB programmer:

Waveshare Electronics USB Blaster V2
http://www.amazon.com/dp/B08CV3L6LF?psc=1&ref=ppx_yo2ov_dt_b_product_details

Any help you might be able to provide would be appreciated. Currently on firmware 0.90a and trying to revert to 0.86

Much Appreciated!

• This reply was modified 1 year, 11 months ago by mexiace.

[Aqua_von_s]

Hello all, I got a similar issue, someone updated my ossc and it died. Now for me I can flash the *.sof file attached in the thread. But after that it won’t update from a microsd…. The other files mentioned in the thread silicon id different from it’s JTAG ID. Anyone with an idea where to find a working file ?

 

Thanks !

[BuckoA51]

Was your OSSC one of the ones from micomputer.es?

[marqs]

@Aqua_von_s Which kind of error you get after programming .sof file and trying to permanently flash firmware via SD card? Also, do you remember what was the firmware version before update and could you also check which flash chip is on your board?

[Aqua_von_s]

Can’t recognize silicon ID for device 1 – I swapped the chip and I could flash the new one but looks like there is some damage to the unit somewhere. LCD is still blank when it powers on. My U7 gets instant warm when powering on. So it might be my U5, ordered a bunch of spare parts from Mouser today and I hope i can go down the rabbit hole and figure out where the short is….

[Aqua_von_s]

So i Swapped U7/U6 , D5, U17 and still the same. One of the caps near U7 was shorted, decided to take out U1 and the short is gone…..might be that my U1 died. Previous to this is was getting hot really fast, is this normal ? The unit starts up now with error 3 code.

• This reply was modified 1 year, 10 months ago by Aqua_von_s.

[marqs]

@Aqua_von_: it’s a bit hard to follow your chain of events in order to understand in which point the HW has got damaged. Based on the posts above I gathered the following:

1. Board OK
2. Firmware updated
3. Board “died” (should still start up even with non-supported flash chip as described in earlier posts -> probably already damaged in 1.)
4. New flash chip installed and programmed
5. Board not booting, U7 warm (AVDD shorted, probably inside U1)
6. U1 removed and short is gone -> starts with error 3 (“cannot find U1”)

Anyway, installing new U1 should restore functionality.

[Author]

Posts