• Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About analog604

  • Rank
    MIDIbox Newbie

Profile Information

  • Gender Not Telling
  • Location northeast usa
  1. problems setting up MIOS32 toolchain

    Yep, I all needed was the basic xcode452 cli tools from Apple Dev downloads.   I just double checked the bill of materials in the mounted dmg: lsbom -s `pkgutil --bom /Volumes/Command\ Line\ Tools\ \(Lion\)/Packages/DeveloperToolsCLI.pkg` | grep make ./usr/bin/gnumake ./usr/bin/make ..and this is where it also places gcc.   So no need to alter standard shell pathing.   I worked for quite a few hours trying to get the toolchain to compile under redhat and I can get everything but the compilers! So I'll stick with the mac dev environment until I can figure it out.   I already lived in Terminal shell all day!  ;)   -Jay
  2. problems setting up MIOS32 toolchain

    The toolchain was not building so easily under Linux, the package gcc build in particular failed. Not a big problems though,  I've got to setup the gcc prerequistes more properly.    Will do that later.   In the meantime I got MIOS32 apps compiling from the Mac via Terminal/shell using the appropriate toolchain.  :))  After installing xcode command line tools for 'make', I was all set.   Thanks again..  next I will port Arduino code to Cortex for MIDIbox... that should be interesting.   :)
  3. problems setting up MIOS32 toolchain

    Thanks very much TK for that insight!   I remember reading and seeing the linkage somewhere on this forum a month ago or so ago, but couldn't find it today, and wanted to try code on my fresh new LPC17.  :)   I'm on a Mac, but didn't want to get into the mess of using Xcode for this stuff, as I've been at odds with it for years.  For example only trying to compile basic GNU code that was no issue on Linux and Solaris boxes.   I'll try your toolchains!   cheers~ Jay
  4. Hi Guys,   This post relates my experience with problems using MIOS32 Toolchain (version mios32_toolchain_linux86_20101024.tgz) on Centos Linux (redhat basically) and what I did to  resolve it by setting up a working Arm compiler for the LPC17/NXP1769.   Here's my Linux version: Linux um 2.6.18-308.24.1.el5 #1 SMP Tue Dec 4 17:43:34 EST 2012 x86_64 x86_64 x86_64 GNU/Linux   So I'm attempting to build MIOS32 apps on a Centos Linux server: Followed wiki instructions:   and installed toolchain mios32_toolchain_linux86_20101024.tgz set my paths and environment.   Then I go to build the test app and got an error from the toolchain compiler: [root@um 001_forwarding_midi]# make rm -f project.hex Creating object file for app.c arm-none-eabi-gcc: /lib/ version `GLIBC_2.11' not found (required by arm-none-eabi-gcc) make: *** [project_build/app.o] Error 1   # OK am I using the right one? lets see [root@um 001_forwarding_midi]# which arm-none-eabi-gcc /usr/local/mios32_toolchain/bin/arm-none-eabi-gcc # YES- ok run compiler to see what happens, broken [root@um 001_forwarding_midi]#  arm-none-eabi-gcc arm-none-eabi-gcc: /lib/ version `GLIBC_2.11' not found (required by arm-none-eabi-gcc)   # Find out what is linked into it and if those libraries resolve (no they don't) [root@um ~]#  ldd /usr/local/mios32_toolchain/bin/arm-none-eabi-gcc /usr/local/mios32_toolchain/bin/arm-none-eabi-gcc: /lib/ version `GLIBC_2.11' not found (required by /usr/local/mios32_toolchain/bin/arm-none-eabi-gcc) =>  (0xffffe000) => /lib/ (0x00bae000)     /lib/ (0x00b8f000) --------- So after checking everything in the setup it seemed that my Linux version simply wouldn't work with the old libc compiled against the toolchain.    I looked into installing the older libc 2.11, but couldn't get that to compile fully so moved on. Then I downloaded arm-2008q3-66-arm-none-eabi-i686-pc-linux-gnu.tar from Installed into /usr/local Updated path in /etc/bashrc and checked to see if it ran (looks good): [root@um trunk]# /usr/local/arm-2008q3/bin/arm-none-eabi-gcc -v Using built-in specs. Target: arm-none-eabi Configured with: [snip...] Thread model: single gcc version 4.3.2 (Sourcery G++ Lite 2008q3-66)   # checked shared library dependencies (looks good): [root@um trunk]# ldd /usr/local/arm-2008q3/bin/arm-none-eabi-gcc =>  (0xffffe000) => /lib/ (0x00bae000)     /lib/ (0x00b8f000) Then went on and built several MIOS32 apps without incident.  :smile:   Hope that this may save some time for someone, the entire process took 3 hours of mine!   cheers Jay  
  5. Core_LPC17 with LPCXpresso and LPC1769 parts

    guys, I built the LPC-17 today and verified that the alternate (less expensive) NXP part works just fine. Bootloader was flashed correctly and then I loaded MIDIbox NG onto it for a quick test.     More detailed photos here   cheers~ Jay
  6. Core_LPC17 with LPCXpresso and LPC1769 parts

    Interesting, kpete..  thanks for doing a compare.    I was hoping that the core module would arrive today to test this out!  No worries though, holiday mail being what it is. -Jay
  7. Core_LPC17 with LPCXpresso and LPC1769 parts

    Thanks for the replies.   Yes the photo is incorrect on the NXP Semiconductors OM13000,598 Mouser listing. The PCB package came with a card providing a URL to NXP and featured a coupon code plus logos of NXP, core_red, and Embedded Artists (it's but rewrites to this):     Thumbnail photos that I made of it:     Same in high resolution:     Next week sometime I'll build out the LPC17 core board and test out MIOS32.     -Jay    
  8. Hi! For the MIOS32 application can the part 'OM13000,598 EA LPCXpresso board' be used? The CORE_LPC17 parts list calls for this part: 924-EA-XPR-003 So I had made a mistake and ordered the 'EA LPCXpresso board' which contains the LPC1769 and rev B of the board. It costs a few dollars less. Successfully programmed the MIOS32 bootloader with positive indicators including the 3 pulse fades of the LED. I just don't have the CORE_LPC17 PCB to try out MIOS32 apps yet. If no one knows for certain, I'll report back my findings! -Jay [edit: corrected links]
  9. MIDIbox CV V2 Concept

    Hi TK, I'm looking forward to experimenting with all these great features that you are building into the code. : ) I just ordered my first LPC module and LPC1769. cheers~ Jay
  10. Built a Midibox CV this weekend

    Hi ! I haven't seen too many postings of completed MIDIbox CV builds, got any of your build to share? It is in progress (got sidetracked greatly in 2011 !).. full build progress photo log: Jay's MIDIbox CV build circa 2011 with this recent set containing most recent photos: Dec2012 CV pics It works and calibrated with my bench top variable PSU but I need to get it working with my in-progress modular synth PSU.. almost there. [edit: oh yeah, this frontpanel design was inspired by Sneakthief's work, except that I made it for 5U] -Jay
  11. MIDIbox CV V2 Concept

    This is excellent news TK! I love the Lemur control surface, and having worked Lemur quite a lot within the past two weeks, I admire your bitwise code in the template. :) The only problem that I have with this is that I am only just completing the MIDIbox CV as a 5U x 3U wide module for my still being soldered modular synth. I am looking forward to building this one when available. cheers~ Jay