Phoreo Board revisions

Hi,
I just got a Phoreo board (and panel) from Thonk.
It’s the v5 with the part numbers in the 100’s, matching the schematic.

I can only find BOM for v6, (from Befaco shop)
Thonk have broken links for docs.

Help…

hey Andy,
sorry about this -
let’s see if @befaco can help us out.

This should be it!

Phoreo_Assembly_Manual.pdf (152.6 KB)

Yup. Thankyou!
Thonk site is now linking to v6 docs…but they sent me link to here via email.

Anyway, Phoreo has been making beats for about an hour now, with it’s pal Logoi :slight_smile:
(I managed to work from the schematic)

1 Like

@andybutler are you going for the full algorithmic beat machine setup now?.. :slight_smile:

Polyrhythm beats with algorithmic disturbances.
I’d get the Klasmata for voltage controlled Euclidean if I didn’t already have the Tesseract Tukra (and Euclidean Circles).

Question though, I suspect my modules are running slow. max delay time from the Logoi is 5s, and it’s quoted at 1000mS. (and it’s really difficult to set the swing, knb almost fully anti-clockwise) Also response to audio rate is no-where near the quoted 30kHz.
That 2nd point for both modules.
I have a suspicion that the fuses aren’t set correctly in the atmegas, …well if not “bad soldering”.

Any ideas/comments.
@mars @Befaco

That’s weird!

Yes that would potentially lead to all sorts of weirdness, with the MCU running at 8 MHz instead of 16. Don’t understand quite how that could happen though. Did you build them both from full kits?

I bought panel/pcb/chip packages from Thonk. They could be old versions, I got v5 board for the Phoreo.
Panels are really nice (and black) , but don’t look like they came from Befaco, made from pcb not Befaco’s enamelled metal.
Basically both modules are working, but not up to 30KHz. The audio rate response is uneven.
The only absolute time I can measure is the delay on the Logoi, which is 4-5 seconds. There’s not much control over swing as the useful settings are within a very small range, almost fully anti-clockwise.

I’m going to slip the chips into my Muxlicer to see if I can read the fuses.

They should be, for the atmega328p:
EFUSE = FD
HFUSE = DA
LFUSE = FF

I’ll investigate on our end if something could have gone wrong with the flashing.

thankyou,

Well I tried. I put the Logoi atmega chip into the Muxlicer and queried it with avrdude.
I’m using a usbasp.

afraid I didn’t find out anything though

AVRdude says Chip not responding.

When I tell avrdude to ignore that error (-F) I get the following.

avrdude: auto set sck period (because given equals null)
avrdude: error: program enable: target doesn’t answer. 1
avrdude: initialization failed, rc=-1
avrdude: AVR device initialized and ready to accept instructions
avrdude: Device signature = 0x000000 (retrying)
avrdude: Device signature = 0x000000 (retrying)
avrdude: Device signature = 0x000000
avrdude: Yikes! Invalid device signature.
avrdude: Expected signature for ATmega328P is 1E 95 0F

I checked, Logoi and Muxlicer both reassembled and working as before.

I’ll look into loading up the Logoi firmware on another atmega chip.

Oh, hang on. Last time I had an atmega do that it needed the fuses setting and that fixed it…
So starting to think something’s wrong there.

So I got out a fresh new atmega.
Set the fuses as per your instructions.
Burned the bootloader with the Arduino IDE

then burned the firmware

C:\Users\Andy>“C:\Program Files (x86)\Arduino\hardware\tools\avr/bin/avrdude” -C
“C:\Program Files (x86)\Arduino\hardware\tools\avr/etc/avrdude.conf” -v -patmega
328p -cusbasp -Pusb -Uflash:w:“C:\Users\Andy\Documents\Arduino\ClockDelay-master
\build\ClockDelay.hex”:i

avrdude: Version 6.3-20190619
Copyright (c) 2000-2005 Brian Dean, http://www.bdmicro.com/
Copyright (c) 2007-2014 Joerg Wunsch

     System wide configuration file is "C:\Program Files (x86)\Arduino\hardw

