-->
Page 1 of 2

Can No Longer Flash My NodeMCU

PostPosted: Thu Aug 04, 2016 6:04 pm
by raintime
I have flashed successfully many times using my COM34 port, which is the serial port connected to my nodemcu.

When I run TERMITE it finds: COM1 , COM26, COM28 and COM34, which is correct.

When I run the latest flasher, it says: Com port 1 found , Com port 26 found , Com port 28 found.

But it does not find the one COM port that I need! - COM34.

Please look into this, since I can no longer flash my nodemcu with the latest BASIC!

Re: Can No Longer Flash My NodeMCU

PostPosted: Fri Aug 05, 2016 1:12 am
by forlotto
I know you want this fixed and I am sorry if you feel your donation was a waste provide me with a receipt and I will gladly refund you for buying mike some beers I just know how hard this guy works at this project personally I couldn't imagine handling all of these requests being one person to be honest and to do it all free of charge because he believes in open things and supporting this.

Now beyond this here are some things that may hold you over or things to test...
Did you try typing in the numbers 34 for the time being and see if that works?

There is an alternate method that will hold you over for the time being if this is the case so you can get the latest version http://www.electrodragon.com/w/Category ... re_and_SDK if you visit the github source and download the 4MB version of the latest build in the flasher folder and flash it 0x0000000 load that binary sync with the flash button and you have the latest version.

It is also possible your coms got tied up things like restarting your pc often helps this issue.

Now you may already know all of these things but in the event you do not I am sharing.

You could also download the previous flasher and put the new builds in the build folder that the flasher creates when you execute it.

Hope this helps will have to wait on mike to see what is what but just try to be sure it is not something possibly on your end at this time I need sleep or else I would test I wish you the best and as I say I'd gladly refund you if you felt your donation was not a worthwhile thing or cause sorry for the promotion I guess but he really did work tirelessly for days wrapping up a lot of huge bugs and I know I personally annoyed the crap out of him trying to help things along so if anyone is responsible for your donation it is me I will gladly refund you! It was an excellent gesture though and if I mistook you apologies it is easy to do online.

Re: Can No Longer Flash My NodeMCU

PostPosted: Fri Aug 05, 2016 1:27 am
by schufti
just go in device manager and change com34 to something much lower ...
and for heavens sake clean up your COM devices: enable "show hidden devices" and delete all COMs that you don't need right now. They will reappear when connected next time (but with different number)

Re: Can No Longer Flash My NodeMCU

PostPosted: Fri Aug 05, 2016 12:02 pm
by raintime
Forlotto,

Thanks for your reply and concept of using the electrodragon flasher. This might come in handy later. And your idea of using an earlier flasher along with the latest build in the same directory! As it turns out there was a simple way to fix my problem that Mike mentioned to me: Simply type 34 into the combo box! I didn't think of that because combo boxes I have used in the past are read-only and don't let me type new things in!

I certainly do NOT want a refund for the beers I sent Mike's way! Thanks for offering! I really want to support Mike in this effort, even if it sometimes gets VERY frustrating! This is the most exciting new software development I have seen for years!

Schufti,

Thanks also for your advice - I remember trying to clean up my COM devices using the device manager and it turned out to take a long time and was painful for me. But really, the flasher should work in my current COM environment, which works fine for everything else I use my COM ports for - even though 34 is a big number!