(Topic ID: 267078)

Stern SAM code update error code 1

By FatPanda

1 year ago


Topic Heartbeat

Topic Stats

  • 17 posts
  • 6 Pinsiders participating
  • Latest reply 1 year ago by FatPanda
  • Topic is favorited by 3 Pinsiders

You

Linked Games

No games have been linked to this topic.

    Topic Gallery

    View topic image gallery

    20200423_212426 (resized).jpg
    20200423_163947 (resized).jpg
    20200423_212619 (resized).jpg
    20200423_212421 (resized).jpg
    Screenshot_20200423-222539_Video Player (resized).jpg
    Screenshot_20200423-141218_Chrome (resized).jpg
    20200423_134840 (resized).jpg

    #1 1 year ago

    Trying to install the latest code on a recently acquired Iron Man VE. I downloaded the code from their site (already a .BIN file). Copy the file onto a freshly formatted 16gb drive, switch Dip switch 8 to on, and start the update procedure. When the game completes the ERASE FLASH operation, it fails to upload the code and displays ERROR CODE 1.

    I've tried 3 different drives and they are all do the same. I've tried to download the code again 2 more times, and the result is the same.

    I sent Stern an email since they aren't taking calls right now, but was hoping someone already went through this knows how to resolve it.

    UPDATE: Resolution in Post #11

    #2 1 year ago
    20200423_134840 (resized).jpg
    #3 1 year ago

    Correction: it doesnt even complete the erase process. It stops at around 60/134 and shows the error message.

    #4 1 year ago

    Have you downloaded the correct code ? There are separate downloads for the original and the vault.

    #5 1 year ago
    Quoted from stoptap:

    Have you downloaded the correct code ? There are separate downloads for the original and the vault.

    Yes, I have the VE version of the code.

    #6 1 year ago

    I saw this on google groups so I swapped the flash RAM from my TWD, which I know is working, and came up with the same error.

    Coincidence that it's the same game too???
    Screenshot_20200423-141218_Chrome (resized).jpg

    #7 1 year ago

    Anyone have any thoughts? Really frustrating as the game was working fine at v1.81 before I tried to update. Now it does nothing.

    I ordered a new USB stick, PNY 8 Gb, as a glimmer of hope that it'll work, but I'm doubtful. Since its having issues erasing the old code, I dont think the USB stick is the problem.

    I've tried two computers plus I'll bring home my work computer tomorrow to try that one also.

    #8 1 year ago

    Is the file in the root file of the usb. Did you try the verify code option to see if the code is corrupt?

    #9 1 year ago

    You could try installing an older version of the code.

    #10 1 year ago
    Quoted from stoptap:

    You could try installing an older version of the code.

    Or the code for the orginial version and not the vault?

    #11 1 year ago

    I got it figured out. I was told by someone very knowledgeable about the SAM system that it was an error erasing a flash sector and said it was very rare, and it had confirmed my suspicions. Thank you sir_tankalot !

    My wife came across this thread from another forum, which was difficult to find given the thread title:

    https://www.pinballinfo.com/community/threads/stern-updating-sam-old-chestnut.39537/

    Basically, he was reporting differences between his boot chip, 128M, and others' boot chips, 64M. He was also updating IMVE and getting Error Code 1 (again, similar to the screen cap I made above). He was convinced that was the issue but never posted the actual resolution.

    On my game, with the 128M boot chip factory installed, the game would try to erase 134 Million bytes (?) of memory, and would fail at around 69 Million bytes. The reason my TWD boot chip didn't work was because it was the same 128M. The chips were functional. I think the problem was that the boot chip was expecting to see 134M of memory (if this is what that means) and was only seeing 69M. It couldn't finish its complete 134M operation, so it errors out.

    Going back to the thread, I just happen to have an XMLE (2012) lying around, and thought that it was a similar era of the OG IM (2010), and I knew that my USB drives weren't the issue because the game never even got to accessing the data on the drives, it would error out before that, so I decided to swap the boot chip from my XMLE. With this chip, it was only looking for 33.5M of memory to flash, and seeing that the update file was only ~29 Mb, I was hopeful. And it worked! It completed its 33M erase, then proceeded to update the 29 Mb file successfully. I flipped about a half dozen games last night afterwards.

    Pic of the operation with the 128M boot chip
    Screenshot_20200423-222539_Video Player (resized).jpg

    Pic with the XMLE boot chip
    20200423_212421 (resized).jpg

    Pic of the file upload
    20200423_212619 (resized).jpg

    Pic of the actual 128M boot chip
    20200423_163947 (resized).jpg

    Pic of the XMLE boot chip
    20200423_212426 (resized).jpg

    Hopefully this will be easier to find for those that encounter this problem in the future, given the thread title. I was getting really bummed out after a while but glad I was able to resolve it.

    #12 1 year ago

    Great stuff and great knowledge for the future.

    #13 1 year ago
    Quoted from FatPanda:

    I got it figured out. I was told by someone very knowledgeable about the SAM system that it was an error erasing a flash sector and said it was very rare, and it had confirmed my suspicions. Thank you sir_tankalot !
    My wife came across this thread from another forum, which was difficult to find given the thread title:
    https://www.pinballinfo.com/community/threads/stern-updating-sam-old-chestnut.39537/
    Basically, he was reporting differences between his boot chip, 128M, and others' boot chips, 64M. He was also updating IMVE and getting Error Code 1 (again, similar to the screen cap I made above). He was convinced that was the issue but never posted the actual resolution.
    On my game, with the 128M boot chip factory installed, the game would try to erase 134 Million bytes (?) of memory, and would fail at around 69 Million bytes. The reason my TWD boot chip didn't work was because it was the same 128M. The chips were functional. I think the problem was that the boot chip was expecting to see 134M of memory (if this is what that means) and was only seeing 69M. It couldn't finish its complete 134M operation, so it errors out.
    Going back to the thread, I just happen to have an XMLE (2012) lying around, and thought that it was a similar era of the OG IM (2010), and I knew that my USB drives weren't the issue because the game never even got to accessing the data on the drives, it would error out before that, so I decided to swap the boot chip from my XMLE. With this chip, it was only looking for 33.5M of memory to flash, and seeing that the update file was only ~29 Mb, I was hopeful. And it worked! It completed its 33M erase, then proceeded to update the 29 Mb file successfully. I flipped about a half dozen games last night afterwards.
    Pic of the operation with the 128M boot chip
    [quoted image]
    Pic with the XMLE boot chip
    [quoted image]
    Pic of the file upload
    [quoted image]
    Pic of the actual 128M boot chip
    [quoted image]
    Pic of the XMLE boot chip
    [quoted image]
    Hopefully this will be easier to find for those that encounter this problem in the future, given the thread title. I was getting really bummed out after a while but glad I was able to resolve it.

    Awesome. Thank you for posting this.

    #14 1 year ago
    Quoted from FatPanda:

    128M boot chip factory installed, the game would try to erase 134 Million bytes (?)

    128Mbit is the same as 134,217,728 bits. 1KB = 1024 bits and 1MB = 1024 Kb, so 1 Mb is equal to 1,048,576 bits; multiply that by 128 and you get 134,217,728

    Time to make copies of my Boot ROMs...just in case

    #15 1 year ago

    I did receive confirmation from Lyman that the correct boot EPROM should be 64M, same as Mustang and Star Trek. A good thing to note for anyone getting SAM VE's that if they are getting this error, that the incorrect boot EPROM might be installed.

    #16 1 year ago
    Quoted from FatPanda:

    I did receive confirmation from Lyman that the correct boot EPROM should be 64M, same as Mustang and Star Trek. A good thing to note for anyone getting SAM VE's that if they are getting this error, that the incorrect boot EPROM might be installed.

    so by that logic the game rom you had installed was factory flashed and a machine based game rom upgrade would have never successfully been performed before?

    #17 1 year ago
    Quoted from koops:

    so by that logic the game rom you had installed was factory flashed and a machine based game rom upgrade would have never successfully been performed before?

    My game was built JUL 23, 2014. They had revisions on JUL 5, 2014 (v1.81) and JUL 17, 2014 (v1.82) so my game probably had 1.81 from the factory without ever getting an update. Plus it was routed, and completely feasible that it was never updated by the Op.

    Hey there! Got a moment?

    Great to see you're enjoying Pinside! Did you know Pinside is able to run thanks to donations from our visitors? Please donate to Pinside, support the site and get anext to your username to show for it! Donate to Pinside