Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - mario

Pages: [1] 2 3 ... 16
1
Firmware - Expanding and updating / Re: PLEASE HELP!
« on: June 10, 2024, 11:59:11 AM »
Hi Adi,
It looks safe to update now, I've heard from 2-3 people for whom it worked without issues.
And here is a short demo of channel #133 made by our friend Denis: https://www.instagram.com/p/C8BcAL9NcKu/
I hope that you can fix your unit easily, if you need any help, I'm here :)
Cheers,
Mario

2
Programming and Hardware / Re: Loopstyler Headless Interface?
« on: June 02, 2024, 11:39:28 AM »
Hi Michael,

Thank you for the first question about Loopstyler, yay! ;D

Yes absolutely, you can connect to it via the virtual COM port at 115200 baud rate, using any common terminal utility (e.g. PuTTY).

To find out which port it is, in Windows you can check control panel / device manager, and in Mac, it should be something like /dev/tty.usbmodemXXXXXX or /dev/cu.usbserial-XXXXXX. It should just work without installing any drivers, it's a very standard USB interface that is widely supported in various operating systems.

It may happen that you can see the port but can't connect to it, then you may need to disable the LS app so it does not take over the resources right after power on. There is a file on SD card in "system" directory named "midi_init_enabled". It triggers this script to run: "/root/start_midi_and_app.sh". If you rename that file to something else, e.g. "midi_init_enabled.not", and power cycle the unit, you will get access to the console. Then, to restart the app from there, you can run the script again using "/root/start_midi_and_app.sh &".

If you can connect without disabling the app, there is a script to stop it (so you can take over the audio interface): "/root/stop_app.sh". It's not a permanent disable, after restart the app will be back.

By connecting you gain root access, no login info necessary. You can look around and try a few debug commands like "dmesg" (kernel log), "cat /proc/iomem" (to show hardware interfaces, for which the device tree configuration is in /boot/sun8i-v3s-ls257.dtb), "mount" (list file systems), "fdisk -l" (list SD card partitions), "top" (interesting to see the CPU load while something plays) etc.. There are also commands available to play and record various formats: "aplay", "arecord" and "mpg123" (LS could be a MP3 player too). Also SOX command and library is available for processing audio files. Voice messages that LS uses are in /data/voice/ and could be replaced with another voice, keeping the file names.

Have fun and let me know if you need any help or advice.

Cheers,
Mario

3
Firmware - Expanding and updating / Re: PLEASE HELP!
« on: June 01, 2024, 09:14:38 PM »
Oh no, looks like there was another problem - which only appeared in units in 2nd half of the first batch (s/n. 500 and above) just when I thought it was all sorted. This time it was a problem with the server rather than code :o

I guess after updating, your unit just started playing a random channel and could not be stopped?

The good thing is that there is a simple fix for this: you can reset it back with the same method as previously, then re-download and apply the firmware again.

Maybe even quicker method is using the service menu which should still work - accessible by holding RST when powering on, then command B3 to revert back to previous version.

Thank you for bearing with me and for beta-testing this!

4
Firmware - Expanding and updating / Re: PLEASE HELP!
« on: June 01, 2024, 04:21:27 PM »
Thank you Adi!  8)
It should work now, maybe check the file size after downloading, it should be 734896 bytes (the previous bad one was 733728 bytes) to make sure that it's not a version cached by the browser or something like that (as the file name did not change).
Fingers crossed all works without issues this time!

5
Firmware - Expanding and updating / Re: PLEASE HELP!
« on: June 01, 2024, 09:43:46 AM »
Hi Adi, that's fantastic news!
This should not happen again, I'll be testing the updates on both versions from now on.
And good to know that there is an easy(ish) fix, once you can find a computer that collaborates :)
The problem that caused it is almost fixed now so I'll try to release the new version over the weekend.
(still puzzled why this did not happen in the previous releases, we had 2 versions of PCBs for a while now)
Really sorry about all the hassle that this caused to you!

6
Hi Adrian,

That is very strange problem. Using the B3 option in service menu repeatedly should not have any effect, as there is only one "original firmware" and once you are there, this should not change anything.

You say that the unit seems to behave normally (reacts to buttons and animates LED lights), just that there is no sound?

Have you tried to reset the settings? (4321-SET). I guess you have but asking just in case.

