c0nb0x

[antto]

first post updated with the links
v1.00 is out

-bugfix- non-working protection from too-large .hex files, making it possible
to erase the bootloader, ouch
-bugfix- .hex file size being printed with 1 byte less, and thus Remaining
flash space being printed with 1 byte more
-bugfix- old .xbp files not loading correctly
-bugfix- some minor typos corrected
-new- serial port auto-detection on Windows as well
-new- PatternEditor now has hotkeys for writing pitch and time directly
the keys are configurable through the .cfg file, defaults to QWERTY
setup. The old hotkeys SHIFT+U/D/A/S have been removed
-new- PatternEditor automatically Load/Save on bank/slot change / pattern
modification
-new- PatternEditor Manipulators added - shift reorder and "303ify"

[mario1089]

If antto shares the code, I'd put the randomizer into conbox, with a more handy UI (the randomizer, not conbox!) possibly and even more options. Would be fun..

[mario1089]

@roxxx303: If you like randomizers and want enthusiams, I`d say it`s just the right point to re-think your fear about "messing up your xoxbox". Thousands of user have successfully uploaded firmware. I mean propably your TV or iPhone or printer is currently uploading a new firmware:) But for the xoxbox, you can choose and downgrade if you don`t like what`s happening. The greatest risk is you don`t get it done, well, then, fine, nothing has happened. There is NO risc you get something done, but messed your xox (at least not with conbox1.0). And even if, you go back to your sokkOS. Also, if having trouble, the forum helps..

As for me: I have the box since a month or so, I`m on win7. I did not install any drivers as far as I remember, just plugged the box. I did not change any settings anywhere, nothing. Plugged it in, started conbox, uploaded firmware. "Easy-As-Apple".

So, now have fun randomizing! And let me know what you think - the algorithms are highly adjustable, it`s easy to add something that serves your needs/loves, if you want. It`s fun for me to work with someone that loved to work the "Battteries-Off-Way".

[antto]