are\tools\avr/etc/avrdude.conf"

     Using Port                    : usb
     Using Programmer              : usbasp
     AVR Part                      : ATmega328P
     Chip Erase delay              : 9000 us
     PAGEL                         : PD7
     BS2                           : PC2
     RESET disposition             : dedicated
     RETRY pulse                   : SCK
     serial program mode           : yes
     parallel program mode         : yes
     Timeout                       : 200
     StabDelay                     : 100
     CmdexeDelay                   : 25
     SyncLoops                     : 32
     ByteDelay                     : 0
     PollIndex                     : 3
     PollValue                     : 0x53
     Memory Detail                 :

                              Block Poll               Page
  Polled
       Memory Type Mode Delay Size  Indx Paged  Size   Size #Pages MinW  Max

W ReadBack
----------- ---- ----- ----- ---- ------ ------ ---- ------ ----- —


       eeprom        65    20     4    0 no       1024    4      0  3600  36

00 0xff 0xff
flash 65 6 128 0 yes 32768 128 256 4500 45
00 0xff 0xff
lfuse 0 0 0 0 no 1 0 0 4500 45
00 0x00 0x00
hfuse 0 0 0 0 no 1 0 0 4500 45
00 0x00 0x00
efuse 0 0 0 0 no 1 0 0 4500 45
00 0x00 0x00
lock 0 0 0 0 no 1 0 0 4500 45
00 0x00 0x00
calibration 0 0 0 0 no 1 0 0 0
0 0x00 0x00
signature 0 0 0 0 no 3 0 0 0
0 0x00 0x00

     Programmer Type : usbasp
     Description     : USBasp, http://www.fischl.de/usbasp/

avrdude: auto set sck period (because given equals null)
avrdude: AVR device initialized and ready to accept instructions

Reading | ################################################## | 100% 0.02s

avrdude: Device signature = 0x1e950f (probably m328p)
avrdude: safemode: lfuse reads as FF
avrdude: safemode: hfuse reads as DA
avrdude: safemode: efuse reads as FD
avrdude: NOTE: “flash” memory has been specified, an erase cycle will be perform
ed
To disable this feature, specify the -D option.
avrdude: erasing chip
avrdude: auto set sck period (because given equals null)
avrdude: reading input file “C:\Users\Andy\Documents\Arduino\ClockDelay-master\b
uild\ClockDelay.hex”
avrdude: writing flash (3440 bytes):

Writing | ################################################## | 100% 2.39s

avrdude: 3440 bytes of flash written
avrdude: verifying flash memory against C:\Users\Andy\Documents\Arduino\ClockDel
ay-master\build\ClockDelay.hex:
avrdude: load data flash data from input file C:\Users\Andy\Documents\Arduino\Cl
ockDelay-master\build\ClockDelay.hex:
avrdude: input file C:\Users\Andy\Documents\Arduino\ClockDelay-master\build\Cloc
kDelay.hex contains 3440 bytes
avrdude: reading on-chip flash data:

Reading | ################################################## | 100% 1.52s

avrdude: verifying …
avrdude: 3440 bytes of flash verified

avrdude: safemode: lfuse reads as FF
avrdude: safemode: hfuse reads as DA
avrdude: safemode: efuse reads as FD
avrdude: safemode: Fuses OK (E:FD, H:DA, L:FF)

avrdude done. Thank you.

++++++++++++++++++++++++++++++++++++
Put the new atmega in the Logoi, and suddenly it runs up to speed.
This is fun!

Next step is to see if the supplied atmega can be recovered.

Success.
So it seems the atmega as supplied (via Thonk) didn’t have fuses set.

Now the Logoi working well in audio range with the original chip (before it was glitchy) and the max delay is now more like 1000mS as it should be,
much better range for setting swing.

I also had a look at the atmega in the Phoreo. Exact same situation, so set the fuses and reloaded firmware. No big difference really. Audio performance is “better”, but perhaps if you want a really rough digital sound sometimes you’d rather leave the atmega running slow.

Next task…work out what that middle output on the Logoi is actually meant to be doing. :wink:

Hey Andy, thank you so much for persisting with this. Having your feedback and help with troubleshooting is fantastic.

We’ve taken stock of the situation on our end, and turns out that we’ve messed up badly! :frowning:

At some point in time the flashing process changed, for reasons still unknown. Since then the microcontrollers have shipped out with default fuse settings.
It means the microcontroller runs at half speed, which can cause timing problems such as what Andy describes on the Logoi.

We don’t know exactly how many kits have shipped out with this problem. If you have bought any Rebel Technology kit with black front panels then please let me know (DM) if you think yours might be faulty or have a problem.