http://forums.leaflabs.com/forum.php?id=5 A place to share, learn, and grow... en-US Fri, 22 Jan 2016 00:01:20 +0000 http://bbpress.org/?v=1.0.2 q http://forums.leaflabs.com/search.php http://forums.leaflabs.com/topic.php?id=73&page=4#post-105765 Sun, 02 Aug 2015 09:23:06 +0000 JPB 105765@http://forums.leaflabs.com/ <p>Hi daduck748!<br /> Your solution is fine!<br /> Work on win 8.1/64 :-) !!!<br /> "after the compiler failed to find a "Serial Device", it searches for DFU devices. This is when I hit the Reset button and my Blink program uploaded successfully. When you hit the Reset button at this point, you'll see "Maple" disappears and "Maple 003" will appear in the Device Manager."<br /> Maple Mini (clone)<br /> ebay:"STM32 ARM Cortex-M3 Leaflabs Leaf Maple Mini Module for Arduino"<br /> AU $5.52 </p> http://forums.leaflabs.com/topic.php?id=73&page=4#post-105670 Tue, 03 Mar 2015 14:52:45 +0000 JoshSanders 105670@http://forums.leaflabs.com/ <p>RogerClark and Tim Schuerewegen, you are both officialy the bomb! This was such a pain before... </p> http://forums.leaflabs.com/topic.php?id=73&page=4#post-105636 Sun, 25 Jan 2015 17:01:22 +0000 rogerclark 105636@http://forums.leaflabs.com/ <p>There is a now a good solution to the Windows driver issue.</p> <p>See <a href="https://github.com/rogerclarkmelbourne/Arduino_STM32/tree/master/drivers/win" rel="nofollow">https://github.com/rogerclarkmelbourne/Arduino_STM32/tree/master/drivers/win</a></p> <p>Tim Schuerewegen, wrote a modified version of libwdi which installs does all the clever stuff to install custom cert's etc for the Leadlabs VID/PID </p> http://forums.leaflabs.com/topic.php?id=73&page=4#post-105633 Fri, 23 Jan 2015 05:00:28 +0000 fxstrike 105633@http://forums.leaflabs.com/ <p>f343,</p> <p>please do send your WinUSB.sys driver </p> http://forums.leaflabs.com/topic.php?id=73&page=4#post-105582 Thu, 04 Dec 2014 08:18:42 +0000 f3434 105582@http://forums.leaflabs.com/ <p>Use WinUSB.sys driver. If you want I can send example code. </p> http://forums.leaflabs.com/topic.php?id=74195#post-105292 Mon, 17 Mar 2014 22:53:49 +0000 gruvin 105292@http://forums.leaflabs.com/ <p>Can't help you, sorry. But I just looked over the site myself as a sanity check and I don't see any way to do it, either. </p> <p>There is a <a href="http://leaflabs.com/contact/">contact link</a> on the home page. Try sending an email, perhaps? </p> http://forums.leaflabs.com/topic.php?id=74199#post-105072 Thu, 12 Dec 2013 06:56:04 +0000 gbulmer 105072@http://forums.leaflabs.com/ <p>jappiemike - Thank you for posting the solution. Hopefully that will help others. I apologise for missing the pinModes; I can get a bit 'snow blind' some days.</p> <p>Maybe the documentation could call out more strongly and clearly that the pins are set by spi.begin, and there is no pinMode needed:<br /> <a href="http://leaflabs.com/docs/lang/api/hardwarespi.html#turning-the-spi-port-on" rel="nofollow">http://leaflabs.com/docs/lang/api/hardwarespi.html#turning-the-spi-port-on</a></p> <p>Maybe using spi.transfer() might be worth trying. It would remove the need for wait(), and should be correct at any speed. Just discard the returned value.</p> <p>(Full disclosure: I am not a member of LeafLabs staff.) </p> http://forums.leaflabs.com/topic.php?id=74199#post-105071 Wed, 11 Dec 2013 22:52:41 +0000 jappiemike 105071@http://forums.leaflabs.com/ <p>Ok, a couple of things. Firstly, thanks for the replies and assistance.<br /> I took out the pinMode code in my program which set up the SPI pins(MOSI and CLK) but not the SS one. I then used the wait() function to allow the transfer to complete and it's now working perfectly at any speed. I'm surprised that my pinMode (which occurred after initialising the SPI) caused an error as I would've assumed it was also setting the pins up as OUTPUTS, I also noticed when my faulty code tried to run that pin 13 didn't glow but it does now and the brightness changes with the speed of the SPI transfer.<br /> Now all I have to do is finish 2 8x10 rgb matrixes for Christmas!</p> <p>Cheers<br /> Mike </p> http://forums.leaflabs.com/topic.php?id=74199#post-105070 Wed, 11 Dec 2013 05:44:33 +0000 ventosus 105070@http://forums.leaflabs.com/ <p>@jappiemike</p> <p>I'm running 3 daisy-chained TLC5917s fine here with a Maple Mini.</p> <p>From the manual: <em>Serial data is transferred to the respective latch when LE(ED1) is high. The data is latched when LE(ED1) goes low.<br /> Also, a control signal input for an Error Detection Mode and Current Adjust Mode (see Timing Diagram). LE(ED1) has<br /> an internal pulldown.</em></p> <p>Pulse duration for LE has to be 20ns minimum.</p> <p>There may be an additional problem in your usage of spi.write.</p> <p>spi.write calls the libmaple routine spi_tx which is a non-blocking function, e.g. it returns although the SPI Tx may still be busy (transmitting). If you then immediately pull high SS to trigger the latch, transmission may get corrupted.</p> <p>So, you may either have to check whether SPI Tx is still busy before pulling high SS, or use spi.transfer instead which is blocking and only returns when a byte from SPI Rx was received (and transmission therefore was successful).</p> <p>Changing spi.write to spi.transfer might already do the trick.</p> <p>I use the underlying libmaple routines directly.</p> <p><code><br /> digitalWrite(BOARD_SPI1_NSS_PIN, LOW)<br /> spi_tx(SPI1, rgb, 3);<br /> while(spi_is_busy(SPI1))<br /> ; // wait until not busy<br /> digitalWrite(BOARD_SPI1_NSS_PIN, HIGH)<br /> </code></p> <p>Or the problem may lie somewhere else... </p> http://forums.leaflabs.com/topic.php?id=74199#post-105069 Tue, 10 Dec 2013 22:35:09 +0000 gbulmer 105069@http://forums.leaflabs.com/ <p>jappiemike - <em>Is setting SS to low purely to let the chip you are writing to know to expect some data or is it tied to the SPI data transmission from MOSI?</em></p> <p>Normally, SS is a 'chip select', purely "to let the chip you are writing to know to expect some data".</p> <p>However, the chapter on SPI in the RM0008 manual is 50 pages long. I don't know it well enough to answer definitely, and the answer is slightly more complex than you might like.</p> <p>AFAIK, the STM32F's NSS pin can be used in master mode to allow multiple SPI masters to collaborate and share the same signal connections. I don't believe you are trying to do that.</p> <p>AFAIK, there is no need for the Maple's (STM32F's) NSS to be used for SPI single master, single slave comms when the Maple (STM32F) is master.</p> <p>Further, the signal output on NSS from the Maple (STM32F) isn't enough to select between more than one slave on shared SPI signals. You have to do that in your program.</p> <p>I'd recommend not using Maple's NSS (if possible), and just get a TLC5917s working. Either wire the TLC5917's serial-in/serial-out in series, and use a common LE, or use multiple Maple pins to control LE (effectively chip select) with digitalWrite (or digitalwritefaster) to select the appropriate TLC5917, and so direct the MOSI data to the correct chip. </p> http://forums.leaflabs.com/topic.php?id=74199#post-105068 Tue, 10 Dec 2013 21:41:46 +0000 jappiemike 105068@http://forums.leaflabs.com/ <p>OK, but my real problem is that the changing of the SS line appears to happen some time after the CLK starts to toggle and the data transmission begins, I used a fairly slow data rate and I imagine the problem would be worse at 18MHZ. I'm also using digitalwritefaster to make my interrupt as fast as possible but I wouldn't think this is a problem. Is setting SS to low purely to let the chip you are writing to know to expect some data or is it tied to the SPI data transmission from MOSI?<br /> Cheers<br /> Mike </p> http://forums.leaflabs.com/topic.php?id=73&page=4#post-105065 Tue, 10 Dec 2013 12:18:24 +0000 superprp 105065@http://forums.leaflabs.com/ <p>ok, finally after upload the bootloader with an arduino board as indicated in the maple bootloader i have found that the problem was that i was compiling the code as RET6 not REV3+ and i have the board REV5.<br /> i hope that this could help you in the future checking this point at first. </p> http://forums.leaflabs.com/topic.php?id=74199#post-105064 Tue, 10 Dec 2013 12:10:17 +0000 gbulmer 105064@http://forums.leaflabs.com/ <p>jappiemike - maybe try running the same program, but replace <code>random(255)</code> with <code>0x81</code> (first and last bits are 1, others 0)? It might be easier to see the relationship between edges.</p> <p>The SPI on Maple can run in a four different "modes" described at<br /> <a href="http://leaflabs.com/docs/lang/api/hardwarespi.html#id2" rel="nofollow">http://leaflabs.com/docs/lang/api/hardwarespi.html#id2</a><br /> These set the relationship between the clock (idle LOW, or idle HIGH), and the edge on which the data is sampled. AFAIK, this shouldn't be a big issue while you are outputting data, but will determine the idle state of the clock.</p> <p>Even when Maple's SPI is running as the master, IIRC, it doesn't assert the SS pin. Asserting SS is the job of your program, using a digitalWrite.</p> <p>(Full disclosure: I am not a member of LeafLabs staff.) </p> http://forums.leaflabs.com/topic.php?id=73&page=4#post-105063 Tue, 10 Dec 2013 07:23:02 +0000 superprp 105063@http://forums.leaflabs.com/ <p>I have just checked that maple doesnt work, this could be the reason to not detect the serial port.<br /> I have created a basic program to ON the LED when the program start but the led still OFF after program the board.<br /> When i program the board everything is ok. Could someone tell me if i am doing something wrong? or what could i checked?<br /> No error has been found during device programming.<br /> Thank you. </p> http://forums.leaflabs.com/topic.php?id=74199#post-105056 Tue, 10 Dec 2013 03:28:47 +0000 jappiemike 105056@http://forums.leaflabs.com/ <p>Hello again, So I'm working with some TLC5917s for an LED matrix which is working fine with a mega2560. When I tried one of the SPI examples ( the last one on the SPI hardware page) I noticed that it doesn't work as expected.</p> <pre><code>// Use SPI port number 1 HardwareSPI spi(1); void setup() { // Turn on the SPI port spi.begin(SPI_4_5MHZ, MSBFIRST, 0); pinMode(9,OUTPUT); // this line is always here pinMode(10,OUTPUT); // this line is always here } void loop() { digitalWrite(9,LOW); // this line was added later digitalWrite(10,LOW); // this line was added for 1 run spi.write(random(255)); digitalWrite(10,HIGH); // this line was added for 1 run digitalWrite(9,HIGH); // this line was added later }</code></pre> <p>there is a screen dump at the following link to illustrate the results <a href="https://drive.google.com/file/d/0B1ghmDU_EL2BME1Pd28yb0p1d1E/edit?usp=sharing" rel="nofollow">https://drive.google.com/file/d/0B1ghmDU_EL2BME1Pd28yb0p1d1E/edit?usp=sharing</a><br /> Running the 2 variations of the program with my logic analyser gives these 2 results. Notice how the CLK((7) and MOSI (6) don't line up with the SS(5) as you would expect or my indicator (4 pin9) and when I remove the SS toggle it doesn't get activated by the SPI library but the CLK and MOSI still fire. So what am I doing wrong or are there problems with the library?<br /> Cheers<br /> Mike </p>