RyuX

sammichFM OLED Display

40 posts in this topic

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? 

Share this post


Link to post
Share on other sites

I think you didn't refesh your MIOS folder since a long time ;)
http://svnmios.midibox.org/listing.php?repname=svn.mios&path=%2Ftrunk%2Fapps%2Fsynthesizers%2Fmidibox_fm_v1%2Fsrc%2F&rev=1168&peg=1161#

Then refresh it...

Set the USE_8BIT_LCD_DRIVER flag in "setup_pic18f4685_sammich_fm.asm" file

    ;; set this flag to 1 in order to enable 8bit LCD access mode for PIC18F4685 derivatives.
    ;; IMPORTANT: this option requires a modification on the sammichFM hardware:
    ;; Connect:
    ;; - PIC Pin RE1 to J16:D3
    ;; - PIC Pin RE2 to J16:D2
    ;; - PIC Pin RB1 to J16:D1
    ;; - PIC Pin RB0 to J16:D0
    ;; Compare following schematic for sammichFM J16 pinning: http://www.midibox.org/dokuwiki/lib/exe/fetch.php?media=sammichfm:sammichfm_base_pcb_rev_1.pdf
    ;; And following schematic for PIC pinning: http://www.ucapps.de/mbhp/mbhp_core_v3.pdf
#define USE_8BIT_LCD_DRIVER 0

replace the "src/app_lcd_8bitdriver.inc" by mine
compile and upload "setup_pic18f4685_sammich_fm.hex" in MIOS Studio"

Best
Bruno

.

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites
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.

Share this post


Link to post
Share on other sites

Ok understood you never use MIOS trunk.
You have to checkout the MIOS, using tortoise svn is very easy.
just follow this howto http://www.midibox.org/dokuwiki/doku.php?id=windows_toolchain_svn#tortoisesvn
this page is useful too: http://www.midibox.org/dokuwiki/doku.php?id=windows_toolchain_core#path_environment_variables

First try by yourself but If you're really stucked I can take the hand on your computer like we already did ;)
 

Edited by Antichambre

Share this post


Link to post
Share on other sites

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:

Share this post


Link to post
Share on other sites
7 hours ago, Academic Planner said:

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.

This indicates that your 'make' compiler doesn't find your new and fresh MIOS directory.
This is a path issue. Did you follow this ? -> http://www.midibox.org/dokuwiki/windows_toolchain_svn#path_environment_variables

MIOS_PATH and MIOS_BIN_PATH need to be set ;)
Always restart you computer after this operation, for changes to become effective.
 

Share this post


Link to post
Share on other sites

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.

Edited by Academic Planner

Share this post


Link to post
Share on other sites

try this hex:
https://www.dropbox.com/s/ma98bbopt8s1tzb/setup_pic18f4685_sammich_fm.hex?dl=1

It's a 8bit version then extra connection are necessary.

    ;; set this flag to 1 in order to enable 8bit LCD access mode for PIC18F4685 derivatives.
    ;; IMPORTANT: this option requires a modification on the sammichFM hardware:
    ;; Connect:
    ;; - PIC Pin RE1 to J16:D3
    ;; - PIC Pin RE2 to J16:D2
    ;; - PIC Pin RB1 to J16:D1
    ;; - PIC Pin RB0 to J16:D0
    ;; Compare following schematic for sammichFM J16 pinning: http://www.midibox.org/dokuwiki/lib/exe/fetch.php?media=sammichfm:sammichfm_base_pcb_rev_1.pdf
    ;; And following schematic for PIC pinning: http://www.ucapps.de/mbhp/mbhp_core_v3.pdf
#define USE_8BIT_LCD_DRIVER 0

;)

Edited by Antichambre

Share this post


Link to post
Share on other sites

Well, I'm getting closer!

 

Not sure if this is due to the hardware or firmware. Looks cool, though. ;)

ot_KmJuE.jpeg

Edited by Academic Planner

Share this post


Link to post
Share on other sites

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.

Edited by Academic Planner

Share this post


Link to post
Share on other sites

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:

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now