Re: [M100] Rex# Crash on an M102
Thanks for the updates! I tried the following: 1. Flash REX# firmware via TPDD, which appeared to work but then exhibited the same behavior of trying to load some ghost image on start and then crashing 2. Flash REX# with the test.do, which I realize would lose the flash images but I've got backups. However this also crashes, though with some old-school panache, video here: https://photos.app.goo.gl/XfT9VQaVRBXG4HHM7 @Steve Thank you for the offer but I am pretty sure I have things backed up. If I don't have any luck doing the full reflash, I may drop you a line directly. This 102 is occasionally flakey, so once I'm back near another machine I will give it one more go and see if it's 102 specific or if I've bricked my poor rex. Thanks again, -Charlie On Fri, May 26, 2023 at 12:32 AM Brian K. White wrote: > First thing verify the connection to all the pins in the socket. It's a > common weak point. No weak/compressed pins, no oxidization, rex# fully > seated etc. > > Otherwise what Steve said, run the install/update tool to reflash the Rex#. > > -- > bkw > On 5/25/23 21:27, Charlie Hoey wrote: > > Hello there! > > > > I had my first crash on a Rex# that I can't get myself out of, curious > > if anybody has any tips. > > > > I was in the process of creating a clean bank for a new project, and it > > failed somewhere near the end. I RESET and then ran `CALL 63012` to > > reload REX, but now whenever I start REXMGR, it attempts to load/write > > something and hangs. I've done a cold reset, pulled batteries etc, so I > > think it's in eeprom/flash somewhere. Here's a shot of what I'm seeing: > > > > Screen Shot 2023-05-25 at 9.13.23 PM.jpg > > If images don't work here, launching REXMGR shows the standard top line > > with "REX #2.1" in the top left, and the bottom right is the progress > > bar, which fills up most of the way and then hangs. > > > > Any way I might peek/poke my way back to a usable state? I don't care > > about the in progress job that failed, so if I could clear a flag or get > > it to just abandon it that would be fine. > > > > Thanks as always! > > -Charlie > > >
Re: [M100] Rex# Crash on an M102
First thing verify the connection to all the pins in the socket. It's a common weak point. No weak/compressed pins, no oxidization, rex# fully seated etc. Otherwise what Steve said, run the install/update tool to reflash the Rex#. -- bkw On 5/25/23 21:27, Charlie Hoey wrote: Hello there! I had my first crash on a Rex# that I can't get myself out of, curious if anybody has any tips. I was in the process of creating a clean bank for a new project, and it failed somewhere near the end. I RESET and then ran `CALL 63012` to reload REX, but now whenever I start REXMGR, it attempts to load/write something and hangs. I've done a cold reset, pulled batteries etc, so I think it's in eeprom/flash somewhere. Here's a shot of what I'm seeing: Screen Shot 2023-05-25 at 9.13.23 PM.jpg If images don't work here, launching REXMGR shows the standard top line with "REX #2.1" in the top left, and the bottom right is the progress bar, which fills up most of the way and then hangs. Any way I might peek/poke my way back to a usable state? I don't care about the in progress job that failed, so if I could clear a flag or get it to just abandon it that would be fine. Thanks as always! -Charlie
Re: [M100] Rex# Crash on an M102
Charlie, Hard to say what's wrong. In an ideal situation, I'd like to get it back and root cause the problem. So, yoo could send it back and I send you a replacement. Short of that, a rebuild would be what is needed. Release 2.1 to do a rebuild are posted on the wiki, along with instructions. Option 1. Refresh the rom. This puts a freshness copy of rex manager in the flash. It preserves your saved images and directory. If that does not work.. Option 2. Rebuild. This is a complete wipe and reset to original, erasing the contents. Your rom images are likely there and still fine. I've never written tools tor ecover them. If you need those images I could probably recover them for you if you send me the rex#. ..steve On Thursday, May 25, 2023, Charlie Hoey wrote: > Hello there! > > I had my first crash on a Rex# that I can't get myself out of, curious if > anybody has any tips. > > I was in the process of creating a clean bank for a new project, and it > failed somewhere near the end. I RESET and then ran `CALL 63012` to reload > REX, but now whenever I start REXMGR, it attempts to load/write something > and hangs. I've done a cold reset, pulled batteries etc, so I think it's in > eeprom/flash somewhere. Here's a shot of what I'm seeing: > > [image: Screen Shot 2023-05-25 at 9.13.23 PM.jpg] > If images don't work here, launching REXMGR shows the standard top line > with "REX #2.1" in the top left, and the bottom right is the progress bar, > which fills up most of the way and then hangs. > > Any way I might peek/poke my way back to a usable state? I don't care > about the in progress job that failed, so if I could clear a flag or get it > to just abandon it that would be fine. > > Thanks as always! > -Charlie >
[M100] Rex# Crash on an M102
Hello there! I had my first crash on a Rex# that I can't get myself out of, curious if anybody has any tips. I was in the process of creating a clean bank for a new project, and it failed somewhere near the end. I RESET and then ran `CALL 63012` to reload REX, but now whenever I start REXMGR, it attempts to load/write something and hangs. I've done a cold reset, pulled batteries etc, so I think it's in eeprom/flash somewhere. Here's a shot of what I'm seeing: [image: Screen Shot 2023-05-25 at 9.13.23 PM.jpg] If images don't work here, launching REXMGR shows the standard top line with "REX #2.1" in the top left, and the bottom right is the progress bar, which fills up most of the way and then hangs. Any way I might peek/poke my way back to a usable state? I don't care about the in progress job that failed, so if I could clear a flag or get it to just abandon it that would be fine. Thanks as always! -Charlie
