Welcome to the Slashdot Beta site -- learn more here. Use the link in the footer or click here to return to the Classic version of Slashdot.

Thank you!

Before you choose to head back to the Classic look of the site, we'd appreciate it if you share your thoughts on the Beta; your feedback is what drives our ongoing development.

Beta is different and we value you taking the time to try it out. Please take a look at the changes we've made in Beta and  learn more about it. Thanks for reading, and for making the site better!


Following instructions. (1)

Merls the Sneaky (1031058) | about a year ago | (#42047961)

I assume that the update comes with a warning about turning off power during update installation I also assume that the update takes some time? If these assumptions are correct why are people turning the WiiU off during the process? Are they dumb asses? They don't even deserve a warranted repair/ replacement if that is the case.

Re:Following instructions -- cuz it takes HOURS (1)

neurocutie (677249) | about a year ago | (#42048195)

uh... because the update is FIVE GB in size, and with some people's connections, can take hours to download and install. A broken connection within these HOURS, not just a few minutes, can brick the Wii U. Seems like they should have just sent out/distributed update discs instead...

Re:Following instructions -- cuz it takes HOURS (1)

JustNiz (692889) | about a year ago | (#42050305)

I'm already surprised that they didn't make the flash large enough to hold 2 firmware images, so that they can validate the most recently flashed image before they make it 'live', and fall back to the old one if the new one doesn't check out.

But sorry I just cant believe your comment can be factual.
I just can't believe even Niintendo would actually be stupid enough to start overwriting the flash while the new image is still being downloaded. Its just basic common sense to download it first (to SD I presume in the case off the Wii U) then only begin to reflash after the download passes size, checksum (and probably authenticity signature) validation.

Re:Following instructions -- cuz it takes HOURS (1)

sjames (1099) | about a year ago | (#42052965)

Ideally, they would do that and have a toggle that flips the two segments in memory based on the reset line. The firmware goes into the alternate bank and then you hit reset. If it all works out, copy the (now primary) new image over the old. If anything goes wrong during any reflash, reset will put it right again.

Re:Following instructions -- cuz it takes HOURS (1)

JustNiz (692889) | about a year ago | (#42054661)

why copy it over the old image? just use it in place.

Re:Following instructions -- cuz it takes HOURS (1)

sjames (1099) | about a year ago | (#42057823)

So that next time someone hits reset they don't end up going back to the old firmware.

If instead of a commonly used control like reset, there is a special recovery switch, the copy-over is unnecessary.

Re:Following instructions -- cuz it takes HOURS (1)

JustNiz (692889) | about a year ago | (#42070123)

Just have it so after you've flashed the new bios and it gets checksummed and found good, it gets marked as valid.
Then whenever you reset or power up, the boot loader just jumps to the entrypoint of whichever bios in flash is market valid and has the latest version number.
Obviously next time you flash the bios, which one it overwrites depends on which is valid and/or oldest.

Re:Following instructions -- cuz it takes HOURS (1)

sjames (1099) | about a year ago | (#42070407)

That's fine if you aren't flashing the bootloader itself. The scheme I outlined allows for a safe re-flash of everything.

Re:Following instructions -- cuz it takes HOURS (1)

Kiralan (765796) | about a year ago | (#42063589)

Agreed. Motherboards have been doing this for YEARS! At the very least, have a minimal permanent/ROM Bios that can do a download.

Re:Following instructions. (1)

Captain Spam (66120) | about a year ago | (#42048217)

I have to wonder when the user's powering it off during this process. If it's being bricked when powered off during the download phase (before the firmware gets flashed), then it's a point of concern, since it should be stuffing that data into a holding area before it does a single thing with it.

However, if it's during the flashing phase, well, then that's the user's stupid fault. They DO throw warnings all over the place. But, knowing Nintendo, there's a nonzero chance that the download/update screen are one in the same and you get no indication which it's doing at a given moment. I mean, this IS a company that, last I knew, still didn't understand the basic OS concept of hardware abstraction...

Check for New Comments
Slashdot Account

Need an Account?

Forgot your password?

Don't worry, we never post anything without your permission.

Submission Text Formatting Tips

We support a small subset of HTML, namely these tags:

  • b
  • i
  • p
  • br
  • a
  • ol
  • ul
  • li
  • dl
  • dt
  • dd
  • em
  • strong
  • tt
  • blockquote
  • div
  • quote
  • ecode

"ecode" can be used for code snippets, for example:

<ecode>    while(1) { do_something(); } </ecode>
Sign up for Slashdot Newsletters
Create a Slashdot Account