Spin Semiconductor

Great thanks for your reply. So there's no danger of noise affecting other aspects of the chip if the pot pins are left floating?

I know this probably sounds like a daft question but if the program select and pot inputs are not switched or controlled in any way (ie an application that only uses one program and has not controls), can these pins be tied directly to ground or is there any reason to include a resistor? I've seen s...

Just double checking, is is ok to leave this output floating if the LED is not in use?

Ah that's the badger. Muchas gracias. I didn't realise that you could use the "Assemble to EEPROM" button to build a single program and get those details in the output window (and that doing that first then makes the "View Machine Code Listing" button work). Am I right in thinkin...

That was very helpful thanks. I've knocked out an implementation based on your advice but I'm still getting the pops on the transitions from both wet-to-dry and dry-to-wet as before. Can you spot anything glaring in my code that I might have overlooked? FL00 EQU %00000000_00000000_00000000 ;possible...

Using the register certainly sounds safer and simpler. Let's say I decrement a counter for 2048 samples (62.5ms xfade on a 32768Hz clock, deliberately long), would this be a reasonable approach? FADE_TO_DRY: rdax XFADE_CTR,$0008 ;load XFADE_CTR and divide by 2048 (S1.14) to obtain xfade coefficient,...

Ah that makes sense, thanks. I was going about it completely the wrong way around, testing each flag individually and working from the current and last pedal states rather than using each possible scenario as an individual case. I'll rewrite it tomorrow and give it another shot. In terms of setting ...

I'm not sure I quite get it. I still need at least three flags in order to detect the six possible states (including the transitions) and thus perform the six possible behaviours: 1. no fade, output dry 2. no fade, output wet 3. fading to dry 4. fading to wet 5. starting a fade to dry, output wet 6....

Ok so I'm running out of instructions the way I was trying to do it, which leads me to believe there must be an easier way... The key elements I identified to query here were as follows: current pedal state previous pedal state crossfade state (is there already a previous crossfade happening?) ramp ...

Ahhh I see cheers. So just to clarify, I can assign the 24 bit value using the EQU statement, and that will be fine for AND/OR/XOR, but for sof etc the compiler will simply bin the last 13 bits so I need to make sure my flag bits occur within the first 11 bits? The sof was really just a way that I m...

Thanks for your reply Sweetalk. I understand what S.10 etc mean but the manual doesn't explain how to convert a value from one of those to the 24-bit mask that is required. The manual actually explains that a 24-bit mask is reqd for the logic operations, so I presumably need to feed those 24-bit, no...

Hmmm. Excuse my ignorance but I'm quite confused by the formats allowed here. For logic operations, the manual specifies a 24 bit mask (I'm aware that I missed a zero in my last post...), so where does the S.10 format come from? Is it something inherent to the EQU statement? This is my first foray i...

Ah thanks. Is there any reason why we can't just use something like this for values that are going to be used as a bit mask?

alpha EQU %00000000_00000000_0000111

Hey Gary,
It might be worth checking out the "Basics of the LFOs in the FV-1" (AN-0001) document if you haven't already. It examines some similar functionality in depth.
I'm only starting out with this but it certainly helped me to get my head around it
Ant

Great thanks Frank. Slightly off topic, is there a way to load an arbitrary number into the acc without reading from a register? I see with sof that the offset constant "D is not intended to become used for integer arithmetic". I'm trying to save on instructions at points in my code where ...