Since the last release there's been no serious bugs, thus a lengthy break before the new version: 20210406

• Fixed false crash report when launching multiple instances of the program
• Option to check write protection before writing is defaulted to on
• Added event log column width auto resize option
• Added detailed connection and reading events
• Removed excess debug error messages
• Improved connection performance

thank you so much for this project - the code and explanations are all very well done - thanks

short question on using the GUI code - when it reports RSWP unavailable - does this mean that there is something wrong with the circuit - SA0, SA1, or HV ?

or is it related to the RSWP set on the module (which seems to report accurately - 2 blocks enabled, 2 blocks disabled for the module that I am testing) - but Clear RSWP is gray

thanks

er1pp
thank you so much for this project - the code and explanations are all very well done - thanks

short question on using the GUI code - when it reports RSWP unavailable - does this mean that there is something wrong with the circuit - SA0, SA1, or HV ?

or is it related to the RSWP set on the module (which seems to report accurately - 2 blocks enabled, 2 blocks disabled for the module that I am testing) - but Clear RSWP is gray

thanks

Hi,
 
If it says RSWP unavailable, then it failed to test or toggle SA0, SA1, or HV switches.
 
(I just noticed the schematic shows the SA0 control is optional, but it is still checked in the code before enabling RSWP controls. Give me a few moments, I'll prepare a new build which will ignore SA0 state to work with RSWP features.)
 
But SA1 and HV control circutries are still required, so make sure those are wired up properly.
 
 
Edit: see one post below

Done, here's the promised release: 20210411

• Fixed crash on scrolling if mouse wheel vertical scroll option is set to 'One screen at a time'
• Window state is restored properly when 'Remember window size and position' is enabled
• SA0 pin control is no longer required to enable RSWP operations

 

thanks for the quick answer & the quick turn-around for new code - this works for me & my RSWP are enabled now
 
thanks again for sharing all the effort that you have put into this project 
 

New version, mostly cosmetic updates: 20210416

• Fixed devices disappearing when changing serial port settings
• Connected device will not disconnect when changing serial port settings
• Modified settings are highlighted before they are applied
• Added option to hide some toolbar buttons
• Settings window can be resized

Nice work. I've done some Arduino work before, but I just don't have the patience for something like this. Wow!

Thank-you for this easy to build and use tool!
It was well documented enough for me to build and use it to unlock RSWP on my memory modules!
 
However, I did encounter a problem while using this tool.
When I tried to use the GUI tool to unlock RSWP, the menu was greyed out, and the log suggested that RSWP functionality was unavailable.
However, conversely, the serial monitor worked fine, and RSWP was unlocked successfully, though no success message was returned.
This is weird since a success message is supposed to be returned according to the code?
 
But weirdly enough, thaiphoon and your GUI shows that it is indeed unlocked.
 
=== Edit ===
After checking again, it seems it has locked itself again..?
But I have checked every connections, and it seems to have been connected according to the schematic..
Hmm..

Make sure there are no loose connections and everything is assembled properly. RSWP controls are disabled when HV_CTL and SA1_CTL checks fail during the initial connection. Also make sure the pins are assigned properly in the firmware configuration file if you didn't use the default ones.
 
Inconsistent RSWP behavior suggests loose or missing connection.
 
If you have a multimeter, PM me and I'll guide through troubleshooting steps to find out why RSWP isn't working.

a213m
Make sure there are no loose connections and everything is assembled properly. RSWP controls are disabled when HV_CTL and SA1_CTL checks fail during the initial connection. Also make sure the pins are assigned properly in the firmware configuration file if you didn't use the default ones.
 
Inconsistent RSWP behavior suggests loose or missing connection.
 
If you have a multimeter, PM me and I'll guide through troubleshooting steps to find out why RSWP isn't working.

Thanks. So, I've checked every single solder joint with the multimeter, but have not found ANY connections that I've missed.
After that, I just figured I had a bad Arduino and started over with just SA1_CTL and HV_CTL / HV_DET, but I didn't have another nano, so I just went ahead with a pro micro.
The pro micro doesn't have a 3.3v output, so I had to salvage an AMS1117 3.3 from a broken board that I had, but I managed to get that working.
 
The nano that I used was a bit dodgy. The USB wasn't working half the time, (probably the cable though), and the stock bootloader was the old variant, so I had to flash a new bootloader and etc.
I guess that I just drew the short straw. Soldering it on the perfboard didn't help either, cuz troubleshooting meant tons of desoldering and soldering 😂
(But I soldered the pro micro too though lol)
 
Anyways, the new one with the pro micro worked without any major hiccups.
Thanks again for the open source tool! People like you drive the development of our community! 😀
 
P.S. It would be great if a self-check sort of a function was implemented, so we could more easily diagnose a problem on the board.
Also, it would be helpful if I could know which test the program failed to validate, just for debug reasons.