Re: [M100] odd REX error - anybody run into this?
Might also check that none of the solder joints have gone bad. The board might start out fine but as the solder oxidizes over time a badly soldered joint could fail. Re-programming may resolve the problem but if there is a bad joint it will just happen again or you may not be able to reprogram the device. Worth a close inspection to make sure especially with hand assembled part. Could also try this REX in another machine see if it behaves the same way. On 29/6/18, 8:20 AM, "M100 on behalf of Jim Anderson" wrote: >> -Original Message- >> >> So, on powerup, the 100 loads directly to REXMGR w/o it being invoked? > >Exactly. > >> When you get back to main, does CALL 63012 do anything? > >It installs REXMGR on the menu, as you'd expect. Launching REXMGR gets >you stuck back at the same screen again, though. > >> Did you make sure to remove the flux after soldering? The flash chip >> is especially sensitive to excess flux residue (in my experience). > >I don't think I did. I used a flux pen and a barely-visible amount of >flux when I built it so I don't know if there's really anything there to >remove. I'd have to check. > >This issue can most likely be resolved by re-loading the REX software, >but I'm just hoping for an alternative fix that might keep the data >intact - my son is very concerned about losing his stuff (although he was >only gone to his mom's house for two days with it so I can't imagine he's >lost much - there was a program he was working on to play a new song he's >been composing). > > > > > > > > jim
Re: [M100] odd REX error - anybody run into this?
> -Original Message- > > You might try unseating REX, checking that the metal fingers in the > socket > are all ok and working, then re-seat REX. Just trying to think of > something. Good point - I did try re-seating the module (no luck) but I should make a physical examination of the socket and also try swapping it with the working REX from my machine, when I next have a chance. jim
Re: [M100] odd REX error - anybody run into this?
> -Original Message- > > So, on powerup, the 100 loads directly to REXMGR w/o it being invoked? Exactly. > When you get back to main, does CALL 63012 do anything? It installs REXMGR on the menu, as you'd expect. Launching REXMGR gets you stuck back at the same screen again, though. > Did you make sure to remove the flux after soldering? The flash chip > is especially sensitive to excess flux residue (in my experience). I don't think I did. I used a flux pen and a barely-visible amount of flux when I built it so I don't know if there's really anything there to remove. I'd have to check. This issue can most likely be resolved by re-loading the REX software, but I'm just hoping for an alternative fix that might keep the data intact - my son is very concerned about losing his stuff (although he was only gone to his mom's house for two days with it so I can't imagine he's lost much - there was a program he was working on to play a new song he's been composing). jim
Re: [M100] odd REX error - anybody run into this?
You might try unseating REX, checking that the metal fingers in the socket are all ok and working, then re-seat REX. Just trying to think of something. Bob -Original Message- From: M100 [mailto:m100-boun...@lists.bitchin100.com] On Behalf Of Jim Anderson Sent: Friday, June 29, 2018 2:11 AM To: m...@bitchin100.com Subject: [M100] odd REX error - anybody run into this? My son's REX (in his M100) is in a strange state. I don't know what exactly he did just before initially getting this message, but now he gets this every time he runs REXMGR. The REXMGR screen appears with the top line saying "REX 4.9 M Group:RAM" and the rest of the screen blank except for the following on the bottom line: "no blank sector pair found" Cold reset and CALL 63012 just leads back to the same screen. The "no blank sector pair found" message is flickering every second or so, as though it is being re-drawn. Any ideas? Is there a possibility of recovering from this with the contents of flash intact, or are we going to have to go straight to reloading REXMGR into the module so it re-formats the flash? jim
Re: [M100] odd REX error - anybody run into this?
On Fri, Jun 29, 2018 at 8:28 AM, Jim Anderson wrote: > > Can't get to the ROM menu - it's stuck at this point and doesn't respond to > any keystrokes. Power cycling brings it right back to the same screen - you > have to use the reset button to get back to the M100 main menu. So, on powerup, the 100 loads directly to REXMGR w/o it being invoked? When you get back to main, does CALL 63012 do anything? >> Where did you get your REX device, and how old is it? > > The kids and I built our own as a family project last fall - total of four > modules. Did you make sure to remove the flux after soldering? The flash chip is especially sensitive to excess flux residue (in my experience). -Josh
Re: [M100] odd REX error - anybody run into this?
> -Original Message- > > Do option ROM images still work? I've never encountered this before, > but it kinda sounds like all the flash sectors have been filled, which > I didn't think was possible. Either that, or the flash has failed > somehow. Stephen would probably know better than I though. Can't get to the ROM menu - it's stuck at this point and doesn't respond to any keystrokes. Power cycling brings it right back to the same screen - you have to use the reset button to get back to the M100 main menu. > Where did you get your REX device, and how old is it? The kids and I built our own as a family project last fall - total of four modules. jim
Re: [M100] odd REX error - anybody run into this?
Do option ROM images still work? I've never encountered this before, but it kinda sounds like all the flash sectors have been filled, which I didn't think was possible. Either that, or the flash has failed somehow. Stephen would probably know better than I though. Where did you get your REX device, and how old is it? -Josh On Fri, Jun 29, 2018 at 2:11 AM, Jim Anderson wrote: > My son's REX (in his M100) is in a strange state. I don't know what exactly > he did just before initially getting this message, but now he gets this every > time he runs REXMGR. The REXMGR screen appears with the top line saying "REX > 4.9 M Group:RAM" and the rest of the screen blank except for the > following on the bottom line: "no blank sector pair found" > > Cold reset and CALL 63012 just leads back to the same screen. The "no blank > sector pair found" message is flickering every second or so, as though it is > being re-drawn. > > Any ideas? Is there a possibility of recovering from this with the contents > of flash intact, or are we going to have to go straight to reloading REXMGR > into the module so it re-formats the flash? > > > > > > > > jim >
