stryd_one

Nice font :) Reminds me of the lettering on a piece I have here, that I sketched when I came up with my alias... Ahh memories :)

Hey that's a good one thanks opkod! Very simple circuits with very common components.

I would check the doco for your revision You think? ;D I'll just stop helping then. heehehehe Asking again.. did you use smart mode? What were the issue, the file, and the solution? Fell free to paste it... and don't forget auaimbctg Hang in there...

Well yes and no... One person I know had a friend who is proficient with PC based C programming write some code for him. It worked, just fine - but the code was slow and big. On a PC it would not have even been noticeable, but here, it was a little different. A few little tweaks decreased codesize and processing time, but it is evidence that, although C is C is C.... SDCC for PICs is a different story to GCC for PC. As fluke wisely said, sometimes it is better to start out on PC and move on from there... YMMV ;)

Might be easiest to get an ISA SB Pro 2 and drive that...

Yeh, maybe you could summarise for us ;)

Hey mate sorry to hear you have to bail, but your new child is more fun than any midibox anyway :) If you change your mind I'm sure we'll all help out, and you can solder it one joint at a time if you want :) Did you buy a chip from wilba and put it in? C64's don't come with 6582's :)

Sounds like the bootloader is starting, but not MIOS. Did you use MIOS studio in smart upload mode? (You should!) What do you recieve on your midi interface at this point?

I had a very quick look and I don't know MBCV well... Only one thing stood out immediately... Are all the necessary bank selects called before these code snippets?

Nah I just tried it and analysed the output :) I've read about 1/4 of that document so far and he has already mentioned some of the things I've posted about above, for EG: What I've found so far was that SDCC would compile very heavy ASM if the code was not just-so. The only solid recommendation that can really be made here, is to try stuff out and see how you go... What I tried, and what was mentioned in that article (pointers to ram not rom), differ somewhat... But I can tell you that when I started to head in the direction suggested there, the code size exploded.

Who plays barre chords anyway? ;D

Just another plug... If someone would like to make the perl scripts (search/replace), we can replace the macros and we may be able to compile in GPASM (cross-platform)

A custom driver for your custom LCD is the trick here :) Rather than modifying MIOS_GLCD0.inc, you can copy it's contents into your app_lcd.inc (some minor editing is required) and set your PIC ID to use a custom LCD. All set :) PS we just chatted about this but I put it here also for others to refer to ;)

Heya goonzy... Use the search, Luke. ;)

That's the lucky diode! If you guess right you get a SID synth ;D Don't ask what happens if you get it wrong. Isn't it fun!? ehehhe

LOL we are such geeks mate.... I thought the same thing. I'm actually a little weirded out by that. I didn't even stop and think about it... I wonder if the pattern of characters gave us a subconcious hint?

MB64e will take pots/faders too :)

Be aware that that model is not one of the fancy (high contrast) STEP displays :(

Heh I was looking at that page the other day, I was wondering if you had noticed the other displays there too :) You get that a lot at optrex

LOL I wasn't serious about the matrix mate ;D If you can find me a PS2 keyboard with the same matrix as a C64 one, I think you might also be able to find me a giant pink dinosaur. However using a PS2 driver is possible, but of course would mean major modifications to the application, which i why I said it won't be easy.

Welcome aboard! About four months late... and I think that was all said in the previous posts ;D But you're correct! Maybe sometimes true but not in the case of SDCC. When you inline the function, the switch statement compiles entirely differently, and it kills the efficiency. It's better to call the function from the switch statement - and I mean call a function, not using a function pointer. Just to add something interesting to my post... The jumptable generated by a simplified switch/case statement is generally faster than a series of 'if's , but there is some code that is always present for the jumptable, so if you only have a few options, or if you won't be using 'break' at the end of each case, sometimes the 'if' is actually faster. Sometimes.....

Most synth/controllers use a soft takeover function for that - the knob does nothing until it's value reaches the target (0 in your example) and then it's movement is tracked (so in your case you would turn the knob to 0, and then turn it up)... That said, encoders are certainly a better solution. Welcome aboard!

Hey it might not be the prettiest, but how does it sound? :D

Well, if your PS2/USB keyboard just so happens to have a matrix laid out exactly like a C64 you'll be right ;) If you want to actually connect the keyboard connector to the PIC (not tap directly into the switches) you'd need to write a PS/2 driver. I have some documentation and code if you're serious about it, it will tell you all you need to know.... But it won't be easy.

Fine by me :D It's great so far, just the way it is! Ohh yes please ;D