stryd_one

You have to add your file to makefile.orig. See my last few posts for full explanation. Code?

Youre talking bout the vids from the first post, we're talking about the 2nd post... now who's smokin :) Hey guys: Remind me to hang shit on every imperfection of all your midiboxes one day. Oh wait, noone here would ever do that, because we respect other DIY efforts for what they are... right?

Geezus i knew i couldn't give them props without you going spastic. I should a kept my trap shut. No, but it gives them the perfect experience required to know what makes for good sound for their kind of music, and that's what the system is for. It also gives them industry contacts out the wazoo to help them and tell them what not to do. If you're gonna quote me, don't take it out of context, and you won't have to ask pointless questions like that one. The rest of the sentence which you removed, answers your question. I didn't say they had theory, I said that I believe it's crucial, but they have experience. Exactly, they were talking about why they named it the way they did, not how they designed it. It's paying homage, not copying. Your'e so busy being a hater that you can't even hear what's going into your ears. No, they said they built 16 bass bins, and they spent that much time on it. Not the whole system. It would not have been just those two guys, it woulda been the whole crew. What's wrong with not remembering the name of the wood (that you never heard before) your engineer told you to buy when you were pilled out of your mind? Exactly. It's like midiboxing. Why buy when you can build. <"I know more that these guys" rant removed> I'm sure you'd find some way it was not perfect to pick on. Of course they did! What the hell do you expect, they should spend a small fortune building a sound system for a crowd and then try to not attract a crowd? I never implied otherwise. Dunno why you thought that my boosting their effort was an invitation to put up a defense wall like you just did. We all know that you know your shit - that's obvious - the point is, so do these guys, and you hanging shit on them for their hard work is just wack. It only serves to make you look bitter.

wiki - search - toolchain ;) We use make (the tool, IE make.exe) now.

Bah cut him some slack... it's kinda like 'studio advice in 20 words or less'... In 20 words or less I dunno if any of us could do a lot better ;) And artesia: screw literacy. Theory is crucial in my opinion, that's not gonna be news to you...but experience is king. Those guys have more real world experience than the entire midibox forum combined. I'll judge the 'valve sound system' when I hear it ;)

Isn't that exactly what the LC is for?

I doubt anyone else will care to say this so directly, so I'll save you some wondering: I think you're screwed buddy :( You could maybe read the eeprom from another board and de-solder yours and burn it, or maybe do some reverse engineering to figure out novation's bootloader (BTW, a row of black squares sounds familiar! hahah) or whatever, but to be honest, I think you're gonna have to take it to get repaired. Or use it for spares and stuff it with a far more powerful and flexible midibox core ;)

Sorry, I should have posted an update... Haven't been spending as much time on the forum lately so I'm not very attentive. :-[ Some of us have been chasing better pricing in the background, and we're coming along nicely... We'll be back soon, hopefully with better pricing :)

If you change makefile.orig so it looks like this: # default rule that defines the .hex files which should be created # note: always require a "cleanall", since dependencies (e.g. on .h and .inc files) are not properly declared all: cleanall setup_mbseq_v3.hex setup_mbseq_cd_cd.hex setup_mbseq_tk.hex setup_mbseq_v3_3b_dejfHW.hex Then it will try to create setup_mbseq_v3_3b_dejfHW.hex, from setup_mbseq_v3_3b_dejfHW.asm. Did you have the asm file by that name, in the same directory? Did you put the .hex extension on that line in makefile.orig?

;D ;D ;D (the universal language)

Short answers: Eduy, I don't mind the spanish posts, the translator (foxlingo/autotrans) is doing a good job, I hope my English posts are OK - you seem to be reading them just fine :) MPLAB/MPASM are no longer used for MIOS. Use GPUtils/GPASM instead. That is not supported, it really should be removed from the wiki. It was an experiment done by one user, and does not really work. Use the skeleton you can download from ucapps.de download page :)

Running MIOS on a 4685 (which defaults to 4-bit mode) with the LCD wired as 8-bit, can fry your PIC. one more time, because saying it 1 million times doesn't seem enough ;D Running MIOS on a 4685 (which defaults to 4-bit mode) with the LCD wired as 8-bit, can fry your PIC. I don't understand why so many people have this idea that you can wire the thing up and ignore the schematic and TK's design and instructions, and expect it to work OK. Sure, it *might*. It *might* also fry the PIC or the LCD. I'm not singling you out here m00die - you're one of many to make this mistake :) Check the cabling, twice, as per cimo's instructions. Try reburning the bootloader, re-upload MIOS, re-upload the app (try one of TK's hex files first, in case your mods broke it) All in mios studio, smart mode, wait for upload request... blah blah One at a time, as always ;)

Ahh my bad. good on you for linking them up man :)

