buhler

i hope somebody asked before doing this... :o http://cgi.ebay.com/MIDIbox-Analog-Sid-MOS-Synth-SidStation-Clone-LoFi-Acid_W0QQitemZ200217139437QQihZ010QQcategoryZ38071QQrdZ1QQssPageNameZWD7VQQcmdZViewItemQQ_trksidZp1638Q2em123

Woo Hoo!! paid taxes.. paid Nebula!! ;D ;D

PM sent!! ;D

i get a small click as well with my MbSid but i'm using 6581's and i've tested 10 different ones in my box. most of them don't click but it just so happened that one of the two that matched (filter, clip etc..) had the "click." i don't know about 6582's as i haven't received mine from wilba yet but i assume that clicking is just a "chip-trait" that these Sids have. i don't think you can really do a whole lot about it.

if you're using a Mac, i highly recommend using Xcode. Fluke has been teaching me how to program with "C" and Xcode has been awesome! ;D

it sounds like you need to tell your compiler where the file is first. check this out: http://www.midibox.org/forum/index.php/topic,11197.0.html this was me a week ago. ::) this is stryd_one at his best. this cleared it all up for me so read the 6th post down in this thread and it should help a lot! ;D

i did the wiring according to that diagram and that's when i started having the freeze problem, then i connected the 4 remaining pins (D0-D3) to their respective connections and voila! it seems to be working in 4-bit mode, just not with TK's omissions. i seem to be repeating myself a lot don't i? :P i noticed some people have said that they had to ground D0-D3 on the LCD end. i wonder if having them connected to core J15 is replacing the grouding??? @stryd- if you're still interested in making the wiki for modifying the setup_*.asm, i could really use a crash course in changing the LCD driver. i had a look at the main.asm file as well as the app_lcd.inc file that wilba linked me to in the device id v1.9d and i have no clue what to do with them... i understand the process of re-compiling now but i have no idea how to change the driver and how to recompile it with the setup and device id, etc. without someone holding my hand. sorry. i'm really nervous to change all this when i know it's functioning already. i don't want to ruin this after i've come this far. i don't mind messing with the firmware but once i mess with the core like wilba said, there's no turning back... :( by the way, here are some pre-finished photos:

i don't know anything about the V1 process but as far as the LCD and DIN/DOUT goes, it should all be in the main hex file. just watch out for the 4-bit/8-bit issue i seem to be having. it's no fun. make sure your LCD will run in 4-bit mode otherwise you may have to re-ID your PIC and change the LCD driver.

OK here's the deal. when i bought the LCD, the place i bought it from said it was an "OLED" LCD. is that different than a "PLED?" second, initially i did have D0-D3 connected to nothing, but now i have D0-D3 on J15 of the core connected to D0-D3 on my LCD and it works PERFECTLY. no feezes, no nothing. so, i can't see why going against the old "if it ain't broke, don't fix it" adage would help UNLESS, i am harming my core because of this connection. yeah, i'm just overwhelmed. do you mean search the code or MIOS has a search i can use to find certain lines in the code? i'm having a really tough time figuring out 1. what ID to give the PIC since it is already 0 unless it stays 0 and re-uploading the ID will cause the IC to ask for a new LCD driver (?) and 2. what to do with the driver once i figure out what the driver is. as far as i can remember it was this one, http://www.ucapps.de/mios/lcd7_clcd_v1_9a.zip but i haven't checked it lately... yeah, my wife says the same thing about me worrying too much... i can't really help it :-[ as far as the search goes, i just kept getting results to this thread and nothing else... i'll keep at it.

so if i do go ahead with one, i should do it Plog's way? that's fine with me. i have a Midi interface that won't run on my Win2000 machine and i like windows better for Mios. this seemed like a great solution. when i get the time, i may build one. ;D

don't forget me... the special ed. kid! ::) i ride the short bus here every morning...

i know what you are saying but i'm not sure i need 8bit mode to run my LCD... it seems to be 4bit and 8bit compatible. if i understood what Wilba was saying about the code end of things, i would be more than willing to change what needs to be changed. i'm more or less overwhelmed and intimidated by "rebuilding" code and there isn't enough about rebuilding the code for me to follow Wilba's overview without f***ing my Sid firmware up. the Pin switching on the core is no problem but i have no idea how to even start with the code. i assume that along with the change id app, i will have to modify the 6581main hex file that i already modded for SIDL/SIDR to also use a custom LCD driver? do i need to write a driver? last time i checked, the lcd driver links were dead. i don't know stryd, i may as well get a new LCD so that i don't have to worry either way... :( i am eternally grateful for your guys' help!! i'm just a little lost again... [edit] here's a link to my LCD user manual: http://www.sure-electronics.net/mcu,display/DE-LM004.pdf

Is this still going strong? any new developments? i think i'm going to build one of these but i'm curious how Jidis is doing with his pcb. ;D

did you get my email Neb? if not i'll send another...

Awww... thanks for the explanation!! i see. i just had these two extra buttons and only one core and i figured that this would be a good way to utilize them.. :) anyhow, that makes a lot more sense! ;D thanks seppoman!! now my MbSID is pretty much done!! woo hoo!!!

i'm more of a newbie than you nILS so you can adopt me!! ;D i still want to know if my SIDL/SIDR issue has a cure... thanks!!

my question was: i connected all 4 data pins that were left unconnected before i.e. D0-D3. that "fixed" my freezing LCD problem. i just wanted to make sure that i wasn't doing anything wrong by doing this. i don't have a CAN connection so i figured it would be ok, plus my LCD datasheet says that my LCD runs in both 4bit and 8bit mode. Wilba was very kind. i just wanted to make sure that my much more "lazy" fix was not going to cause my midibox to blow up in the near future. thanks Wilba!! [edit]i didn't ever mean to sound ungrateful!! sorry if i did! :-[

http://www.midibox.org/dokuwiki/midibox_sid_faq'>http://www.midibox.org/dokuwiki/midibox_sid_faq http://www.midibox.org/dokuwiki/midibox_sid

*bump* i just want to make sure this is ok :)

