Sasha

Thank you all!

This is very cool feature. I LOVE it! It's about time to build a sequencer.

Thanks mate! ;)

I`m back after long time out of MB community and doing electronics in general. I have quite a few unfinished projects that needs some attention. In most cases it is just building housings and final touches, but still a lot of work. I feel bit rusty now, but I`ll catch what I`ve missed. See you around! ;)

Sorry for not dropping by for some time, I`m having some private issues. If I manage, I`ll make a prototype in near future.

Maybe would be good idea to put some list who is interested.

PCBs are ready for prototyping for quite some time, but I put my money savings and efforts onto 303 style sequencer(stripped x0xb0x)as it seams to have more perspective. Not sure is there enough people interested into drum sequencer to pay itself. But some small prototype series could be done.

And, here some more videos from the development phase.

Sounds good. :)I wasn`t aware of 303 edit feature. Gotta check it out.

Yes, CS will be on another board/chip connecting with BassBoy and SQ303 a sequencer from x0xb0x. I`m afraid project is not open source, but I hope he will realized the benefits of OS projects, and will change his mind. I`m working on it. ;)

And, here are some better sounding samples... Sequence 01 - by TG ViRUS.mp3 Sequence 02 - DJ Abadroza.mp3 MIDI files.zip

assembled and tested ;)

Not sure about glitching possibilities ... it is classical MIDI bassline synth. Control surface is in developing phase. Actually, I already have a working prototype. It is well known x0xb0x sequencer that I did for myself, and now we are planing to join the forces and create a CS for BassBoy so result will be something like digital x0xb0x based on parts that are easily available. I must say that Aleksandar is planing drum module as well based on same SSP (small synth platform) as he calls it. Yes, shipping price is high, but you know all problems I had when organizing x0xb0xes from Serbia. Ordering multiple BB is best way to save on the shipping significantly.

I`d like to inform you about cool little project of my friend Aleksandar Krstic. It is inexpensive bassline synthesizer based on ATXMega32D4. Me and kokipsiho had a chance to get one of the prototypes. Bassboy is now available for ordering trough Mikroelektronika: http://www.mikroe.com/eng/products/view/658/bassboy/ Here is the picture of the my bassboy from the prototype series. Now it is changed a little bit. Aleksandar made a quick demo video...

I built a Shuthi-1 with modified DIY CEM PCB. It will look bit different at the end as I couldn`t find nice pots, and I don`t like those wobbling Alps that are sold by Farnell. So I`m going with panel mount pots. I like the synth. It sounds pretty good for what it is. It is definitively inspired by Sammich which is good thing, but it is much smaller than Sammich. I`ll probably make them both look like they are from the same "series". Cool project. My recommendations!

DOG finally barks! :) Besides altering the initialization, I needed to change the second line offset to 0x40. Thank you once again for your help. ;)

Cool, I`ll try it as soon as I back home from work. Thanks for the help mate.

Thank you philetaylor. I did so, but still no 2nd line. :( I`ll try alter the initialisation. I hope it should look like this: movlw 0x39 ; 8bit interface, switch to instruction table 1 call MIOS_LCD_Cmd movlw 0x1c ; BS: 1/4, 3 line LCD call MIOS_LCD_Cmd movlw 0x52 ; Booster off, set contrast C5/C4 call MIOS_LCD_Cmd movlw 0x69 ; set Voltage follower and amplifier call MIOS_LCD_Cmd movlw 0x74 ; set contrast C3/C2/C1 call MIOS_LCD_Cmd movlw 0x38 ; back to instruction table 0 call MIOS_LCD_Cmd movlw 0x0F ; display on call MIOS_LCD_Cmd movlw 0x01 ; Clear Display call MIOS_LCD_Cmd movlw 0x06 ; Entry Mode call MIOS_LCD_Cmd

I managed to make display work with MB808 with help of my friend, but it don`t shows content of 2nd line. I`m using 2x16 instead of 3x16 DOG. Are there something else I should configure in order to show 2nd line?

The problem is that I can`t recompile the code if I add that "select LCD type #7..." part to the asm code. I pointed make file to the doglcd driver.

Have I asked incredibly stupid question or nobody can`t give me any clue what I`m doing wrong? I did my best to follow the integration instructions but still getting nowhere. :(

Julien, the link is not OK, and search engine don`t give me any results. Can you please check it again? EDIT: It must be because Programmers Lounge is not public forum. I have tried this LCD with dog test application and it worked fine, after that I change just makefile to use dog driver. After compiling, uploading and rebooting it seams LCD is working fine, but after powering down, it fails to initialize. When I upload the same MB808 code, it don`t initialize until I upload test app first, and than MB808. Again, it work until powering it down.

I`m having hard times compile MB808 application to use dog driver. Can somebody please explain this in details. I tried to follow steps from Readme file. "Assembler-Only" Applications ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 1) main.asm (or main.inc): ensure, that the application includes the global <app_lcd.inc> instead of "app_lcd.inc" Where do I set it and how? I don`t see anything like that in .asm files of MB808 2) Makefile: include app_lcd.mk --- # include application specific driver include $(MIOS_PATH)/modules/app_lcd/clcd/app_lcd.mk I believe my makefile should look like this: MIOS_PATH = . MIOS_BIN_PATH = ./bin export MIOS_PATH export MIOS_BIN_PATH include Makefile.orig # include application specific LCD driver (dummy driver by default) # include application specific driver for DOG LCDs include $(MIOS_PATH)/modules/app_lcd/dog/app_lcd.mk 3) main.asm (or main.inc): call MIOS_LCD_TypeSet from USER_Init hook: --- ;; select LCD type #7 ;; (custom LCD driver, hooks in $MIOS_PATH/modules/app_lcd/dog/app_lcd.asm module will be used) ;; Parameter #1 and #2 select the enable pins like for common CLCD driver ;; Note that the DOG driver switches to CLCD (type #0) after initialisation! ;; Up to 2 DOG based LCDs are supported ;; E input of first LCD at D.7, E of second LCD @C.4 movlw 0x37 ; E pin movwf MIOS_PARAMETER1 movlw 0x24 ; E2 pin movwf MIOS_PARAMETER2 movlw 0x07 call MIOS_LCD_TypeSet Where exactly should I put this code? I have tried various locations in the .asm file, but than I`m receiving error when compiling. I Have also tried to put it in the main.inc but receiving error again.

I have just received negative doglcd with red backlight with help from kokipsiho. I like it, but not entirely satisfied with it`s contrast. \ May somebody tell me how exactly can I change the contrast in driver. I see these lines, but not sure how to increase/decrease it. movlw 0x50 ; Booster off, set contrast C5/C4 movlw 0x7c ; set contrast C3/C2/C1 Am I looking in right place?

Good news. TK checked my PCB and said situation is "relaxed" so I`m continuing with 1st design. :) There were some changes on the design meanwhile. I left out LED BPM display from the CS PCB, but kept pin connector if somebody still like to add it in integrated designs like TR-9090. There is a DOG LCD on it`s place now. Even I wanted to make it clean and simple it will be really hard to navigate trough all the functions without proper panel labels. Main reason I decided to use DOG LCD, is because of its very small size and low profile. It fits nicely with minor controls rearrangement without cutting the PCB. Even it is not so easily awailable, especially from where I live, i feel that DOG is a way to go for this design. Distance between PCBs are grown back to 20mm, and that is about all for now. I`ll let you know the news. Here is the splash of the arrangement.