tarzan boy

can anyone help here with the above post? For now I've uploaded the precompiled syx files (i.e. 6581 slave2, etc) to my pics, but i do want to make a few changes when i have my complete control surface finished.

that sucks about the pic, i was lucky i think that i didnt burn one. one got really really hot when i disconnected everything from the computer and took my board to the solder station to redo a resistor with the 9v still plugged into the board with the pic still plugged into the board. 2 minutes later when i was finished my soldering the pic was really really hot. luckily 3 days later when i got things working i was finally able to discover that that one wasnt damaged. i never had a problem with running the portdiag while the pic was plugged in, but i did notice that before i ran the portdiag, a few of the voltages of the LPT were on when they should be off, so i always ran the portdiag before plugging the pic in. you are indeed in the worst phase, i agree. have you tried to get free samples from microchip.com? they ship to nearly anywhere and it took 2 weeks but the chips were free... have you tried every imaginable combination possible? that's the key. on linux with v.7 and v.8beta? on windows with v.5 and v.7? in DOS with v.5? powering from LPT? powering from batteries? a different resistor value? (i dont know if you caught that I got mine to work with 220ohm instead of the correctly calculated 330ohm)

have you tried with the sid v1.7a? I had that on my only working sid board until a few days ago and i didn't have any complaints at all about the range of the thing. In fact if anything i thought it was much better than the prophet64; both in signal-to-noise and in my ability to change things (filters obviously only being one small part of this...) plus it was such a HUGE pain to load p64 into my c64s, since i only have a tape drive... I havent tried the 303beta9 that i've uploaded yet because everything is offline while i make my optimized psu, but i really want to try these new algorithms.

yes, new device id did indeed appear ,then i reinstalled the mios v1.8 with corresponding device_id successfully; i'm not getting a sysex message telling me the correct id too. and although it wasnt responding last night to the pic i was using, today all 3 are working with the corresponding sid slave syx files (i'm using the 303beta9 since it apparently has a bug fix i need)

seppoman, very clear explanation, thanks. I actually figured out half of it last night just before bed; i realized the onething i hadnt tried was recompiling the change-id app with mplab ide with different device-ids in the asm file. Once i did this it worked peachy. However now i am at the point where mios is telling me "READY" but i am unable to upload my prepared slave sid apps. I changed the device-id in mplab for those (i think i did anyway, i did a lot of stuff last night) but still the core is ignoring my upload. btw- i am using only the pics and one core to make sure i'm interfacing the pic directly; i dont have them linked up yet.