alright stryd!! i did it! ;D it worked perfectly!! i had a little trouble with figuring out which pins on shift register #1 i was using on the DOUT module but i got it!! everything works now!! woo hoo!! i'm thinking of adding bankstick switching buttons but i need to get my front panel before i know if i have enough room. thanks SOOO much stryd!! YOU ARE AWESOME!! once i get my enclosure i will post pics so you (and everyone else) can see it. thanks again!! EDIT: after playing around with my MbSID, i noticed that even though the buttons/LED's/LCD screen show that both the right and left SID's are either on or off, i get no change from the actual SID chips. is this due to the fact that i'm only using preset patches at the moment? or am i forgetting something in the code? when i turn one SID off, it still plays. something isn't totally right unless this is a normal occurrence when using presets... ???

i'm paying soon Neb, i promise!! i gotta pay the taxman first!! >:(

just got my encoders Frank!! thanks so much!! super fast shipping = awesome ;D

anytime man!! if you ever have questions just let me know. i majored in composition and theory so i'm more of a 'programmer' than a performer anyway. ;D it totally is... i've been challenged on so many levels already! it's hard not to let this take over the actual reason i'm building one! some days i'd rather work on my midibox and dream of making more than write music! it's scary!! :o

stryd. you are AWESOME!! i wish i was home to try this out! sorry for being such a newb but if this is for the good of the community then i don't feel so bad! ;D unfortunately, i still have 2 small questions. i want to be sure. 1. after you run 'make,' will the .hex file be sent to the same folder as the .asm file or do i need to type 'save' or something to keep the .hex file that was just created? 2. in creating a SIDL and SIDR button, i have to modify the setup_*.asm file as well as the CS_MENU_BUTTONS.inc, as you already know. so, once they've been modified, which i already did, do i load them separately with the C: command and create .hex files out of both of them and then upload them separately onto the core of my MbSID? thanks again stryd!!! ;D

bummer! ;D damn my music degree!!! i need to go back to university to study programming!!