I just got a DS Jr. I found that the FW was Yale, so I’ve updated to Torreys, it was successful.
Next step, I tried updating the embedded Bridge II.
I got to the screen “Bridge Update to 2.7.11 LongPress to Update”, I pressed the button for a couple of seconds and the update was started.
Screen shows “Bridge Updating”. And then it’s stuck here.
How long should it take? I’m waiting for a few hours now but status doesn’t change.
I have no control to the DS Jr in this state.
DS Jr is connected to my home network. I can see Bridge II from PC.
wizardofoz said
It can take a while for the bridge version to appear...give it 30 mins then check again
or get Dennis to email you a link to the forced update if you run a windows system
I waited over 6 hours but it didn’t end by itself. I had to cycle the power to stop it. I don’t know if that’s the proper operation.
But now I see Bridge update not available, and see rev 2.7.11 in FW revision display, if that’s the Bridge II version then probably update was successful.
I never managed to install the Bridge II update on my Junior. Torreys was updated no problem, but I get the same message (“bridge update not available”) and can’t make any progress past that, unfortunately.
Dennis K was kind enough to send me the force update but that is Windows only, and the computer that’s connected to the network and the Junior is a Mac
Also if you guys can recall, the “3. (input) issue” never got better. When I switch to the Toslink input it keeps showing the 3. and the asterisk -confirming that the Junior does receive the signal- however it doesn’t say Tos or Opt or anything. The name of the input has disappeared.
I am a big, big fan of PSA and its updates, but wish I had been able to use my products to the maximum of their ability.
Well color me computer illiterate but, no joy and I have given up.
What I did is, I took the DS Junior upstairs and connected to my Windows PC. Took the files that Dennis K had sent me via e-mail, opened MConnect and … it still does not recognize the Junior. All MConnectSetup101 sees is the Realtek PCIe GBE Family Controller (native to the Windows PC), and nothing else.
I have not succeded in getting Bridge II to work or forcing the update. No real biggie as currently I’m using a LanRover but this is not what I envisaged and just hate it when things don’t work. Oh well.
I would contact PS tech support. If the forced update doesn’t work, it’s possible there is something wrong with your hardware that should get fixed under warranty. I went through this recently with my NPC – all sorts of driver reinstalls, trying a different computer, etc., and it turned out to be a bad board.
Also make sure you USB stick has been formatted FAT16 or FAT32 and NOT exFAT. exFAT will not work. And make sure you use the OS eject to eject you USB stack from you system.
Just a quick one to say that Bridge II is finally working on my Junior now.
Not sure what went wrong or what had repeatedly prevented JRiver from recognising the DAC. But I went back to the previous firmware, then back to Torreys again (no need to force update it) and Eureka -it recognises it and is playing / singing beatifully off it.
This seems to be the same problem I’m having as well.
Does the USB specifically have to be 2GB for firmware updates? I recall reading that somewhere.
I tried Roon in the hopes it was a JRiver problem but the static issue is still there. Also under Roon setup it initially had set it was uncertified. I power cycled it this morning and now it doesn’t say that but the audio issue still exists.