Shoot. OK this is what I'm doing: I have pic18's that I want to be 1, 2, and 3 with regards to device id. I have already uploaded the MIOS v1.8 as it comes in .syx format from the download page. (when I try to upload a mios.syx file that I have used hex2syx.pl -os_upload -device-id 0x0[id] I get no response from the pic/core/LCD at all (just the black bars, or if mios is already uploaded, it boots straight to mios ingoring my new attempt at uploading) in the change_id folder, I use the command >perl hex2syx -device_id 0x0[id] main.hex and I get the resulting main.syx file. I have tried uploading this change_id file during the 2-second boot phase, after that when mios is "ready" or even after that when a SID app is already on with "Internal Patch" written on the screen. all 3 ways don't seem to change the 8 byte string that starts when the pic boots, which i've read tells you what device id it is. in my case, I get this: 00 F0 00 00 7E 40 00 01 F7 when i have a sid app uploaded (in which I have changed the device id with the MPLAB IDE to the correct ID inside the .asm file) i get the following 13 messages: 00 F0 00 00 7E 40 00 01 F7 00 F0 00 00 7E 46 01 0D 00 00 00 F7 00 F0 00 00 7E 46 01 0D 01 00 00 F7 00 F0 00 00 7E 46 01 0D 02 00 00 F7 [then a big one i won't type out that is onviously the "Internal Patch" screen] and this cycle of the above 4 messages cycles 3 times. my question is: what should i get to identify what the device id is, and what am i doing wrong that can't change the device id?

now you just need no job and 5 more days and it'll work in Windows for no reason! :) I used label stickers from a grocery store to tape together my AA's (which i eventually didn't use), I took apart a mini-radio-control car remote control and used the battery pack from the body to chain my two AAA's together.

i can at least help you with the burning pic part, i just got past that today, go to this thread http://www.midibox.org/forum/index.php?topic=2952.0 and look at mine and others' progress.

when i try to compile 303beta9, i get the following error, any chance anyone knows what this means? Error[113] C:\WINDOWS\DESKTOP\303_9\CS_MENU_PRINT.INC 186: Symbol not previously defined (CS_MENU_PRINT_DEV_Invalid) Error[126] C:\WINDOWS\DESKTOP\303_9\CS_MENU_PRINT.INC 186: Argument out of range (-9547 not between -128 and 127) Halting build on first failure as requested. BUILD FAILED [5 minutes later] thinking maybe there was a typo, i changed the appearance of CS_MENU_PRINT_DEV_Invalid to CS_MENU_PRINT_Invalid and now I just get the 2nd error, except it now reads: Error[126] C:\WINDOWS\DESKTOP\303_9\CS_MENU_PRINT.INC 186: Argument out of range (-541 not between -128 and 127) Halting build on first failure as requested. BUILD FAILED

Sysex Librarian (mac osx app) doesn't let me listen and write at the same time. Lame,eh? I'm thinking maybe get my win98 to send midi with my midi-via-serial plug then monitor with the mac, or vice versa.

I have just completed successfully burning without the rb5 10k resistor attached, the 10k resistor may disable LVP but i don't think this matters when you have 9 volts (or in my case 11) at MCLR. Anyway, having RB5 resistor not attached was how i was finally able to get this to work so I suggest trying it if nothing else works. My LCD is operating with these 3 fresh pics so RB5 is definately not disabled... smash, could you take a look at my question i just posted regarding change_id?

hello, I have read the asm file and it seems that I'm good with just typing >perl hex2syx.pl main.hex -device_id 0x01 i get the following: Block 003000-0033FF allocated - Checksum: 0F Block 003400-0037FF allocated - Checksum: 08 I then upload this after mios 1.8v boots (after 'Ready' appears) but i do this and nothing happens in the LCD. Is that it? Is the device_id changed now? I use mac's SysEx librarian so there is no way for me to read the values inside the mios except thru the LCD.

oh my god. what can i say... well, I can say that I will never again think that computer behavior won't change with repetition. The only changes I can say I've made from the above post to my success 5 minutes ago is this: I removed the 10k resistor from pin RB5 I added another AAA battery to my chain to power MCLR so now I'm reading 11V from pin 1 to Vss. I switched back to Win98 (i actually was about to try another pic programming software but decided "lets see, I'll try broccoli18 v.07 one more time") Now? Success! And with probably the sloppiest pic programmer in the history of MB. Here is the successful output for the mios_bootloader_v1.1b.hex (renamed boot0.hex here) Detecting PIC,,, Found PIC18F452 Reading hex file... Erasing memory from 0 to 32504... Programming memory from 0 to 32504... **(here it takes a good 3-4 minutes with cursor blinking whereas before it was returning the error within 20 seconds)** Erasing ID locations... Programming ID locations 0 to 8... Programming ID configuration bytes 0-13... Programming done. Wisefire, if you havent sent off you pics yet, give it another shot! it'll dave you quasi-2 weeks of waiting ImAlive, yeah, i screwed walwarts. totally off with the voltage. all my 9volts read at 14-16 volts. I dont thin kyou should disconnect the MCLR from 9V when programming though, without MCLR attached broccoli18 wouldnt even recognize my pic.

i remember reading a while ago that indeed jeri (that woman) designed a new chip that was a monster sid; its not just a name for multiple sids inside the machine. I looked at the schematics of this about a year ago and i seem to remember the 'sid' that she designed being incorporated into the same ICs that control joystick input. She's also the person who designed the c64-direct-to-tv joystick gadget thing, which had all of the c64 recreated on one single IC. (it was even possible to hack the thing and add a keyboard, joystick, and disk drive to it) The reviews i read of that said that she 'faithfully' recreated the 6851 for this toy, although i don't know how connossierre the reviewers were in sid-dom. :)

smash, i would love to take you up on that offer, but unfortunately (at least in this sense) i live in italy; and so far i'm not desperate enough to send you the pics and wait, when i feel that i'm so close... the pic18f i bought from you in august is working perfectly! so i'll let you know. but for anyone else who has successfully used broc18, anything?

wow. 5 days of no forum in the middle of troubleshooting a pic burner. i can't think of a worse torture. using the google cache that is 1 year old only got me half of the info i needed i think. OK, so here I am right now: After lots of micro-incremental changes and do-overs, i am at the point where I am getting the following when I try in Linux (now i've installed linux onto the machine instead of using a live-cd) erasepic a ton of times readcfg gets this (sometimes reliably, sometimes every 4th try, sometimes never then i switch to another pic18f and its reliable again): Configuration bits 00 27 0f 0f 00 01 85 00 0f c0 0f e0 0f 40 Programmable ID bytes ff ff ff ff ff ff ff ff Device ID 04 27 Found PIC18F452 erasepic a ton of times, still same cfg info (i.e. the 6th bit 85 is not changing to 81-- what i have read should indicate that write-protection is disabled/erased) then I writepic with the standard bootstrap loader available from the portal (my failure to change bits for device ID 0x01-3 successfully in IC-PROG is another story for a diff. thread) writepic outputs the following: Detecting PIC... Found PIC18F452 Using hex file mios/boot0.hex. Reading hex file... Erasing memory from 0 to 32504... Programming memory from 0 to 32504... pic_verify: Memory doesn't match at address 0. Error in pic_prog: Success so its not working... well i thought maybe there is a chance in hell it's working but when i tried, the pics are not responding in the functioning CORE that I have.. So far with repetition I am consistently getting either all zeros and no pic detected or the above output; so something is consistent and something is obviously wrong. little notes on setup: -my 9-volt went down to 7.5 volts so i added a AAA battery to the chain and now i am (semi)reliably reading all 3 pic18fs, whereas before i was only getting 2 of them read. -the resistor calculation, either i havent completely understood, or the suggestions are innacurate: I have 4.5 volts coming from my LPT so I calculated 300 ohm, but 300 ohm, 330 ohm and 550 ohm don't work, 220ohm (like original schematic suggests) works. Right now I have a chain of a 220 and a 330 with the 330 shorted with alligator clips (for easy switching, sick of going back and forth to the soldering table! :) ) - i am powering the pic's vdd/vss with the 4.5 from LPT pin 13 (on my computer this is constantly 4.5 volts); 2 AA batteries, 2 AAA batteries, 1 AA+2 AAA, 2AA+1AAA, and 2AA+2AAA wasn't working. :( -after trial and error I am using a pol. cap with value 220uF, all other combinations weren't working (even using 'BIG-ASS' caps with value 2000MF like readme suggests trying) -i have a 10k resistor between pins 38 and 31 to disable LVP but i'm not sure this is needed, no one seems to have mentioned this -pins 11 and 32 are bridged together (the two Vdds) and pins 12 and 31 are also bridged together like schematics for pic-burner, jdm module, and core module all show. this wasnt explicitely mentioned in the broccoli18 schematic but i thought this should be the case ok, sorry for this long post, i've had 5 days alone!

everything compiled perfectly, i dont really know whats what as far as setting the LPT port in bios setup, but i'll give it a shot.

well i tried a linux live-cd for the first time yesterday; GREAT-- i finally got an ethernet card to work that has been sitting in my computer useless for years! But broccoli didnt seem to work; although i'm not sure of its expected behavior. I tried to compile and run it before doing any breadboard work and I had the problem of a message saying "cannot set port address to 378" i have no idea how to address this. (no pun intended) anyone have a clue?

HA! ;D i love it, 'not be so #!?"#@ newbie'! well today i tried out the broccoli software on a linux live-cd boot on my old pc (i have a new mac i use for everything nowadays that has no parallel port) and I had the problem of a message saying "cannot set port address to 378" i have no idea how to address this.

so no one has seemed to answer this question: does one of the ceramic caps like the ones used as bypass additions on the bottom of the MB boards work or do you need a polarized one? I'm not an expert so i don't know what 'elko' means either. Also, can anyone confirm this working in Windows 98 or within DOS on a Win98 machine? My only PC is an old 500mhz with Win98 on it that can't even handle a DSL connection without locking up; i'm hoping i can just use it instead of trying to do it on another machine. thanks

Wisefire, any luck with Broccoli18 yet? I start building mine tomorrow (i want to have a good nights rest before this potentially stressful task) and would like to know your progress with it all.

i wish i had time to remake a SID if i had the choice of pokey or SID, but i think Dr. Wily as well as me and probably others are hoping to find some project to utilize a pokey chip in some sort of homemade musical interface, uh, thing.

can the 303 engine coexist with the normal one? i dont know too much about the 303 one, i was hoping to get all my normal midibox sid stuff straight before i delved into that. Yeah, it does sound like you had the exact same issue as me. to all though: sorry i havent uploaded a sample of the problem, I've been picking pears for the past 2 weeks (only one week left YESS!) on a farm so when i get home i'm so exhausted that i just look at the soldering iron, the half completed bankstick board, and my dissasembled core/sid/din/lcd and sigh.. but this weekend i hope to get back on that train again. or if it rains this week....

great!! I love this! I was thinking of using a PCB but I hadnt even taken apart my keyboard to realize there was a big PCB under it! the only thing stopping me from using this idea is the fact that this now has been done!! :-\ i cant tell from the detail in the photo, which IC is that next to the LCD?

Well I am aware of this problem, yes, i have indeed read about that. and noticed it inside the C64 when using Prophet64... and i don't really consider it a problem because the 'ghost note' is just as loud as the noise floor anyway. What i'm talking about is a LOUD, SHRILL high pitch steady note that is on when a note is not being played. This note does not correspond to the note played previous, whether i do a C-0 or a F-4, its still the same high pitch squeal.