TX NR656 stuck in fw update 1% and fails

morris
Junior Member

Posts: 37

TX NR656 stuck in fw update 1% and fails Jun 16, 2020 18:14:48 GMT -5

Quote

Post by morris on Jun 16, 2020 18:14:48 GMT -5

Hey Guys,

No news to report on the 656. I have't spend time on it lately. I received some new nand chips, so I'm working on a nr818. This one had a endless list of bad blocks on the nand. So i replaced it and flashed it with a found nand dump on the net. Initially it booted and had sound. But I can't get it to update to a newer version (As available per internet connection) And also not via USB. It each time hangs with DSP2 98 percent. So I guess I will be fiddling with this machine for now

If anyone has a good know NR818 nand dump i would gladly take it

br
Maurice

dobrykamil
Full Member

Posts: 116

TX NR656 stuck in fw update 1% and fails Jul 19, 2020 10:12:20 GMT -5

Quote

Post by dobrykamil on Jul 19, 2020 10:12:20 GMT -5

Hi

I recently fixed TX-NR656 which had similar issues. No audio output and it wouldn't update via usb or network. Fw update process was ok until it reached 9% and eventually stopped with 0-83 or similar error.
Turned out, firmware for 2nd DSP was corrupted.

tibimakai Master Tech Posts: 689	TX NR656 stuck in fw update 1% and fails Jul 20, 2020 10:00:09 GMT -5 Quote Select Post Deselect Post Link to Post Member Give Gift Back to Top Post by tibimakai on Jul 20, 2020 10:00:09 GMT -5 I remember, that I had the same 0-83 error on the 656 and RZ610 and I had to run the firmware update twice, than it completed. How did you fix the corrupted DSP?

chris178
New Member

Posts: 4

TX NR656 stuck in fw update 1% and fails Nov 16, 2020 22:01:21 GMT -5

Quote

Post by chris178 on Nov 16, 2020 22:01:21 GMT -5

Hi
Thanks for your input on above nr656 repair progress.
I've found this place also after my going on the same model with pretty much very same symptoms.
All modules seems to be working beside DSP (CS49844A).
I've got this in this condition so, not sure what was previous history....
Did you get anywhere with your unit Maurice?
After some (quite long....) troubleshooting with oscilloscope - it looks as my DSP is struggling to load its FW from SPI nand flash.
Also MMPU is resting it every 1 sec.
Data bursts on DSP flash SPI lines suggests that DSP reads flash initially with 30MHz clock, then 6MHz clock, but all stops after about 50kB of data is read from the flash. Looks wrong.

I don't know what the process is as to how it is supposed to communicate back to MMPU, but it looks as when FW is loaded it shoud pull down ~DSP_IRQ.
But I guess this would only happen if DSP is ready to work...

Also my remark/observation as to DSP update process. By schematic - there isn't any physical connection (nor buffered) from NET CPU (ARM CPU that handles USB stick) to the DSP flash chip.
The only path as I see it is: USB/NET -> ARM -> NET_NOMI/NIMO SPI -> MMPU -> DIG_SDI/SDO SPI -> DSP -> FLASH SPI -> FLASH IC...
So I would image when DSP functions normal it is put into "SPI repeater" mode to program DSP flash to carry out normal user FW upgrade.

