Forty Two

[Ken Forgettable]

dmitri,

Your copyright notice is gone - did you remove the virus correctly?

[dmitri]

Is it THE ultimate question?

[Ken Forgettable]

We can all see you know the answer to that by now...

But seriously - in the mean time I think you'll be needing this:

static volatile

[dmitri]

I have it.

[Ken Forgettable]

On a virgin 16MHz synthex v2.8 kit using 20081222 firmware with pullups fitted the first thing it does is make the LED glow.

In midiox there's constant footcontroller activity, and I have nothing attached. No piezo and no hihat pot.

--cut --

This seems only to occur after a firmware update directly after the megadrum rebooted itself. It keeps on scrolling forever..

Take a look at the screenshot.

midiox_pin4gnd.jpg

We know the statemachine should only be sending CCs when a change has occured therefore we could deduce that some signal activity is occuring within the 2ms period but observing Data2 we see the signal always reads HI with no transitions - how can this be?.

I see some noise (those 4 multiplexers are all being switched at the same time) but when I load the defaults - the activity stops.

If:-
1. The state machine needs to compare consecutive readings on this channel in order to recongnise a signal change over time - it must use a store for the previous value.

and
2. I know a compiler will warn against using uninitialised variables because it's a common problem but I see your code goes like shit off a shovel so assume the state machine is hand optimised assembler.


The question therefore is: Can the store contain a uninitialised (random) value > &7F?

[dmitri]

You most certainly right.
Connect a HH pedal and set Low and High for the pedal accordingly and it won't bother you any more.

[Ken Forgettable]

I will follow your advice and appreciate your help - thanks.

PS.
Is viewtopic.php?f=3&t=532&start=0 the same question

[dmitri]

I will follow your advice and appreciate your help - thanks.

PS.
Is viewtopic.php?f=3&t=532&start=0 the same question

No, it's different.

[Ken Forgettable]

With the new erase_firmware.syx idea is there any point in using a button to initiate a FW update?

Eg. (I assume you don't need a page write!)
+ New build bootloader
....set fwUpdateSemaphore

+ Megadrum firmware gets the erase_firmware.syx
....set fwUpdateSemaphore
....reboot

+ On powerup bootloader checks fwUpdateSemaphore

Perhaps the fwUpdateSemaphore could be a pointer to the crystal speed...

[Ken Forgettable]

...the smart bootloader works out it's own F_CPU, it knows roughly which syx to expect...

The fwUpdateSemaphore then becomes
reset vector == &FFFF