Jump to content

Academic Planner

Members
  • Posts

    36
  • Joined

  • Last visited

Posts posted by Academic Planner

  1. After a few more day of pulling my hair out, staring at system paths, wrapping my mind around instructions that don't seem to apply to Windows 10, and reflowing all solder, I'm still just getting corrupt characters on the display and realizing I'm now just spinning my wheels. I'm officially giving up. Going back to the LCD. Not really worth the hassle!

    Thanks for the help, anyway. :hypocrite:

  2. Was something else adjusted in that .hex file? I switched the OLED to an LCD and this is what I'm getting now.

    20190211_200444.jpg

    Never mind. I realized what I was doing wrong with the LCD. Still having issues with the OLED, though.

  3. hmmm, now I'm getting this from MSYS:

    sh: SET: command not found
    sh: fg: %programfiles%gputilsbin: no such job
    sh: fg: %programfiles%SDCCbin: no such job
    sh: fg: %PATH%: no such job

     

    following the directions here: http://www.midibox.org/dokuwiki/windows_toolchain_quickstart

     

    *edit*

    All paths were set & pointed the MSYS path to the specific midibox_fm_v1 folder and I'm still getting this again:

    Makefile:29: C:/MIOS/TRUNK/BIN/include/makefile/asm_only.mk: No such file or directory
    Makefile:32: C:/MIOS/TRUNK/BIN/modules/app_lcd/dummy/app_lcd.mk: No such file or directory
    Makefile:35: C:/MIOS/TRUNK/BIN/modules/aout/aout.mk: No such file or directory
    make: *** No rule to make target `C:/MIOS/TRUNK/BIN/modules/aout/aout.mk'.  Stop.

  4. So I managed to get tortoise working (thank you) and grabbed the new file structure, but now I'm getting the following error in MSYS:

    Makefile:29: /include/makefile/asm_only.mk: No such file or directory
    Makefile:32: /modules/app_lcd/dummy/app_lcd.mk: No such file or directory
    Makefile:35: /modules/aout/aout.mk: No such file or directory
    make: *** No rule to make target `/modules/aout/aout.mk'.  Stop.

    So it looks like the makefile is referencing the old structure. Am I understanding this correctly? I really appreciate your patience. I'm almost there! :cheers:

  5. 1 hour ago, Antichambre said:

    But question??? How did you tried the 8bit driver without the right recompiled version ???
    Hummm lol

    :shock:

    I had multiple folders from the last few years. Perhaps a few edits were made along the way? Starting fresh today.

  6. I think I might have windows working properly again. I'm able to compile but I'm getting lots of "Address exceeds maximum range for this processor" errors in MSYS. I'm not totally sure this matters.

    So I just double checked - there is no app_lcd or app_lcd_8bitdriver file in the src folder. As a matter of fact, those file structures you posted above don't seem to apply to the midibox_fm_v1_4i, unless I'm not understanding of course.

    Maybe the edited file should be somewhere else? 

  7. On 6/23/2014 at 5:18 PM, TK. said:

    Ok, crossing fingers!

     

    Please try this version: http://www.ucapps.de/mios/midibox_fm_v1_4j__sammichFM_8bitlcd.zip

     

    I've enabled the new USE_8BIT_LCD_DRIVER option for the setup_pic18f4685_sammich_fm.hex file only!

     

    Best Regards, Thorsten.

    Is there any chance someone could fix this link? I just purchased a Vishay OLED for my Sammich, but it seems the wiring modification isn't working. Perhaps my firmware needs updating?

  8. The initial email went 3+ years ago, the waiting list was established over 1 year ago, we hit over 50 preorders (list not completely updated) and there hasn't been any sort of official word on an update. I'd think it's pretty safe to say this isn't happening. Compound this with the recent Volca FM release and this is making even less sense. Prove me wrong? (again)

×
×
  • Create New...