That’s the timestamp on how to format your USB to FAT32 on mac.
2 Likes
Adding image.bin to the usb drive was the missing piece of the puzzle for me too. Thanks for bringing it to my attention.
I needed to add these three bins to my drive before the firmware update worked:
fpga1_239_BlueSky.bin
dsdmk2_v3.2.1.bin
and image.bin
3 Likes
Thanks Vmax - worked for me also! I have the loaded USB of the software coming soon also.
1 Like
What version firmware were you on before the update?
What does the image.bin do? I didn’t put it on the stick and the update went smooth without it.
1 Like
3.1, so I didn’t think I needed it but apparently I still did.
Think I’m there. The good there. Issue was I went with the video and didn’t read the pdf. Was loading the wrong file not the one for the lower 3.x number. Got that right and seemingly loaded both files.
If there’s a revert feature for previous loads I don’t see it or other versions listed. Not that I need it.
Thanks again for the help.
Bob
For peeps need new flash drives, don’t buy the latest and greatest, these should work, currently less than 10 bucks for 5, please note they not “SanDisk” but “SamDisk”:
Yes you need the latest image.bin file for it to work. Soon as I put that on the stick I used since Antero it all went smoothly.
1 Like
Wrong. I see another issue: when I get to the SYStem menu and push center button, it only allows me into the backlight setting and then won’t move, so I can’t get to the update screen,
After about a five hour FPGA break-in an 1 hour firmware due to getting 3.2.1 load snafu. I was amazed at how much better Bluesky sounds. Every intonation of a voice or instrument note is there. Percussion is amazingly clear. What ever the recording nothing gets smeared together. Combined with BACCH-dSP the difference between massive is jaw dropping. The lifting of veils is an old trope. So I will call this delivery “butt naked music” with music everywhere in the soundstage which became undefinable as to its boundaries and clarity in all directions. It is truly like getting a new system not just DAC or software bump we heard in the past. So clearly lively and powerful.
13 Likes
Thanks, Vmax! Adding the image.bin file worked for me, too.
Per the Firmware Update Instructions pdf included in the download package, adding the image.bin file converted the upgrade from a ‘Method 2 upgrade’ to a ‘Method 1 upgrade’. Method 2 didn’t work for me despite my DAC having been on FW rev 3.1.3. The update worked after adding the image.bin file, inserting the memory stick and flipping the power switch on the back of unit on. On boot, the DAC’s power light flashed many times before the menus were displayed. After the unit completed its initialization, the version showed as 3.2.1. Moreover, updating the firmware changed the name displayed for the FPGA from ‘239-Internal’ to ‘239-Blue Sky’.
For Aaron’s benefit, I tried the Method 2 update many times using the two files specified in the pdf and on the video. I used a SanDisk Ultra USB 3.0 32GB memory stick formatted as FAT32. The FPGA update worked as expected (except for the ‘239-Internal’ label), but the firmware update always failed with a TIMEOUT ERROR.
Now I’ll be able to return the 4GB thumb drives I ordered when they arrive.
1 Like
Aaron, as I noted in my reply to VMAX, I needed to use Method 1 and the image.bin file to get the firmware update to take despite my DAC being on 3.1.3. The FPGA update was successful using Method 2 as you described it, but the firmware update was not, failing with a TIMEOUT ERROR.
Not true, macOS diskutil command accepts FAT32 as a formatting option. Available options can be displayed by diskutil listfilesystems command.
4 Likes
Deanndra (sp?) helped and fixed. Factory rest might have been the magic.
Menu buttons were definitely not right.
Hey, while I have you… I have DAC MK2, latest pre, transport… When power is interrupted the pre lights up then goes dark; the other two boxes stay lit.
This is through a P10.
Thanks all!
Bob
My listening impressions mostly echo those of others in this thread: Blue Sky is a significant step forward. In my setup (all PS Audio gear except the cables) the soundstage is wider with a bit more sense of depth. Voices, including voices of instruments, are truer and better defined, often revealing a delicacy I hadn’t appreciated. On a few occasions last night as I listened to some of my favorite tracks, an instrument came into focus where there were just sounds before. Improvements to the bass are not subtle: it’s more full, more authoritative and better controlled. (I’ve found that improvements to clocking and digital signal processing often contribute to better bass.)
My impression is that letting the Blue Sky upgrade bake for 48 hours on a burn-in track provided some sonic benefit.
Thanks to Ted and the PS Audio team who made this upgrade possible. It’s a nice present for the holidays!
6 Likes
Thx. I didn’t know the extra options
Ok, loaded bluesky back on early Sunday morning and let it burn-in and wow what a difference 30’ish hours makes. Sounds way better! Thanks for the suggestion. You really hear pretty deep into recordings with this update and sound decay is crazy. I’m sure ill notice more as I delve into it.
3 Likes
Audio Excellence on their YouTube channel did a comparison between the MK ll running Massive and their MSB DAC early in the year. Adrian said through the MK ll was great for the price it didn’t compare to the MSB. It would be great if they would repeat the test running Mt Blue Sky. Anyone who has a DAC in a higher price category I would surely appreciate a comparison with the MK ll running Blue Sky.
6 Likes