I'm a bit stuck now as I can't find a way to extract DSP FLASH image from official Onkyo firmware package... (it's in .of2)

A copy/dump of working FLASH would help a lot and shed more light to the case. Surely accelerate faultfinding process.

I've just spotted something interesting! - in Onkyo FW .of2 file where I think should be firmware for Cirrus Logic DSP - there is RIFF WAVE data....

Could it be that something "plays" it to DSP for programming?

This idea came as I've seen some strange Yamaha arrangements with FW updates over SPDIF coax..... very interesting.

Last Edit: Nov 17, 2020 4:36:02 GMT -5 by chris178

chris178
New Member

Posts: 4

TX NR656 stuck in fw update 1% and fails Nov 17, 2020 17:54:51 GMT -5

Quote

Post by chris178 on Nov 17, 2020 17:54:51 GMT -5

A bit of update - I've managed to confirm that ARM CPU (NET) is sending (in fact playing, as previously suspected) the update (RIFF waveform) to the DSP CPU over I2S lines.
A playout can be observed on DSP CPU pins 21-22, 26-27, during USB->DSP 1 update process.

Update process usually goes up to 98%, then there is a quite a delay before error 1-83 is returned. I would imagine in this time DSP should transform received playout into binary and physically flash the NAND.

Then boot itself and probably feedback current FW version.

But in my unit there is another contradiction - MMPU constantly resets DSP (pulses on DSP_RST every 1sec) during the update process.
This suggests MMPU is not aware of the update..... (if some kind of watchdog kicks in every 1sec. this should be at least disabled for the duration of the update process).
I'm confused, but at least this perhaps explains why Maurice still could not run normal FW upgrade after he revived DSP FLASH (by direct programming).

Maurice or Dobrykamil, please could you share your working version of DSP dump?

I'm really curious to see how SPI comms should look like between DSP and MMPU.. (assuming this will restore comms).

Last Edit: Nov 17, 2020 17:59:31 GMT -5 by chris178

morris
Junior Member

Posts: 37

TX NR656 stuck in fw update 1% and fails Nov 17, 2020 18:19:12 GMT -5

Quote

Post by morris on Nov 17, 2020 18:19:12 GMT -5

Hi Chris,

I have the unit stored in a corner of my workshop. At this moment I'm working on my house. Keep the mrs happy

brick laying, woodwork. So no "free" time at this moment. This will keep going for some months since i'm doing everything myself.
I wish I had a working DSP dump. Perhaps if I find some time I will look at it. Reading your post, you are far more advanced then me on this unit.

kind regards,
Maurice

chris178 New Member Posts: 4	TX NR656 stuck in fw update 1% and fails Nov 17, 2020 19:06:51 GMT -5 Quote Select Post Deselect Post Link to Post Member Give Gift Back to Top Post by chris178 on Nov 17, 2020 19:06:51 GMT -5 Hi Maurice, thanks for reply. At least your work might be a bit more rewarding and straightforward than reverse-engineering and debuging some odd SPI lines I will keep posting as works progress. BR Chris
	Last Edit: Nov 17, 2020 19:11:40 GMT -5 by chris178

tibimakai Master Tech Posts: 689	TX NR656 stuck in fw update 1% and fails Nov 18, 2020 11:13:08 GMT -5 Quote Select Post Deselect Post Link to Post Member Give Gift Back to Top Post by tibimakai on Nov 18, 2020 11:13:08 GMT -5 Tjmotter wrote this, maybe there is something of interest for you: repairalmostanything.com/thread/767/never-wanted-onkyo-firmware

chris178
New Member

Posts: 4

TX NR656 stuck in fw update 1% and fails Nov 18, 2020 16:00:06 GMT -5

Quote

Post by chris178 on Nov 18, 2020 16:00:06 GMT -5

Hi tibimakai,
Thank you for this too. I've seen it and this is very informative and valuable source. Ive read through most of it.

I can report that I've managed to revive my unit. Big credits go to Kamil as he helped with DSP flash working content.
This was the key. Now CS49844A is working again and appears to take updates too.

Onkyo's (or Cirrus...) build-in update method via RIFF audio file seems to me a bit cloudy... why this way, I don't understand and not simply over SPI comms...
But it looks that perhaps this DSP IC only way to boot is via its SPI FLASH, and there isn't any recovery mechanism built into it. Brief datasheet only mentions booting via secondary SPI interface.

Anyway this is a win and it's made my day today!

Thank you for your help.

Last Edit: Nov 18, 2020 17:25:33 GMT -5 by chris178

geduxaz
Junior Member

Posts: 22

TX NR656 stuck in fw update 1% and fails Dec 5, 2020 18:07:31 GMT -5 poppabradj likes this

Quote

Post by geduxaz on Dec 5, 2020 18:07:31 GMT -5

Hello.
Please help with NR656. Serial stuck at starting kernel... This is after net update. Tried all possible updates, get 0-81 error!

U-Boot SPL 2014.07 (Mar 18 2016 - 11:33:00)
detected max. frequency: 800(MHz) -

U-Boot 2014.07 (Mar 18 2016 - 11:33:00), Build: jenkins-2016EntryAVR-9

I2C: ready
DRAM: 256 MiB
rstst: 0x1, rstctrl: 0x0
NAND: 256 MiB
MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1
Setting partitions for 256MB flash.
Setting mtdparts: mtdparts=omap2-nand.0:128k(mlo),128k(mlo2),128k(mlo3),128k(mlo4),1024k(u-boot),512k(u-boot-env),512k(constants),8192k(settings),5120k(kernel),5120k(kernel_2),512k(dts),512k(dts_2),120064k(rootfs),120064k(rootfs_2)
Net: cpsw
BOOTCOUNT is 18
Warning: Bootlimit (6) exceeded. Using altbootcmd.
Hit any key to stop autoboot: 0
ERROR: Maximum boot count reached!
INFO: Checking boot partition.
Booting from nand ...
INFO: loading kernel image into RAM...
Unknown command 'bstate' - try 'help'

NAND read: device 0 offset 0x1480000, size 0x80000
524288 bytes read: OK
### CRAMFS load complete: 38029 bytes loaded to 0x80800000
INFO: dts file load successful
INFO: fdt addr set successful
INFO: fdt resize successful

Loading from nand0, offset 0xa80000
Image Name: Linux-3.19.0
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 4780376 Bytes = 4.6 MiB
Load Address: 80008000
Entry Point: 80008000
INFO: kernel partition load successful
INFO: booting kernel image...
## Booting kernel from Legacy Image at 80200000 ...
Image Name: Linux-3.19.0
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 4780376 Bytes = 4.6 MiB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksum ... OK
## Flattened Device Tree blob at 80800000
Booting using the fdt blob at 0x80800000
Loading Kernel Image ... OK
reserving fdt memory region: addr=80800000 size=a000
Loading Device Tree to 8fc19000, end 8fc25fff ... OK

Starting kernel ...

Last Edit: Dec 5, 2020 18:08:02 GMT -5 by geduxaz

poppabradj
New Member

Posts: 2

TX NR656 stuck in fw update 1% and fails Jan 8, 2021 11:57:12 GMT -5

Quote

Post by poppabradj on Jan 8, 2021 11:57:12 GMT -5

Dec 5, 2020 18:07:31 GMT -5 geduxaz said:

Hello.
Please help with NR656. Serial stuck at starting kernel... This is after net update. Tried all possible updates, get 0-81 error!

U-Boot SPL 2014.07 (Mar 18 2016 - 11:33:00)
detected max. frequency: 800(MHz) -

U-Boot 2014.07 (Mar 18 2016 - 11:33:00), Build: jenkins-2016EntryAVR-9

I2C: ready
DRAM: 256 MiB
rstst: 0x1, rstctrl: 0x0
NAND: 256 MiB
MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1
Setting partitions for 256MB flash.
Setting mtdparts: mtdparts=omap2-nand.0:128k(mlo),128k(mlo2),128k(mlo3),128k(mlo4),1024k(u-boot),512k(u-boot-env),512k(constants),8192k(settings),5120k(kernel),5120k(kernel_2),512k(dts),512k(dts_2),120064k(rootfs),120064k(rootfs_2)
Net: cpsw
BOOTCOUNT is 18
Warning: Bootlimit (6) exceeded. Using altbootcmd.
Hit any key to stop autoboot: 0
ERROR: Maximum boot count reached!
INFO: Checking boot partition.
Booting from nand ...
INFO: loading kernel image into RAM...
Unknown command 'bstate' - try 'help'

NAND read: device 0 offset 0x1480000, size 0x80000
524288 bytes read: OK
### CRAMFS load complete: 38029 bytes loaded to 0x80800000
INFO: dts file load successful
INFO: fdt addr set successful
INFO: fdt resize successful

Loading from nand0, offset 0xa80000
Image Name: Linux-3.19.0
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 4780376 Bytes = 4.6 MiB
Load Address: 80008000
Entry Point: 80008000
INFO: kernel partition load successful
INFO: booting kernel image...
## Booting kernel from Legacy Image at 80200000 ...
Image Name: Linux-3.19.0
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 4780376 Bytes = 4.6 MiB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksum ... OK
## Flattened Device Tree blob at 80800000
Booting using the fdt blob at 0x80800000
Loading Kernel Image ... OK
reserving fdt memory region: addr=80800000 size=a000
Loading Device Tree to 8fc19000, end 8fc25fff ... OK

Starting kernel ...

===

poppabradj
New Member

Posts: 2

TX NR656 stuck in fw update 1% and fails Jan 8, 2021 11:59:32 GMT -5

Quote

Post by poppabradj on Jan 8, 2021 11:59:32 GMT -5

I am Having the same Issue .. error 0-81 (I believe I have a corrupted firmware on my TX-NR656 ... anyone has a solution or suggestion, before I bring it to service center, I am a noob when it comes to this but I can follow Instruction.

The receive works, but I don't have access to Network or Bluetooth, OSD doesn't work on my TV and IN Settings, I don't have access to many option: for example in 7.Miscellenous all I have access to is 1.Tuner, 3.Remote and 5. Lock (and the option is unlocked).

Any help would be appreciated.

geduxaz
Junior Member

Posts: 22

TX NR656 stuck in fw update 1% and fails Jan 8, 2021 17:58:18 GMT -5 via mobile

Quote

Post by geduxaz on Jan 8, 2021 17:58:18 GMT -5

Just fixed mine!!!

Totaly same 0-81. It means usb not started and cant do usb/net update (linux not booting up).
I managed to boot into UBOOT and reflash nand with images from decoded oficial firmware.
It took 2 weeks in evenings to lear nand programming/ uboot/ uboot env.

Last Edit: Jan 8, 2021 18:01:12 GMT -5 by geduxaz

tjmotter
Senior Member

Posts: 384

TX NR656 stuck in fw update 1% and fails Jan 9, 2021 11:27:59 GMT -5

Quote

Post by tjmotter on Jan 9, 2021 11:27:59 GMT -5

Jan 8, 2021 17:58:18 GMT -5 geduxaz said:

Just fixed mine!!!

Totaly same 0-81. It means usb not started and cant do usb/net update (linux not booting up).
I managed to boot into UBOOT and reflash nand with images from decoded oficial firmware.
It took 2 weeks in evenings to lear nand programming/ uboot/ uboot env.

Would love to hear the process you developed to do this.

geduxaz
Junior Member

Posts: 22

TX NR656 stuck in fw update 1% and fails Jan 12, 2021 17:14:44 GMT -5 via mobile

Quote

Post by geduxaz on Jan 12, 2021 17:14:44 GMT -5

Jan 9, 2021 11:27:59 GMT -5 tjmotter said:

Jan 8, 2021 17:58:18 GMT -5 geduxaz said:

Just fixed mine!!!

Totaly same 0-81. It means usb not started and cant do usb/net update (linux not booting up).
I managed to boot into UBOOT and reflash nand with images from decoded oficial firmware.
It took 2 weeks in evenings to lear nand programming/ uboot/ uboot env.

Would love to hear the process you developed to do this.

Well this was my first repair over all so it took me many tries, flashes, soldering...
I think it was never booting up to usb to do firmware update.
At first i was trying to fix native nand like copying parts and changing places rootfs-rootfs2 etc.

Later i found that uboot enviroment had many scripts. Reading through them it was clear that factory/service can run updates from uboot. Scripts can look into usb or network for update files, and later flash them to needed mtds.

So i did simple things.
I cheched where my boot stops, tried deleting dts, kernel, rootfs and found that it looked only rootfs was not booting.

I took rootfs file from decoded firmware to usb.
Booted uboot, started usb.
Copied rootfs from usb to RAM.
Erased nand partirions with rootfs and rootfs-2
Wrote nand rootfs and rootfs2 from RAM.

Exact comands can paste later. Need to take terminal dump.
After that it booted to linux and i got usb. Did firmware update from official files by usb.

What is interesting. This device has hidden output when system is running ok.
It shows only sratring kernel....

Last Edit: Jan 12, 2021 17:16:36 GMT -5 by geduxaz