<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="bbPress/1.0.2" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>LeafLabs Garden &#187; Topic: Most frustrating outstanding Maple issues?</title>
		<link>http://forums.leaflabs.com/topic.php?id=10230</link>
		<description>A place to share, learn, and grow...</description>
		<language>en-US</language>
		<pubDate>Fri, 22 Jan 2016 00:04:51 +0000</pubDate>
		<generator>http://bbpress.org/?v=1.0.2</generator>
		<textInput>
			<title><![CDATA[Search]]></title>
			<description><![CDATA[Search all topics from these forums.]]></description>
			<name>q</name>
			<link>http://forums.leaflabs.com/search.php</link>
		</textInput>
		<atom:link href="http://forums.leaflabs.com/rss.php?topic=10230" rel="self" type="application/rss+xml" />

		<item>
			<title>ala42 on "Most frustrating outstanding Maple issues?"</title>
			<link>http://forums.leaflabs.com/topic.php?id=10230#post-22316</link>
			<pubDate>Thu, 07 Feb 2013 21:00:22 +0000</pubDate>
			<dc:creator>ala42</dc:creator>
			<guid isPermaLink="false">22316@http://forums.leaflabs.com/</guid>
			<description>&#60;p&#62;&#38;gt;2. Update gcc to &#60;a href=&#34;https://launchpad.net/gcc-arm-embedded&#34; rel=&#34;nofollow&#34;&#62;https://launchpad.net/gcc-arm-embedded&#60;/a&#62; gcc 4.7 supports fixed point out of the packet&#60;br /&#62;
When you do that, you have to add two nops to the micros() function in wirish_time.h, as the gcc 4.7.3 compiler optimizes the code too good. Currently the systick interrupt has no chance to intercept as expected, as the systick_get_count() and millis() functions declared inline are now really handled inline, single assembler instruction to be precise. The nops fix this problem.&#60;br /&#62;
&#60;pre&#62;&#60;code&#62;static inline uint32 micros(void) {
    uint32 ms;
    uint32 cycle_cnt;
    uint32 res;

    do {
        ms = millis();
        cycle_cnt = systick_get_count();
        asm volatile(&#38;quot;nop&#38;quot;);
        asm volatile(&#38;quot;nop&#38;quot;);
    } while (ms != millis());&#60;/code&#62;&#60;/pre&#62;</description>
		</item>
		<item>
			<title>crenn on "Most frustrating outstanding Maple issues?"</title>
			<link>http://forums.leaflabs.com/topic.php?id=10230#post-22314</link>
			<pubDate>Thu, 07 Feb 2013 19:32:43 +0000</pubDate>
			<dc:creator>crenn</dc:creator>
			<guid isPermaLink="false">22314@http://forums.leaflabs.com/</guid>
			<description>&#60;p&#62;New releases for the IDE would be the thing that I'd like, mainly so the libraries that leaflabs wants and the libraries I write with testing in the IDE are the same. Adding Wire.h support is also good. The ability for libraries to include other libraries is something that would be useful without having to do so in the sketch would be nice.&#60;/p&#62;
&#60;p&#62;Also, I don't have enough Maple Minis, but I don't think that's something you can fix really ;P
&#60;/p&#62;</description>
		</item>
		<item>
			<title>gbulmer on "Most frustrating outstanding Maple issues?"</title>
			<link>http://forums.leaflabs.com/topic.php?id=10230#post-22312</link>
			<pubDate>Thu, 07 Feb 2013 18:51:52 +0000</pubDate>
			<dc:creator>gbulmer</dc:creator>
			<guid isPermaLink="false">22312@http://forums.leaflabs.com/</guid>
			<description>&#60;p&#62;bnewbold - my votes would be:&#60;/p&#62;
&#60;p&#62;1. Consolidate existing fixes to libmaple. Nothing new, just the fixes. There are a bunch of threads asking for help, and the fixes are often already in github. They need to be integrated and packaged as a proper release.&#60;br /&#62;
2. Update gcc to &#60;a href=&#34;https://launchpad.net/gcc-arm-embedded&#34; rel=&#34;nofollow&#34;&#62;https://launchpad.net/gcc-arm-embedded&#60;/a&#62;  gcc 4.7 supports fixed point out of the packet&#60;/p&#62;
&#60;p&#62;Edit:&#60;br /&#62;
3.Please integrate bug fixes back into the git repo, in a coherent way (i.e. one main thread), with some instructions on how folks can 'stay current'.
&#60;/p&#62;</description>
		</item>
		<item>
			<title>bnewbold on "Most frustrating outstanding Maple issues?"</title>
			<link>http://forums.leaflabs.com/topic.php?id=10230#post-22309</link>
			<pubDate>Thu, 07 Feb 2013 18:18:07 +0000</pubDate>
			<dc:creator>bnewbold</dc:creator>
			<guid isPermaLink="false">22309@http://forums.leaflabs.com/</guid>
			<description>&#60;p&#62;Hello old friends!&#60;/p&#62;
&#60;p&#62;Starting next week i'm going to be rejoining the Leafers and will have a bit of time to give the World of Maple some much needed love and attention. We'll give a more comprehensive and long-term update later, but for now I was wondering what the most frustrating problems people are running in to with the existing Maple toolchain and documentation. Many of the bugs in our tracker are (shamefully) months or years old; which ones are still causing difficulties?&#60;/p&#62;
&#60;p&#62;Things that are less likely to happen any time soon are: fully tested support on the latest Microsoft Windows platforms and world-changing improvements in cross-platform SerialUSB/DFU USB interop, because (as always) improvements there are dependent on OS vendor decisions and could break backwards compatibility.&#60;/p&#62;
&#60;p&#62;Things that are more likely to happen soon are: integrating outstanding pull requests to libmaple, Linux platform support and packaging, updates to the libmaple toolchain (gcc-arm-embedded 4.7, etc), adding peripheral support to libmaple, and API-preserving bug fixes.
&#60;/p&#62;</description>
		</item>

	</channel>
</rss>