I doubt that a firmware update will fix this (the problem cannot simply be a corrupt firmware because there is a self-check and it wouldn't run at all).

Do you use Windows by any chance? we could diagnose the problem by downloading content of the Flash memory and analyzing it. If yes, please try what is suggested in this post, once you get to the point where you can use the esptool.py script to communicate with the Loopsynth, we will be able to figure out whether the issue is on the software or hardware side.

Cheers,
Mario

7
Firmware - Expanding and updating / Re: PLEASE HELP!
« on: May 31, 2024, 07:05:15 PM »
There is a way how to make it work on Mac, you need to have the FTDI driver installed, if it's missing you can find it here: ftdichip.com/drivers/vcp-drivers/

But I've heard from other Mac users that they usually didn't need to install anything, as it already was in the system.

The Loopsynth should appear as something like /dev/tty.usbmodemXXXXXX or /dev/cu.usbserial-XXXXXX

You can just try to plug it in and see if the online tool can connect.

In Windows, is there some "unknown device" listed somewhere among USB devices, at the very end of the Device Manager list?

Which version is it by the way?



8
Firmware - Expanding and updating / Re: PLEASE HELP!
« on: May 31, 2024, 04:24:16 PM »
how does it look in your control panel / device manager?
some other devices may also appear as virtual serial COM port, if you see one while the Loopsynth is not connectet, that might be it.

if your computer has more USB ports, can you try another one?

if the web tool does not work, there is an alternative flashing firmware, which gives you more control - it can be set up easily in windows using the ESP32 framework installer.
once you see the "command prompt" window, you can try if it connects properly by running the command:

python C:/path/to/esp-idf/components/esptool_py/esptool/esptool.py --chip esp32 --port COM123 read_mac

(just replace path and com port with your values)

however it does not make sense to try that until we're sure that the problem is not a missing driver or bad cable.

9
Firmware - Expanding and updating / Re: PLEASE HELP!
« on: May 31, 2024, 03:45:57 PM »
Hi Adi, so the COM port is detected but can't connect? is the power switch in the OFF position? the only way to reset it is to unplug the power and plug it back again.

10
Firmware - Expanding and updating / Re: PLEASE HELP!
« on: May 31, 2024, 01:25:59 PM »
Hi Adi,

Thank you for your kind words and supporting the project! 8)

Please check this guide: gechologic.com/v2_recovery

Chance is that the first half will be enough (uploading the OTA data file). This should disable the newer problematic firmware and revert back to the older one which previously worked in your unit.

But if not, you can get your original firmware here and upload it as shown in the 2nd half of the guide (or you can start there, and upload both files at once).

After this, the updates should work normally (the update download page will be active once I fix the issue).

Hope this helps!

Cheers,
Mario

11
Firmware - Expanding and updating / Re: PLEASE HELP!
« on: May 28, 2024, 10:15:17 AM »
Hi Adi,

Sorry about this! I've tested the update on 2 units and it worked so I thought it was fine but both of those were from the newer batch (s/n. 1000 and above). Your one is from the first batch and indeed when I tested the update with an older unit, I got the same issue.
There seems to be some incompatibility with the older circuit, it's something new as it did not happen with the previous version so I'll need to investigate.

No worries at all as it's not possible to brick it completely, I'll fix the issue in the firmware and post a guide here about how to restore the functionality.

Cheers,
Mario
 

12
Sorry to hear this, thanks for trying though! It is most likely a hardware issue. But no worries, I'm sure we'll fix it :) I've sent you an email a minute ago.

13
Hi Greg,

thanks for the update! Looks like it went well except for the downloaded file which only contains 8 bytes and string "test.s19" in it, weird as the screen shows downloading 1024kB... but never mind, we don't really need that.

Please flash this file: gecho-v1_rev244_loopers_and_drones.bin (it's the latest firmware with user data reset to default)
and with flash loader settings as shown in this picture (I think those are default anyway).

This should rule out all software issues.

Cheers,
Mario

14
PS: if the ST website does not allow you to download it without creating an account, you can find it here as well  8)

15
Yes that is correct! Good to know that it's possible to access the chip & memory.

If I remember correctly, it won't allow you to re-flash the same version, I can modify the app later if the needs be.
Would you please try this first: https://gechologic.com/how-to-use-stm32-flash-loader
(the download link is in the beginning and then the guide for the GUI version in the 2nd half of that article)

If this tool works, you will be able to erase all flash (then the Gecho app will allow to update the firmware again).

And if you have time to experiment, please try to use the "Upload from device" option first (as on this picture) to create a backup of the current state. It would be interesting for me to see this file to diagnose the problem, in case that the issue happened because of corrupt firmware or settings.

Pages: [1] 2 3 ... 16