performer (or is it per|former?) sequencer build

From circuitbending to homebrew stompboxes & synths, keep the DIY spirit alive!

Moderators: Kent, luketeaford, Joe.

Post Reply
User avatar
cnicht
Ultra Wiggler
Posts: 805
Joined: Mon Sep 23, 2013 9:23 am

Re: performer (or is it per|former?) sequencer build

Post by cnicht » Sat Aug 08, 2020 8:16 am

The chamfer also seems to indicate orientation

Hales
Common Wiggler
Posts: 196
Joined: Mon Apr 30, 2018 11:22 am
Location: Strasbourg, France

Re: performer (or is it per|former?) sequencer build

Post by Hales » Mon Aug 10, 2020 6:17 am

Do you think it's possible to flash the firmware without solder SW8 and SW19? I don't have them yet, I have to order them…

User avatar
cnicht
Ultra Wiggler
Posts: 805
Joined: Mon Sep 23, 2013 9:23 am

Re: performer (or is it per|former?) sequencer build

Post by cnicht » Mon Aug 10, 2020 6:30 am

Yes.

I've omitted them from my builds

Hales
Common Wiggler
Posts: 196
Joined: Mon Apr 30, 2018 11:22 am
Location: Strasbourg, France

Re: performer (or is it per|former?) sequencer build

Post by Hales » Mon Aug 10, 2020 6:41 am

OK, thanks! I will try to find some information in this post, I don't have much experience, I already flashed Elements before but it was blind with someone guiding me on mac os x using vagrant and terminal…

User avatar
cnicht
Ultra Wiggler
Posts: 805
Joined: Mon Sep 23, 2013 9:23 am

Re: performer (or is it per|former?) sequencer build

Post by cnicht » Mon Aug 10, 2020 7:36 am

Just use the hex files on GitHub and ST-Link Utilty

https://www.st.com/en/development-tools ... nk004.html

Hales
Common Wiggler
Posts: 196
Joined: Mon Apr 30, 2018 11:22 am
Location: Strasbourg, France

Re: performer (or is it per|former?) sequencer build

Post by Hales » Mon Aug 10, 2020 9:04 am

That was my first try with Elements: using ST-Link Utility, but I was unable to use it on mac os X. Someone suggest to me to use VirtualBox with Vagrant and Terminal and it worked well. Are there people here who manage to make ST-Link utility work on Mac OS and flash modules?

Hales
Common Wiggler
Posts: 196
Joined: Mon Apr 30, 2018 11:22 am
Location: Strasbourg, France

Re: performer (or is it per|former?) sequencer build

Post by Hales » Tue Aug 11, 2020 4:01 am

Actually, I try to follow the instructions on this page:
https://github.com/westlicht/performer? ... BBwe8k46vY

"Setup on macOS and Linux"
I'm stuck after entering this command:
make setup_stm32

On terminal I have this answer:
(mkdir -p /Users/xx/performer/./build/stm32/debug && cd /Users/xx/performer/./build/stm32/debug && cmake -DCMAKE_TOOLCHAIN_FILE=./cmake/arm.cmake -DCMAKE_BUILD_TYPE=Debug -DPLATFORM=stm32 ../../..)
/bin/sh: cmake: command not found
make: *** [setup_stm32] Error 127

Hales
Common Wiggler
Posts: 196
Joined: Mon Apr 30, 2018 11:22 am
Location: Strasbourg, France

Re: performer (or is it per|former?) sequencer build

Post by Hales » Sun Aug 16, 2020 1:16 pm

Hi, I currently have the performer powered on with st-link connected. I'm on mac os X under vagrant, seems that the chip is recognized, ST-Link led is green. As I have precompiled hex files, I'm wondering which code to type, can someone help me?

Hales
Common Wiggler
Posts: 196
Joined: Mon Apr 30, 2018 11:22 am
Location: Strasbourg, France

Re: performer (or is it per|former?) sequencer build

Post by Hales » Sun Aug 16, 2020 2:15 pm

I'm stuck because I only find examples with "makefile", but as I understand makefile is used to compile and make hex files. What is the command line to 'simply' flash modules with compiled hex files? Please?

User avatar
forestcaver
Ultra Wiggler
Posts: 877
Joined: Tue Mar 14, 2017 4:41 pm
Location: UK
Contact:

Re: performer (or is it per|former?) sequencer build

Post by forestcaver » Sun Aug 16, 2020 2:30 pm

