<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Definitely out-of-date or new hardware, though if it’s just that, updating the main MBED library fixes it. Usually though, if there’s a library which is a child of another, say a FAT filesystem for the SD library, it’s like they got out of sync in terms of function prototypes.<div class=""><br class=""></div><div class="">I don’t have any older MBED hardware. I probably would have more success, though, if I went with an LPC17xx board, but I wanted M4. LPC17xx stuff came out in 2010 I think.</div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On May 17, 2016, at 8:29 PM, Neal O'Hara <<a href="mailto:ngohara@ncsu.edu" class="">ngohara@ncsu.edu</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">"<span style="font-size:12.8px" class="">Many of the examples in the MBED repo have hardware descriptor headers which are out-of-date"</span><br class=""><div class=""><br class=""></div><div class="">Out of curiosity, do you know if they are: out of date for new hardware, or out of date doesn't even run on older original chips?</div><div class=""><br class=""></div><div class="">Just trying to keep an eye on good platforms for future IOT projects...</div></div><div class="gmail_extra"><br class=""><div class="gmail_quote">On Tue, May 17, 2016 at 6:53 PM, Alex Davis via TriEmbed <span dir="ltr" class=""><<a href="mailto:triembed@triembed.org" target="_blank" class="">triembed@triembed.org</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I’ve been trying MBED for a few weeks now and thought I’d comment on the overall ‘ecosystem’ it provides. On the surface, there’s a good choice of boards and plenty of libraries. Deeper in, it’s somewhat of a mess.<br class="">
<br class="">
I’m already aware of the microARM vs ARM C issue with the boards, which caused issues due to lack of standard C functions. Recently I’ve found there are issues with both libraries and code, in terms of hardware support and dependencies. In my case, I’m trying to play a wav file while simultaneously doing other things in threads, like PWM for LEDs. I’ve yet to find a SDFileSystem which works properly with a wavfile library for FRDM-K64F, not to mention one that works in an MBED RTOS thread.<br class="">
<br class="">
Many of the examples in the MBED repo have hardware descriptor headers which are out-of-date, necessitating an update of MBED before compiling. That’s fine, but doing this usually breaks the other libraries, and I’ve yet to successfully get code working where I had to go past updating just mbed.h. If that doesn’t do it, you’re on a wild goose chase.<br class="">
<br class="">
I’ll have to go back yet again and see how well TI has done in providing working libraries for the launchpad add-on boards in CCS. It’s valuable to me to not have to re-invent libraries for things like displays, sensors, and storage. I guess I’m lazy and need libraries AND working examples. I just don’t have the time to do it all from the ground-up.<br class="">
<br class="">
BTW I found my FRDM-K64F pin D8/PTA0 is actually not wired to the correct pin on the MCU! It’s attached instead to something to do with the JTAG debugger interface. I went nuts trying to figure out why an LED would not light, only to stumble upon a MBED post which explained the situation. Luckily I was able to lift a leg on a resistor and move it over to D7 and get it working.<br class="">
<br class="">
I’ll keep plugging on the MBED stuff but I have a few projects in the queue which are going to continue to be ATMEL-based, just because they’re simple and I know ATTINY/ATMEGA very well.<br class="">
<br class="">
<br class="">
|\ | (¯ \/ |¯\ |V| |\ ¯|¯ |¯) | \/ | | | |¯\ (¯ /¯ /\ |V|<br class="">
|-||_ (_ /\ |_/ @| | |-| | | \ | /\ |^| | |_/ (_ . \_ \/ | |<br class="">
<br class="">
<br class="">
<br class="">
<br class="">
<br class="">
<br class="">
<br class="">
<br class="">
_______________________________________________<br class="">
Triangle, NC Embedded Computing mailing list<br class="">
<a href="mailto:TriEmbed@triembed.org" class="">TriEmbed@triembed.org</a><br class="">
<a href="http://mail.triembed.org/mailman/listinfo/triembed_triembed.org" rel="noreferrer" target="_blank" class="">http://mail.triembed.org/mailman/listinfo/triembed_triembed.org</a><br class="">
TriEmbed web site: <a href="http://triembed.org/" rel="noreferrer" target="_blank" class="">http://TriEmbed.org</a><br class="">
</blockquote></div><br class=""></div>
</div></blockquote></div><br class=""><div class="">
<div class="">“The right of the people to be secure in their persons, houses, papers, and </div><div class=""> effects, against unreasonable searches and seizures, shall not be violated, </div><div class=""> and no Warrants shall issue, but upon probable cause, supported by Oath </div><div class=""> or affirmation, and particularly describing the place to be searched, </div><div class=""> and the persons or things to be seized.”</div><div class=""><br class=""></div><div class="">US Constitution 4th Amendment - It's The Law</div><div class=""><br class=""></div><div class="">|\ | (¯ \/ |¯\ |V| |\ ¯|¯ |¯) | \/ | | | |¯\ (¯ /¯ /\ |V|</div><div class="">|-||_ (_ /\ |_/ @| | |-| | | \ | /\ |^| | |_/ (_ . \_ \/ | |</div><br class=""><br class=""><br class=""><br class=""><br class=""><br class="">
</div>
<br class=""></div></body></html>