|
|
Post by mmartell on Nov 26, 2021 19:56:56 GMT -5
Also note that "Firm. Package" being zero is NOT recorded as an error by the cpu as the first character is not a triangle, though it certainly seems it should be.
|
|
|
|
Post by mastertech on Nov 26, 2021 22:30:46 GMT -5
According to the SM, the firm error you are getting could be because of an incorrect region setting. Go to page 190 and check the region setting resistors. If they are incorrect then change them. If they are correct, try changing them to the opposite and see if it solves the "firm error".
|
|
|
|
Post by mmartell on Nov 26, 2021 22:40:32 GMT -5
Already checked that and they are correct. Are you suggesting I swap them, that maybe the receiver has taken firmware for another region ?
|
|
|
|
Post by mastertech on Nov 26, 2021 22:53:15 GMT -5
yes
|
|
|
|
Post by mmartell on Nov 26, 2021 23:13:58 GMT -5
Will have a look at that tomorrow. Thanks.
|
|
|
|
Post by mmartell on Nov 28, 2021 23:22:26 GMT -5
I don't see how that's possible as the receiver boots with the message SR7011_U, that being the designation for North America. The current loaded firmware matches the resistor configuration.
SM page 135 explains that the FIRM ERROR comes in this case from the Version number expecting certain non-zero values from the DSP.
There has to be some other issue common to all four DSP's. Odd that no specific errors are returned as in SM page 134 condition 5-DSP NG.
|
|
srt
Junior Member
Posts: 90
|
Post by srt on Nov 29, 2021 1:03:38 GMT -5
HI i am not an expert , but can you please check communication line between 1st DSP and MCU, like MISO MOSI , reset etc. check the continuity .
|
|
|
|
Post by mmartell on Nov 29, 2021 10:40:33 GMT -5
I have checked the reset line and that is good but yes I will check the others.
|
|
|
|
Post by mmartell on Nov 29, 2021 12:30:25 GMT -5
Ok I just checked miso, mosi, clk, chip sel, flags0 and the previously tested rst and they're all good.
Also moved the resistor at R1589 to R1590 and that only brought me to the setup page. After going through setup still had the FIRM ERROR and there were no updates available, said I had the latest. Moved the resistor back back to original location.
|
|
|
|
Post by mastertech on Nov 29, 2021 12:48:30 GMT -5
Clearly you are showing DSP errors on 1 thru 4. What I am having trouble with is page 134 section 5 which indicates something should read out an error number. How to get that is unclear. When the DSP error shows can you select it somehow to show the error numbers?
|
|
|
|
Post by mmartell on Nov 29, 2021 13:19:12 GMT -5
Not that I'm aware, the only key that responds is "status" and that moves you to the next item.
What if the dsp IS responding normally except that the response is zero's ? What about the spi flash associated with each dsp ? I know these can fail but I have a hard time believing all four have failed at the same time. Do you see a common point with these that might be causing a problem with all four ?
|
|
|
|
Post by mastertech on Nov 29, 2021 16:01:58 GMT -5
What if the dsp IS responding normally except that the response is zero's ? What about the spi flash associated with each dsp ? I know these can fail but I have a hard time believing all four have failed at the same time. Do you see a common point with these that might be causing a problem with all four ? All 4 DSP's on your screens have a triangle in front of it which according to the manual indicates an error. Unless the error is the firmware zeros. But the manual is not clear on this so I can only speculate. I agree that those SDRAM's and Eeprom's are know to be problematic but changing them may be the only way to find out. They are not very expensive from what I have seen. Just a lot of soldering. I've been looking over the schematics and I am seeing quite a few safety resistors in these control lines and I have seen surges take out multiple's. I would suggest doing continuity test right from pin to pin of the CPU and each DSP's pins. This would be easier then locating these resistors and also eliminate any connections or broken trace issues. If you need help finding these pin to pin locations let me know. |
|
|
|
Post by mmartell on Nov 29, 2021 17:09:16 GMT -5
What if the dsp IS responding normally except that the response is zero's ? What about the spi flash associated with each dsp ? I know these can fail but I have a hard time believing all four have failed at the same time. Do you see a common point with these that might be causing a problem with all four ? All 4 DSP's on your screens have a triangle in front of it which according to the manual indicates an error. Unless the error is the firmware zeros. But the manual is not clear on this so I can only speculate. Right. On page 135 you can see where the "created" Version number is a kind of hash from all the firmwares. I would guess a Version number sent in an update is stored somewhere and checked against the created version number and in this case the zero's implicate the four DSP's.
So I am speculating as well but surmise exactly that - that the error IS the firmware zero's. Of course that doesn't help as finding out WHY is much more important.
Speculating aside I will start tracing out pin to pin connections when I get some time.
|
|
srt
Junior Member
Posts: 90
|
Post by srt on Nov 29, 2021 22:16:50 GMT -5
What if the dsp IS responding normally except that the response is zero's ? What about the spi flash associated with each dsp ? I know these can fail but I have a hard time believing all four have failed at the same time. Do you see a common point with these that might be causing a problem with all four ? All 4 DSP's on your screens have a triangle in front of it which according to the manual indicates an error. Unless the error is the firmware zeros. But the manual is not clear on this so I can only speculate. I agree that those SDRAM's and Eeprom's are know to be problematic but changing them may be the only way to find out. They are not very expensive from what I have seen. Just a lot of soldering. I've been looking over the schematics and I am seeing quite a few safety resistors in these control lines and I have seen surges take out multiple's. I would suggest doing continuity test right from pin to pin of the CPU and each DSP's pins. This would be easier then locating these resistors and also eliminate any connections or broken trace issues. If you need help finding these pin to pin locations let me know. if the 1st DSP is boot from SPI flash , then there is chance for firmware corruption, like in ONKYO if 1st DSP is failed to boot , then it will not recognize the second DSP even it have its on SPI flash , MY suggestion you can remove the SPI flash and check the content on(check for FFs-means Blank) it or else just copy firmware from same model , also you can use multimeter you can check the pin 2(monitor the voltage changes while booting) of SPI flash to understand any reading is happening. Another thing is you can remove the 1st DSP spi flash and check the firmware version of DSPs which still showing 00 or nothing . Can you post SM of 7011 |
|
|
|
Post by mmartell on Nov 29, 2021 22:49:03 GMT -5
How do I post the SM there is a very small size limit here. Do I have to host the file somewhere and post a link ? Where is a good place to upload the file to ? Thanks
|
|