i already have a randomizer coded into c0nb0x (tho, it's not in v1.00)
CTRL+8 - randomize TM
CTRL+9 - randomize PM

my internet connection is pretty broken, so reuploading ~1.3MB is a very tough job (it took me like 4 hours now)
and don't forget that i rely on another person for the mac-osx version, both for compiling and testing
fortunately, OS-dependant stuff hasn't changed since v0.99 thus there wasn't any huge need for testing

i want to see if there are any other issues with this version
like if anything bothers you - just shout

i also want to see what's new around the CPU mod, since that can affect the future of c0nb0x
for those who haven't read - i wanted to change the serial protocol because there are some unneded things, like packet format having uint16_t size while the maximum size of a packet cannot be bigger than the uart buffer which is already defined as 64 bytes
removing 1 byte from the packet (making the size simply uint8_t) and thus removing the small integer math involved in converting it would free up some tiny fraction of code space
i wanted to put these changes in the current OSes (adafruit 1.05, n0nx0x and sokkos) but i didn't really get any response from sokkan and maybe that's right - such modification would make the current OSes completely incompatible with c0ntr0l (only firmware will be still flashable)

but such serial protocol modification can be implemented perfectly in the brand-new upgraded-cpu firmware
since c0ntr0l already won't be compatible with it (i think)
then, this can be used as the foundation firmware for all others
this would be doable because the new CPU has 256kB flash, that's much much more than the original x0x cpu

but let's see if the CPU mod *really* is a fact

[darffader]

Small note for users of OSX 10.8 Mountain Lion
When opening the program for the first time you may get a notice about the need to install X11
This is perfectly normal since Apple doesn't ship X11 window system with OSX any more.
You'll need XQuartz, which is just a free (and safe) download away, so click continue in the prompt or visit http://xquartz.macosforge.org directly

The app is compiled in OSX 10.7 and it has been made to work in earlier versions starting from 10.4 (Intel). This has NOT been tested this because no macs running 10.4/10.5/10.6 are around.. If it works fine in any of those systems, please report back here!

[realeoin]

hi
big help needed
i'm having all the exact same problems gompie was having right down to a t
i'm using c0nb0x and attempting to flash new firmware
i was running sokkos 1.9 prior to even trying this at all and all functions were fine
i'm using win 7 64bit
after trying like 20 times i eventually got firmware to upload and all done fine...
oddly enough i can only get it to work just like he did by working quickly, ie power on in bootload--->straight to upload firmware

but now x0x is stuck in perma-bootload mode - none of the modes work and some/none/all of the lights come on when powered on
needless to say it makes no sound either
i usually have the x0x din synced (as slave) to my 606 which oddly enough wont operate unless sync cable is unplugged now
i've tried flashing a few different firmwares countless times now to no avail - perma bootload/crash mode is all i get
Please help - been looking forward to trying this
Cheers


might be worth noting that prior to this computer control mode was working fine also
now i get timeout errors trying to import/export eep and patterns

[antto]

what does c0nb0x say exactly, and did you use c0nb0x v0.99 or v1.0?

were you able to "Connect to x0xb0x" when the firmware still worked? or did you get similar (unresponsive) symptoms as gompie?

[realeoin]

hi cheers for quick reply
using v1.0
was having exactly same issues as gompie
same screen caps he posted back a few pages ago. all the things he described except on win 7
at moment i can still upload firmwares successfully if i move fast, but then i switch off x0x, change modes, remove usb, power on
and i am stuck in boot/crash mode in every mode

[realeoin]

sorry
yeah directly after succesful firmware uppdate, if i sswitch to connect to x0xb0x i get
Opening serial port success
Ping Bad
Firmware version....
so i skip this and get
???unknown FW
V1.05
Detecting pattern size... Failed
Get tempo... using default: 120 (in red text)

same thing in diagnostics mode

also cannot import/export in computer control mode any longer

[antto]

already with "Ping Bad" it means that there's something wrong
and the following tests confirm that

so it sometimes works, sometimes not?
that's odd

are you using some extremely long or bad USB cable?
i'm not sure how to help if it's something to do with the hardware

but if you manage to upload firmware sucessifully - that means that there is a bootloader
why it works *sometimes* is a different question

oh, i got an idea.. when you "Connect to x0xb0x" and all tests fail, when you get to the actual menu, check the connection status
it should show something like [Rcv:Err:CRC: X / Y / Z]
with 3 numbers, number of packets received, number of errors, and number of bad CRC packets
tell me what it prints there immediately when you see it

[mario1089]

Don`t know if this helps but some experiences I have made:

1) I have seen many times (maybe 5% of all uploads) that the firmware is partly broken after upload. Uploading again always helped, but: it`s definitely a matter of what else the computer is doing. When a audio DAW is running at the same time at 40% CPU load, actaully NO upload will ever be working on my system. So make sure you close other applications. I have not seen in any case, that this would overwrite the bootloader part (unless the hex is too big, and you run conbox0.99), so I would not worry too much now:)

2) My power supply is a little weak, so after turning on the box, it is sometimes not feeling quite well. Normally this seems to be indicated by many LED turned on. So I turn on and off a couple of times, until it looks ok.

[antto]

when i was "brewing" the serial port code, i noticed that i get bad bytes from time to time
my x0x powersupply is 600mA and i have normal red-leds (sanely bright)

this happens at all times, doesn't matter if you're sending a hex or extracting patterns

but when extracting patterns, or in other words, when the x0x is running the firmware - there is a CRC check on each packet at all times, and c0nb0x checks that, and automatically retries when a CRC error happens during pattern extraction

unfortunately, there is no CRC nor any other error checking during hex upload
that's how the bootloader works and i cannot change it

RS232 is also sensitive to timing, try and set the Baud rate to something slightly lower or higher than what it should be, and you'll start to get more and more bad bytes

[mario1089]

I know you`re on win, and me too, so from what I saw here, I`d say the app should get a better threading priority. Here it`s set to "normal", but when doing things that critical it should clearly be set to "realtime". No idea how to that, though.

[antto]

it's the OS which does the actual RS232 stuff, which itself is virtual, the USB-Serial driver is what actually sends the data
i cannot do much from the app
and i don't think chaging it's process priority would help

[mario1089]

makes sense.