Patch.Init() - how to check if the firmware/hardware is actually working?

Hello.
Recently I’ve got my patch.Init() unit.
Installed the toolchain according to wiki, and tried to flash some firmware.
After flashing the seed/Blink example the LED on back of module flashes okay. Then I’ve flashed patch_sm/PassthruExample and installed the module into my rack, plugged the power and fed an audio signal to IN_L. But got no sound from neither of of OUT jacks. The same result for seed/bypass example. The LED on the back of patch.Init() is glowing, LED on front side remains dark, no reaction to front-side encoders at all.

Do I have to reset or in any other way exit the bootloader mode to make patch.Init() work?
Maybe my choice of examples to flash was wrong?
May it be a hardware malfuction and how can I check this?

Thanks in advance!

PS some additional data, in case if it helps:

PassthruExample installation log
$ make program-dfu 
dfu-util -a 0 -s 0x08000000:leave -D build/PassthruExample.bin -d ,0483:df11
dfu-util 0.9

Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2016 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to http://sourceforge.net/p/dfu-util/tickets/

dfu-util: Invalid DFU suffix signature
dfu-util: A valid DFU suffix will be required in a future dfu-util release!!!
Opening DFU capable USB device...
ID 0483:df11
Run-time device DFU version 011a
Claiming USB DFU Interface...
Setting Alternate Setting #0 ...
Determining device status: state = dfuIDLE, status = 0
dfuIDLE, continuing
DFU mode device DFU version 011a
Device returned transfer size 1024
DfuSe interface name: "Internal Flash   "
Downloading to address = 0x08000000, size = 59536
Download	[=========================] 100%        59536 bytes
Download done.
File downloaded successfully
dfu-util: Error during download get_status
make: *** [../../libDaisy//core/Makefile:330: program-dfu] Error 74
$
Toolchain versions
$ make --version
GNU Make 4.2.1
Built for x86_64-pc-linux-gnu
Copyright (C) 1988-2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
 
$ arm-none-eabi-gcc --version
arm-none-eabi-gcc (GNU Arm Embedded Toolchain 10.3-2021.10) 10.3.1 20210824 (release)
Copyright (C) 2020 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

$ dfu-util --version
dfu-util 0.9

Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2016 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to http://sourceforge.net/p/dfu-util/tickets/

$ openocd --version
Open On-Chip Debugger 0.10.0
Licensed under GNU GPL v2
For bug reports, read
	http://openocd.org/doc/doxygen/bugs.html

Managed to make the web programmer work under Linux.
The examples uploaded from website work perfectly. The problem may be in the toolchain (used GCC 10.3 and the old toolchain from ARM website). Currently i’m investigating this.

1 Like

Sorry, I give up. It looks impossible to get a working toolchain on Ubuntu atm. Tried several variants, including building toolchain from sources.

Reverted to static toolchain on Windows.

I wonder what you mean by

The whole GCC toolchain should be at 10.3.10 (10.3.07 is okay too), but maybe I’m just misunderstanding. As long as you download this precompiled version of the toolchain and follow the instructions in the guide, you should be good to go for the GCC side of things. I daily drive Ubuntu (20.04) and haven’t had any issues with the toolchain so far.

It might also be helpful to post a log of the compiler’s output if anything looks unusual. Significantly older or newer versions may have compatibility issues with the current code base.