Sweet. FWIW, supporting other pins for connection is trivial. You just use a #DEFINE to specify the pins in the driver, wrapped in an IFNDEF. This means that if the pins are already defined elsewhere (say, in the makefile using a -D switch) then the definition is not overwritten, and the user-specified pins are used. So, if some dude wants to use J5, they specify the J5 pins in the makefile, and initialise the J5 port correctly in their app's init function. Edit: an example would help: driver sram.inc #ifndef SRAM_PORT_CS #define SRAM_PORT_CS PORTA #endif #ifndef SRAM_PIN_CS #define SRAM_PIN_CS 5 #endif Sets the CS pin to the default (PORTA.RA5 in my case) driver sram.mk # make rule for relocatable version $(OUTDIR)/sram.o: $(MIOS_PATH)/modules/sram_512/sram.asm $(GPASM) $(GPASM_FLAGS) $(GPASM_INCLUDE) $(GPASM_DEFINES) $(SRAM_DEFINES) $< -o $@ so that when the app builds the driver module, it passes the SRAM_DEFINES to GPASM (yep, works with native C drivers and SDCC too) app makefile SRAM_DEFINES += -DSRAM_PORT_CS=PORTA SRAM_DEFINES += -DSRAM_PIN_CS=6 Overrides the defaults shown above To PORTA.RA6 HTH!

HOT TIP (Pay attention now people): The best way to allow yourself to hear someone who is trying to talk to you over load music, is to BLOCK your ear. Yes, I know, it doesn't sound sensible at first. Try it. Stick one finger over that little bit of cartilege and push it into your ear canal and make a seal. All the music is all muddy and drowned out. Get a friend to speak normally next to your ear. Clear as a bell ;) Yes: Rhythm and melody. (and that's not 'rhythm/melody as perceived by the listener', so people calling Hendrix 'noise' were just lacking education) Oh and people; If it's even vaguely legal, it's not a rave. It's a dance party, or a discotheque, or something. Raves are illegal by nature, and as such are pretty much nonexistent these days. Blame England, and conservative anti-drug politicians.

Hardware routing?! :o (sorry for English posting - please continue in German, I'll use a translator)

Yay![me=stryd_one]does the 'it's working' dance[/me] AHA! Right - a midi feedback loop will certainly cause Java to fall on it's face. BTW, so will heavy streams of corrupt midi. Don't ask me how I know that ;D Now, there is only one thing left for you to do: Sell me your midisport 8x8. ;D

Hahahah math for paranoia, we do have a lot in common ;D Well, it's either lazy, efficient, or a bit of both. Sometimes resolving such equations is fun...sometimes it's just a waste of time :D

Exactly. All is good there, you have the right tools, and they are correctly found in the path. :) The problem must be something else.... Only old projects use MPASM, new projects should use GPASM. Eduy: Can you also paste the messages you see, when you run 'make'? Which code are you compiling? Did you download the .zip file from ucapps.de? Maybe you could attach the code here, or you can email it to me if you would prefer - just PM me for my address :) I wish I spoke Spanish right now! Sorry Eddie! Thanks for translating, Cimo!

Futureman: What's with the secrecy? I'd like to think that anyone with sufficient knowledge of MIOS and time to build a basic sequencer like this for free, would share it publicly - it's kinda the midibox way, right? All: TK should be the one to respond to this request.

Yeh, you can use a binary counter IC as a basis for this. Not that you need to (see above)

Aussie English is almost always the same as UK English (The Queen's)... US English however, has been umm... let's say it's been 'bent'. You lot spell things with a Z a lot (quantise), and say zee instead of zed, drop lots of hints to etymology (analogue), etc etc etc. In fact pretty much everywhere that speaks English does it the UK way, officially... but unofficially, US English has become the de facto standard, thanks to the internet combined with people not paying attention in school ;) This whole situation sh*ts me, and is the primary basis (along with imperial measurement) of my recurring joke trademark: America. We're not England! tm

If the compiler outputs an error about __wparam, then you have done something wrong with the toolchain setup - the code is fine. I think that you must be running an old version of SDCC, or that the makefile is not working correctly. Please copy and paste from the command line, everything that you see when you run "make" Also, type: sh --version sdcc --version gpasm --version make --version And paste the output. So, you should paste something like this: C:\Documents and Settings\stryd_one>sh --version GNU bash, version 2.04.0(1)-release (i686-pc-msys) Copyright 1999 Free Software Foundation, Inc. C:\Documents and Settings\stryd_one>sdcc --version SDCC : mcs51/gbz80/z80/avr/ds390/pic16/pic14/TININative/xa51/ds400/hc08 2.8.0 #5117 (Mar 23 2008) (MINGW32) C:\Documents and Settings\stryd_one>gpasm --version gpasm-0.13.5 beta C:\Documents and Settings\stryd_one>make --version GNU Make 3.81 Copyright (C) 2006 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. This program built for i386-pc-mingw32 C:\Documents and Settings\stryd_one> This should help us find the problem :) Good luck!

Cool, I love a bit of math. I never knew such a thing existed, my toolset is usually a pencil, paper, and a basic calculator. I imagine I take somewhat longer than you to do this stuff :D

Probably funnier if you follow this link instead ;D