Try having a look at the readme - all the instructions are there.
I used openocd directly though (it also has a manual)

Hales
Common Wiggler
Posts: 196
Joined: Mon Apr 30, 2018 11:22 am
Location: Strasbourg, France

Re: performer (or is it per|former?) sequencer build

Post by Hales » Sun Aug 16, 2020 2:41 pm

Thanks forestcaver, maybe I'm missing something, I only see explanations about how to do development on the firmware not the flashing process by using hex files.

Hales
Common Wiggler
Posts: 196
Joined: Mon Apr 30, 2018 11:22 am
Location: Strasbourg, France

Re: performer (or is it per|former?) sequencer build

Post by Hales » Sun Aug 16, 2020 3:53 pm

I took everything from 0 and I followed the instructions on this page: https://github.com/westlicht/performer/ ... /README.md

and I find myself stuck again in the previous step:
"xx:performer xx$ make setup_stm32
(mkdir -p /Users/xx/performer/./build/stm32/debug && cd /Users/xx/performer/./build/stm32/debug && cmake -DCMAKE_TOOLCHAIN_FILE=./cmake/arm.cmake -DCMAKE_BUILD_TYPE=Debug -DPLATFORM=stm32 ../../..)
/bin/sh: cmake: command not found
make: *** [setup_stm32] Error 127

Hales
Common Wiggler
Posts: 196
Joined: Mon Apr 30, 2018 11:22 am
Location: Strasbourg, France

Re: performer (or is it per|former?) sequencer build

Post by Hales » Sun Aug 16, 2020 4:03 pm

Is there something to do with CMake? I downloaded and installed the software but don't know if I need it…

User avatar
gbiz
Super Deluxe Wiggler
Posts: 1076
Joined: Tue May 07, 2013 11:20 am
Location: Sussex, UK

Re: performer (or is it per|former?) sequencer build

Post by gbiz » Sun Aug 16, 2020 4:32 pm

Hales wrote:
Sun Aug 16, 2020 3:53 pm
I took everything from 0 and I followed the instructions on this page: https://github.com/westlicht/performer/ ... /README.md

and I find myself stuck again in the previous step:
"xx:performer xx$ make setup_stm32
(mkdir -p /Users/xx/performer/./build/stm32/debug && cd /Users/xx/performer/./build/stm32/debug && cmake -DCMAKE_TOOLCHAIN_FILE=./cmake/arm.cmake -DCMAKE_BUILD_TYPE=Debug -DPLATFORM=stm32 ../../..)
/bin/sh: cmake: command not found
make: *** [setup_stm32] Error 127
That error message is telling you what's wrong - it can't find the cmake command, most likely as you don't have it installed.

If you're running this in the usual Vagrant image then you're not following the instructions in the README. Specifically the bit that tells you to install cmake ...
"sudo apt-get install libtool autoconf cmake libusb-1.0.0-dev libftdi-dev pkg-config"

That install command won't work on OSX as it's Debian Linux specific (as the readme says). On OSX you'll need to install them by hand, or via one of the open source repos like macports.

That README you linked says that the instructions to build from source are "If you want to do development on the firmware". I guess you probably don't, so as others have said, you're going to be better off installing the pre-compiled hex files. There's plenty of posts further back in this thread on how to do that.

Hales
Common Wiggler
Posts: 196
Joined: Mon Apr 30, 2018 11:22 am
Location: Strasbourg, France

Re: performer (or is it per|former?) sequencer build

Post by Hales » Sun Aug 16, 2020 4:48 pm

gbiz wrote:
Sun Aug 16, 2020 4:32 pm
Hales wrote:
Sun Aug 16, 2020 3:53 pm

That README you linked says that the instructions to build from source are "If you want to do development on the firmware". I guess you probably don't, so as others have said, you're going to be better off installing the pre-compiled hex files. There's plenty of posts further back in this thread on how to do that.
Yes you're right, I just needed to know what to do with the hex files since the chip was recognized. It might be very stupid but I can't find the plenty of posts you are talking about on how to installing pre compiled hex files, can you send me a link to them?

Hales
Common Wiggler
Posts: 196
Joined: Mon Apr 30, 2018 11:22 am
Location: Strasbourg, France

Re: performer (or is it per|former?) sequencer build

Post by Hales » Sun Aug 16, 2020 4:59 pm

… but I made a vagrant up and vagrant ssh. After installation of vagrant I'm on this directory:
(performer) vagrant@ubuntu-xenial:/vagrant/build/stm32/release$

