grahamg

Members
  • Content count

    18
  • Joined

  • Last visited

Community Reputation

0 Neutral

About grahamg

  • Rank
    MIDIbox Newbie
  • Birthday 02/04/1978

Contact Methods

  • Website URL http://www.ee.columbia.edu/~grindlay

Profile Information

  • Gender Male
  • Location New York, NY, USA
  1. schematic file for AOUT module?

    TK, any chance you'd be willing to share your Xcircuit files? thanks! Graham
  2. schematic file for AOUT module?

    hi moxi, thanks, but i'm looking for a schematic file (.sch for eagle). -graham
  3. Hi Everyone, I need to make some modifications to the AOUT module for a MIOS project that I am working on and would love to avoid having to re-create the schematic file for the AOUT board design.  Does anyone know where I can find a copy of the Eagle/Protel/whatever schematic file?  I'd prefer Eagle's format, but anything would be helpful. thanks! Graham
  4. bankstick not working

    Stigmata, That was exactly the problem.  Thank you so much!! I was under the impression that the core module was completely compatible with both the 16f and 18f pics.  Didn't realize that there were these subtle differences. Again thank you! -Graham ps. is this difference documented somewhere on the site?
  5. bankstick not working

    Just to clarify: MIOS doesn't seem to even see my bankstick.  The core never tries to format it and if I try to call MIOS_BANKSTICK_SetCtrl, I get an error code of 2 (bankstick not available). Has anyone had this problem?  Any ideas for what could be causing it? Thanks, Graham
  6. Despite my best efforts checking and re-checking wiring and parts, I cannot seem to get the bankstick module to work.  I'm just trying to verify that it works with my core module by running the bs_xfer code in the download section.  I can compile the main.hex and convert to a syx file just fine, but when I upload it to the core (either using MIDIOX or sysexbox, I get errors returned from the core).  Sysexbox returns error codes 0A 00, 0A 3A, and 00 45.   I have tried several different 24LC256 chips and have double and triple checked the wiring.  I've also tried both MIOS 1.7 and 1.8 RC1. Help! thanks, Graham
  7. MIOS C Wrapper Beta

    Thanks Thorsten!   Everything works great with the old SDCC release.   :) -Graham
  8. Status of SDCC evaluation

    I'm getting some stange LCD behavior with the wrapper: calls to MIOS_LCD_PrintCString result in black spaces between each character in the string.  For example, "dog" prints as "d_o_g" where "_" represents a solid black block.   If I use MIOS_LCD_PrintChar, everything works fine.   Any ideas??! -Graham
  9. Howdy everyone, I'm working on a project which requires that I be able to make use of features in both the sequencer and midio128 applications.  I need to be able to load a pattern from a bankstick and play it back (and be able to adjust the BPM in real-time), BUT the playback should be used to drive a whole bunch of leds.  I would especially like to be able to load a different DOUT pin mapping for each pattern (ie.  keep the mapping in the bankstick as well and load both of them before playback).   Can anyone give me an idea of how doable this all is?  Is this something I should be able to do with minor tweaks to the seq or midio128 apps (and which should I use?), or am I looking at something requiring a more substantial coding investment? Many thanks, Graham
  10. Problems with CORE module...MIDI-

    Well, I rewired the LCD for the third time and voila, clean, clear, and sensible text!  This time I swapped out the entire cable and that did it.  I've been using IDC cables so I guess there must have been an internal short. Now I can finally get crackin' on the rest of my design! Thanks again everyone. -Graham
  11. Problems with CORE module...MIDI-

    I'm pretty sure that the data lines are correct, but will check again.  I just got the EL inverter for LCD in the mail yesterday and have tried it out, but am otherwise testing without it.  Am I correct in assuming that the brightness pot on the core should not work with this type of backlight? Don't have a PIC programmer (got the PIC pre-programmed from SmashTV, but just ordered the JDM), so I can't try wiping the chip, although this sounds like a good idea. I'm starting to think that the display is just busted; maybe I'll just bite the bullet and order a new display....
  12. Problems with CORE module...MIDI-

    Hmm, the on info I have on the display is that it is made by Micrologic Vikay under P/N 2420STELYGBN.  Here is a link to the ebay page if it helps: http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItem&category=26206&item=3827659029&rd=1&ssPageName=WDVW So, the problem you had was that the display didn't actually conform to the HD44780 specs?
  13. Problems with CORE module...MIDI-

    First, let me thank everyone for their comments.  Getting a MIDIBOX going for the first time (especially with limited electronics experience) can be a frustrating experience!  ;) I completely re-wired my LCD and seem to have solved most of my problems, at least I am finally getting stuff on the display.   The problem now is that its mostly garbage.  Depending on what app I upload, I can sometimes make out what the text probably says, buts there are all sorts of weird characters mixed in.  For example, lcd7_clcd prints: 'Jgnno"Wornf#_""" *C+"2226"V.Knosg The first line is supposed to be 'Hello World', right?! I've double and triple checked the wiring as well as checked for shorts with a multimeter since archived posts in the forum suggested these to be likely candidates for the problem.  I also tried re-upping MIOS several times... Could it be a shielding issue?  I tried moving my test station away from any computers, fans, etc., but didn't seem to make much difference.   Maybe the display is just shot and I should try a new one? Thanks! -Graham
  14. Problems with CORE module...MIDI-

    Thanks for the reply, Doc! Jumpers are all on and I've got communication between MIDI-OX and the core now (had wiring reversed on MIDI OUT pins, stupid me!).   Now I've uploaded MIOS 1.7 which I think is working properly since it echoes F0 00 00 7E 40 00 0F F7 when I send it.  However, I don't get any random events in MIDI-OX after starting up the core.  Shouldn't the PIC be sending out random readings from all the 'ghost' connections?  When I boot, I get black squares on my lcd for 2 second (bootloader) and then it goes blank.  I also only get the one single 'ready' sysex message and then nothing else. I've tried uploading all kinds of apps, but the behavior is the same.  Shouldn't my LCD display something after the black bootloader blocks?  Its a 4x20 HD44780-based display that I got on ebay.   BTW, my PIC ID is all 0s. Please help me out here guys, I've read through everything on this site and I'm pulling my hair out trying to get this thing working!!!!
  15. Problems with CORE module...MIDI-

    Yes I'm using Midi OX to try and upload MIOS, but I'm not getting any response from the core at all.   When I power up, my LCD has two bars of black squares for about 2 seconds after which it goes completely blank.   I tried replacing the optocoupler, but still no luck.   One thing I'm not sure about is the jumpers on the board.  They should all be on for uploads and all off for normal use, right?   Any suggestions are *very much* appreciated. Thanks, Graham