Recent Posts

Pages: [1] 2 3 ... 10
Software (PC and Mobile Apps) / Re: Could not retrieve firmware version from Gecho
« Last post by mario on November 26, 2018, 08:35:47 PM »
Yes the STM32 Flash Loader is a bit finicky when it comes to timing, or maybe it's the internal state of MCU, but it eventually works. For example it does not leave enough time for global erase by default, you need to change the timeout to about 10 seconds, or just ignore the warnings and flash it without erasing next time.

Thanks for sharing your observations - happy to hear you figured it out! :D

Software (PC and Mobile Apps) / Re: Could not retrieve firmware version from Gecho
« Last post by keppeco on November 24, 2018, 01:01:40 AM »
Good news!  I was able to get the flash loader to work by keeping the Gecho off when plugging it in, then activating the flash loader at a specific time very soon after plugging in.
Software (PC and Mobile Apps) / Re: Could not retrieve firmware version from Gecho
« Last post by keppeco on November 24, 2018, 12:43:16 AM »
Thanks for the quick response, mario, this is a real head scratcher! It does sound similar to the other post.  My CH340 comes up as COM9 in the device manager.  Where it gets really interesting is that when I try to run the STM32 Flash Loader, select COM9 and hit next, I get this error message:

No response from the target, the Boot loader can not be started.
Please, verify the boot mode configuration and the flash protection status,
Reset your device then try again...

I will post a video in a bit, I just wanted to give this update now in case it provides anymore clues.
Great stuff! Hope you like the new functions! More to come, I will fix the app soon 8)
Software (PC and Mobile Apps) / Re: Could not retrieve firmware version from Gecho
« Last post by mario on November 23, 2018, 11:54:06 PM »
Hi! Sorry to hear it doesn't "just work" as intended  ???

If RDY is blinking, and app claims to not be able to connect, it might be the same issue as discussed here?

The problem is that auto-detect feature is pretty basic and may confuse other COM port for Gecho's port. Can you try to run the app without Gecho attached, that would prove this is the problem.

Otherwise, feel free to share a short video, that's usually very helpful.

I will update the app soon so it has better auto-detect and allows to choosing the correct COM port manually.
Software (PC and Mobile Apps) / Could not retrieve firmware version from Gecho
« Last post by keppeco on November 23, 2018, 11:30:16 PM »
I've missed a couple firmware updates and got excited for the granular synth, but when I try to update my firmware, I get the error message:

Could not retrieve firmware version from Gecho.
Looks like it is not in Ready state (was not powered on and reset, or there is no firmware at all).

My ready light is blinking, and my USB light blinks in 3 shorts bursts of 2.  I have tried plugging it in before turning it on, plugging it in after turning it on, running the app before and after turning it on, and hitting reset all the ways.  I also installed the CH340G driver as mentioned in the other post.  I'm running Win 10 64.  Hopefully this is all the information needed!
Yes, the manual update worked, eventually. I got a few repeated errors, either 'cannot erase flash' or 'cannot download image', but it seemed to take eventually and now it's working on the new firmware.

Thank you for looking further into it, it's really helpful. Just checked the source code and originally it was looking specifically for "USB-Serial" type of COM ports but later it was changed to just go over all ports, I vaguely remember this was changed as on some systems the virtual COM port was showing under a different random name and therefore wasn't detected. It looks for all "active" ports, whatever that means - I guess the problem is that a hardware type port is always active no matter if something is plugged into it.

The "auto-detect" might still work as intended, just needs to check if there is a meaningful reply from the device... but will add a manual override anyway, it's easy enough. Meanwhile, hope you will be more lucky with the manual update process! :)
I don't have anything with the same driver but I do have two other COM ports ('Communications Port' on COM1, and 'Intel Active Management Technology' on COM3). The Gecho appears as COM4. If I disable the COM1 port (from the device manager) I do get an error from the app about being unable to open COM1 properly. Does the app actually search for CH340 devices, or does it just enumerate the COM ports and use the first one it finds?

Allowing you to select a COM port from the gecho app would be really useful at this point! I can't easily switch around such that the gecho appears on COM1 because the other two ports are present from system startup.

I'll look into the manual update utility then, if I can select COM4 directly from there.

Thanks for all the help!
This is very suspicious indeed :) In the video it all looks good. The App definitely should complain when you don't have Gecho plugged in, I just tested it in my computer with v0.61b freshly downloaded from the website.

Any chance you have something else plugged in that might use the same driver? I would not think you are leaving your Arduino permanently connected but some other random device that uses USB-serial. If you look into control panel, you should see it (as shown in the first picture here). That would explain it, Gecho app finds first thing that looks familiar and tries to communicate with it.

It would be interesting to know if it was that. I should make it smarter and let it go over all active ports if more found, until a valid response is received.

The manual update utility will work fine as you can tell it to use the other virtual COM port.

And yes the commands for s/n and version were added later (by the way not too useful right now but you can check what applies to your firmware by looking at legacy manual version, links are at the bottom, i guess this one is for you:
Pages: [1] 2 3 ... 10