I try: "st-info --probe" (try to reanimate STLink, since I unplug the USB)
answer: st-info: command not found

I try: "make -j flash_bootloader"
answer:
GENHDR include/libopencm3/efm32/g/irq.json
GENHDR include/libopencm3/efm32/gg/irq.json
GENHDR include/libopencm3/efm32/lg/irq.json
GENHDR include/libopencm3/efm32/tg/irq.json
GENHDR include/libopencm3/lm3s/irq.json
GENHDR include/libopencm3/lpc13xx/irq.json
GENHDR include/libopencm3/lpc17xx/irq.json
GENHDR include/libopencm3/lpc43xx/m0/irq.json
GENHDR include/libopencm3/lpc43xx/m4/irq.json
GENHDR include/libopencm3/sam/3a/irq.json
GENHDR include/libopencm3/sam/3n/irq.json
GENHDR include/libopencm3/sam/3s/irq.json
GENHDR include/libopencm3/sam/3u/irq.json
GENHDR include/libopencm3/sam/3x/irq.json
GENHDR include/libopencm3/sam/d/irq.json
GENHDR include/libopencm3/stm32/f0/irq.json
GENHDR include/libopencm3/stm32/f1/irq.json
GENHDR include/libopencm3/stm32/f2/irq.json
GENHDR include/libopencm3/stm32/f3/irq.json
GENHDR include/libopencm3/stm32/f4/irq.json
GENHDR include/libopencm3/stm32/f7/irq.json
GENHDR include/libopencm3/stm32/l0/irq.json
GENHDR include/libopencm3/stm32/l1/irq.json
GENHDR include/libopencm3/stm32/l4/irq.json
GENHDR include/libopencm3/vf6xx/irq.json
BUILD lib/stm32/f4
[ 0%] Built target libopencm3
[100%] Built target bootloader
Scanning dependencies of target flash_bootloader
Open On-Chip Debugger 0.10.0
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
Info : auto-selecting first available session transport "jtag". To override use 'transport select <transport>'.
adapter speed: 2000 kHz
adapter_nsrst_delay: 100
jtag_ntrst_delay: 100
none separate
cortex_m reset_config sysresetreq
Error: no device found
Error: unable to open ftdi device with vid 15ba, pid 002b, description 'Olimex OpenOCD JTAG ARM-USB-OCD-H', serial '*' at bus location '*'
** OpenOCD init failed **
shutdown command invoked

src/apps/bootloader/CMakeFiles/flash_bootloader.dir/build.make:57: recipe for target 'src/apps/bootloader/CMakeFiles/flash_bootloader' failed
make[3]: *** [src/apps/bootloader/CMakeFiles/flash_bootloader] Error 1
CMakeFiles/Makefile2:296: recipe for target 'src/apps/bootloader/CMakeFiles/flash_bootloader.dir/all' failed
make[2]: *** [src/apps/bootloader/CMakeFiles/flash_bootloader.dir/all] Error 2
CMakeFiles/Makefile2:303: recipe for target 'src/apps/bootloader/CMakeFiles/flash_bootloader.dir/rule' failed
make[1]: *** [src/apps/bootloader/CMakeFiles/flash_bootloader.dir/rule] Error 2
Makefile:181: recipe for target 'flash_bootloader' failed
make: *** [flash_bootloader] Error 2
(performer) vagrant@ubuntu-xenial:/vagrant/build/stm32/release$

so, i understand that I need to re-animate STLink, do you know how to do that?

Hales
Common Wiggler
Posts: 196
Joined: Mon Apr 30, 2018 11:22 am
Location: Strasbourg, France

Re: performer (or is it per|former?) sequencer build

Post by Hales » Sun Aug 16, 2020 5:31 pm

I also need to change the default "ARM-USB-OCD-H JTAG " in CMakeLists.txt. I have an ARM-JTAG-20-10 and don't find it at tools/openocd/share/openocd/scripts/interface. Is it possible to make it work with an ARM-JTAG-20-10 or do I need another adapter?

Hales
Common Wiggler
Posts: 196
Joined: Mon Apr 30, 2018 11:22 am
Location: Strasbourg, France

Re: performer (or is it per|former?) sequencer build

Post by Hales » Mon Aug 17, 2020 6:27 am

I decided to borrow a windows 10 pc from a friend and use St-Link Utility, I first flashed bootloader.hex, then sequencer.hex

