http://forums.leaflabs.com/topic.php?id=74048 A place to share, learn, and grow... en-US Fri, 22 Jan 2016 00:25:48 +0000 http://bbpress.org/?v=1.0.2 q http://forums.leaflabs.com/search.php http://forums.leaflabs.com/topic.php?id=74048#post-104779 Mon, 14 Oct 2013 04:58:33 +0000 jpopadic 104779@http://forums.leaflabs.com/ <p>Hi gbulmer,</p> <p>Thanks for the reply.</p> <p>I'm using a logic analyzer to investigate the behaviour of the pins.</p> <p>I stripped the problem down to the simplest I could and still see the issue. I may have an explanation for what's going wrong and it doesn't appear to be related to the MCU:</p> <p>I'm driving my columns using open-drain outputs and pull-up resistors so MOSFETs sourcing a (~1 volt) higher voltage will switch properly). Stray capacitance (I'm measuring around 400pF) and the relatively high value of the pull-ups (10k) should be able to introduce a delay in the neighborhood of a couple of microseconds.</p> <p>It looks like I either need to account for the delay by shuffling some code around or decrease the value of my pull-ups.</p> <p>Thanks for your time! Sorry it was a red herring. </p> http://forums.leaflabs.com/topic.php?id=74048#post-104760 Fri, 11 Oct 2013 05:45:35 +0000 gbulmer 104760@http://forums.leaflabs.com/ <p>jpopadic - How do you know that the behaviour described is happening? Do you have an oscilloscope or something?</p> <p>Could the effect be some other cause?<br /> For example, the spi.write might not complete until after several digitalWrites, which may cause very weird behaviour, maybe even latching an incomplete pattern into the shift registers.</p> <p>If you change the sequence of NOPs to delay(1), and put a delay(1) in front of<br /> <pre><code>// Latch row data digitalWrite(LE, HIGH); digitalWrite(LE, LOW);</code></pre> <p>does it change the behaviour?<br /> That might indicate a 'race condition', where the spi write is taking too long.</p> <p>I can't see the arithmetic for gColumn, we need to see that to understand how it all works.</p> <p>Have you tried a simpler test? For example, load the shift registers once, and then only change the column drive. Does the problem show up when spi.write isn't being used? </p> http://forums.leaflabs.com/topic.php?id=74048#post-104759 Fri, 11 Oct 2013 04:39:48 +0000 jpopadic 104759@http://forums.leaflabs.com/ <p>Hi all. I have a bit of a puzzle for you all.</p> <p>The hardware background, in brief, is a 16x16 LED matrix with common anode columns sourced by mosfets controlled by individual IO pins. The rows are sunk by constant current output shift registers. The code below is part of a timer interrupt handler.</p> <p>I am seeing strange behaviour from the IO pins controlling the column drivers. In the code below, column n-1 is being driven high a few instructions before column n is driven low. For some unknown reason, the behaviour of the actual pins has the transition of column n-1 delayed significantly - it looks like what I'd expect if the digitalWrite instruction for "lastColumn" were at the end of the block.</p> <p>Got any ideas? I'm stumped.</p> <pre><code>// Blank row digitalWrite(OE, HIGH); // (active low) // Send row data via SPI const int bitplaneOffset = gBitplane * BITPLANE_SIZE; const int columnOffset = gColumn * 2; // Red first spi.write(pFrontBuffer[bitplaneOffset + columnOffset + 1]); spi.write(pFrontBuffer[bitplaneOffset + columnOffset]); // Then green spi.write(pFrontBuffer[HALFPLANE_SIZE + bitplaneOffset + columnOffset + 1]); spi.write(pFrontBuffer[HALFPLANE_SIZE + bitplaneOffset + columnOffset]); // Wait for data to arrive. NOP NOP NOP NOP // Extinguish last column driver int lastColumn = gColumn - 1; if(lastColumn &lt; 0) lastColumn = Constants::FrameWidth-1; digitalWrite(colPins[lastColumn], HIGH); // (active low) &lt;-------- write here... // Latch row data digitalWrite(LE, HIGH); digitalWrite(LE, LOW); // Light the current column digitalWrite(colPins[gColumn], LOW); // (active low) // Re-enable row drivers digitalWrite(OE, LOW); // (active low) &lt;-------- pin changes here</code></pre>