Here is the report :

13:07:25 : ST-LINK SN : 34FF6D065250343828160943
13:07:25 : V2J29S7
13:07:25 : Connected via SWD.
13:07:25 : SWD Frequency = 4,0 MHz.
13:07:25 : Connection mode : Normal.
13:07:25 : Debug in Low Power mode enabled.
13:07:25 : Device ID:0x413
13:07:25 : Device flash Size : 1MBytes
13:07:25 : Device family :STM32F405xx/F407xx/F415xx/F417xx
13:11:01 : [bootloader.hex] opened successfully.
13:11:01 : [bootloader.hex] checksum : 0x002398A0
13:15:31 : Memory programmed in 1s and 15ms.
13:15:31 : Verification...OK
13:15:31 : Programmed memory Checksum: 0x002398A0
13:15:57 : [sequencer.hex] opened successfully.
13:15:57 : [sequencer.hex] checksum : 0x02162180
13:16:20 : Memory programmed in 9s and 157ms.
13:16:20 : Verification...OK
13:16:20 : Programmed memory Checksum: 0x02162180

Is it ok?

dlavila
Learning to Wiggle
Posts: 25
Joined: Thu Jul 02, 2020 4:55 pm
Location: Amsterdam
Contact:

Re: performer (or is it per|former?) sequencer build

Post by dlavila » Mon Aug 17, 2020 8:05 am

yes, that seems ok, if you are flashing for the first time, try the tester hex first (instead of sequencer.hex), this way you can test all the I/O first

User avatar
cnicht
Ultra Wiggler
Posts: 805
Joined: Mon Sep 23, 2013 9:23 am

Re: performer (or is it per|former?) sequencer build

Post by cnicht » Mon Aug 17, 2020 8:10 am

dlavila wrote:
Mon Aug 17, 2020 8:05 am
yes, that seems ok, if you are flashing for the first time, try the tester hex first (instead of sequencer.hex), this way you can test all the I/O first
Agreed!

Hales
Common Wiggler
Posts: 196
Joined: Mon Apr 30, 2018 11:22 am
Location: Strasbourg, France

Re: performer (or is it per|former?) sequencer build

Post by Hales » Mon Aug 17, 2020 8:47 am

yes, that's what I wanted to ask about the tester hex. Actually, I flashed bootloader and sequencer hex. My build is not finished, I post a photo that shows the current status. So, several questions: do I need to try the tester hex on the current status of the build? Or? Erase the chip to run the tester? … finish the build, erase the chip and run tester hex?
IMG_1526.JPG

dlavila
Learning to Wiggle
Posts: 25
Joined: Thu Jul 02, 2020 4:55 pm
Location: Amsterdam
Contact:

Re: performer (or is it per|former?) sequencer build

Post by dlavila » Mon Aug 17, 2020 9:35 am

after flashing you know the connection and power to the MCU is correct, at this point you can check that all the reference and supply voltages are correct, but not much more.

The tester is to check if the inputs and outputs are working ok, in this case you don't have buttons, jacks or encoder in the board, so you can just finish the build and the run the tester.

Hales
Common Wiggler
Posts: 196
Joined: Mon Apr 30, 2018 11:22 am
Location: Strasbourg, France

Re: performer (or is it per|former?) sequencer build

Post by Hales » Mon Aug 17, 2020 9:39 am

thanks, that's what I ended up deducing. So as soon as I'm done building everything I have first to erase the chip? or I can run tester hex with bootloader and sequencer hex flashed?

dlavila
Learning to Wiggle
Posts: 25
Joined: Thu Jul 02, 2020 4:55 pm
Location: Amsterdam
Contact:

Re: performer (or is it per|former?) sequencer build

Post by dlavila » Mon Aug 17, 2020 9:43 am

If you flash the tester it will overwrite the sequencer hex, the bootloader is a requirement for both, but you already flashed that one

Hales
Common Wiggler
Posts: 196
Joined: Mon Apr 30, 2018 11:22 am
Location: Strasbourg, France

Re: performer (or is it per|former?) sequencer build

Post by Hales » Mon Aug 17, 2020 10:15 am

OK, thanks I will continue the build. Voltage test gives +11,5V // -11,5V. I wanted to do the measurement tests for the +5V, +3V3, +3.3VA and AREF_-10V but I don't know how to do that… the online board viewer give the same components to test. Anyone can explain how to make these tests?

Post Reply

Return to “Music Tech DIY”