c0nb0x

[realeoin]

Hi. thanks for replies. sorry was out of contact there for a few days. just tried all this again.
Gonna apologize beforehand for the big post and all the caps but i thought maybe you might see something i'm missing.

I'm not running any other applications while i'm doing this.
i've tried all this with a different cables and different ports
i have yet to try it with another pc but here's what i get shown in a few screen caps

*do note that i was running sokkos 1.9 prior to this and it was working fine.
**i was also able to use computer control mode with c0nb0x

1. power on x0x in bootload
2. open c0nb0x and device manager - make sure all ports etc are correct
3. all good so far. settings checked ready to go
4. run diagnostics mode and get this


5. if i then try connect to x0xb0x i get this


6. now if i try and upload a firmware after all this, i cannot. i get this


7. however, if i shut everything down and restart x0x in bootload, load c0nb0x and run through the firmware upload nice and quick it works fine and i get this. looks good...


8. firmware uploads successfully. i get this


9. switch off x0x. change to any regular operational mode and nothing works. no sound. no sequencer. looks like still stuck in bootload mode. (some/none/all of LEDs come on each time i power on)

10. back to bootload mode. open c0nb0x. connect to x0x. get this


11. if i try computer control for import/export i get this


Anyways, while I am familiar enough with computers and and software and stuff, I don't know much about coding or electronics so I fear what that what I may need to do to fix this might go a bit over my head. If worst comes to the worst there is a guy in my city that should be able to get it up and running. Would be nice to sort it from home though.

Any suggestions/ideas welcome.

Cheers

[antto]

you are confusing two things:

only "Upload firmware" is what you need the bootloader for
in all other cases, you shouldn't be in BOOTLOAD mode

for "Computer Control" as well as Diagnostics** mode - the x0xb0x should be running the firmware, not the bootloader
if you still find this confusing - watch the tutorial video about uploading firmware, the link is somewhere on the first page of this thread

** this feature basically doesn't work because i haven't released that special firmware, so don't bother trying it, it will never connect

so, you can see you get a few Err packets which means that the x0x is there and responds, but it's in bootload mode and the data it receives is unexpected (c0nb0x is trying to talk to the firmware)

the fact that you can flash firmware means that the bootloader is there

restart the x0x in any mode and try to connect via "Computer Control"
- if it fails to connect and you see Err packets happening like in your later screenshots - this means the x0x is replying to the data but in a weird way which either means there's something wrong with the data happening or it's in BOOTLOAD mode again? while it shouldn't be
- if it fails to connect and you don't see Err packets or any other stuff (all 3 numbers there would be zero) - this means the x0x doesn't respond at all for some reason (or no data arrives at all, not even wrong data)

if you manage to get it to connect properly, try to extract the eeprom a few times to see if you get lots or Err or bad CRC packets
if you do get CRC errors - it's what i suspected, the connection is "flakey" for some reason, packets tend to get corrupted too often
that would explain why flashing firmware works "sometimes"

i hope this helps

[realeoin]

hi thanks again for help.

my mistake. although i am aware that the bootload mode is firmware and computer control is for memory and patterns import export. i've been using it for storing patterns right up until i decided to update my firmware

here's rundown of the issues i'm having
prior to updating the firmware i was using computer control mode just fine for import/export of patterns
but i could not get new firmware to upload. eventually i did get the firmware to upload (by doing it quickly)
but now nothing works and my x0x does not work in any mode (whether connected to my computer or not)

now when connected in computer control mode, first i get the Ping.. BAD message
then i have to skip the fw detection and bpm bit to get to import/export page

when i export memory/patterns i get this "unexpected packet" error like this


this eventually times out and i get this


i've tried all sorts of permutations of all kinds
not sure where to go from here

[antto]

well if the firmware is not working, you cannot test this

try to flash a firmware and get the firmware to run
then do this test with the pattern export to see if you get CRC errors

meanwhile, open the properties of the "USB Serial" driver and make screenshots of the "Port Settings" page and the other page which opens up when you click "Advanced.."

[mario1089]

ähem, antto can you clarify: I stored my patterns a couple of times using conbox, and that looked very much like working (though never tried putting them back, as a relied on your app), but I have not been in computer-control mode! Just did it from some other mode. So then, when looking for bytes, I removed some code from FUNC_COMPUTER_CONTROL (or how its called), something like while(1) { readswitches() }; not much more. I could not see a reason for this mode, as conbox did anything I wanted without. So what`s the story?

- Thanx one more time and in advance for your answers:)

Mario

[realeoin]

hmmm..

i cannot get the firmware to run for any tests. at the moment the only thing that works is the flash firmware function. when this completes though the x0x is useless. like it is stuck permanently in bootload mode. my usb settings are correct as far as i can tell. the only thing i changed was the baud rate to match what is given in c0nb0x. here is a screen cap

[antto]

ähem, antto can you clarify: I stored my patterns a couple of times using conbox, and that looked very much like working (though never tried putting them back, as a relied on your app), but I have not been in computer-control mode! Just did it from some other mode. So then, when looking for bytes, I removed some code from FUNC_COMPUTER_CONTROL (or how its called), something like while(1) { readswitches() }; not much more. I could not see a reason for this mode, as conbox did anything I wanted without. So what`s the story?

- Thanx one more time and in advance for your answers:)

Mario

the important part is the message processing code which happens on interrupt
the actual menu do_computer_control() is practically empty, it only checks if you change to any other mode and exits

the purpose of do_computer_control() was probably, to have most of those features that haven't been implemented (remember those messages i mentioned)
but, as you can see, it's empty

there is basically messages for reading and writing patterns, changing the tempo, and these work from any Mode because they are processed on interrupt
i do not recommend importing and exporting patterns during live performance, as they can interrupt the x0x timing

[antto]

realeoin: your settings are correct, even that they shouldn't matter
so, i really don't know what to say

[realeoin]

not to worry. thanks for help. i give up on it.
a lad i know says he can program me a new chip.
should do the job.

[antto]

i hope that fixes it

[noha]

realeoin, were you able to resolve this issue?

my x0xb0x is displaying basically the exact symptoms you mention, down to the letter.
i was able to flash the firmware once after about 3 tries, but the x0xb0x was still stuck in the bootloader setting (random LEDs on, unresponsive to button presses) when i turned it off and switched it to other modes.
subsequent attempts to burn the firmware are not able to get the DeviceID string.
i'm assuming that since I was able to upload the firmware at least once successfully that I have a bootloader on my chip (this x0xb0x is one of the original ladyada kits, #139 or something), but since it seems pretty unresponsive to these various actions is the solution to just get another microcontroller chip? or can this one be saved somehow with the right software interface?

i'm using c0nb0x on OS X 10.8.2

thanks any and all for your help.

[antto]

if there was a bootloader at first, and then after an attempt to flash a firmware something went wrong and neither a firmware is present nor the bootloader seems to be responding (aka you get those same errors) .. then..

..i can think of one explanation.. in theory, it *might* be data being corrupted during firmware upload, since there is absolutely no error checking (that's because of the bootloader, i cannot change that from the app itself)
could be some byte going wrong and somehow resulting in corruption of the bootloader sector

that theory applies only if my suspection about all x0x CPUs being with unprotected bootloader sections is true, because otherwise it won't happen

also, as a last hope (it probably ain't gonna work but it won't hurt to try) .. since i am not good with electronics, but just guessing, could be the x0x not really getting into bootload mode for some reason.. if there is still power to the CPU or something
so, maybe try switching the x0x OFF (leaving it with the FUNC switch pointing at BOOTLOAD) for a long time - 1 minute, 10 minutes, i don't know.. (so that such theoretical charge goes away and hopefully the CPU really goes OFF)
then switch it ON and try to upload firmware, see if you'll get response from the bootloader
(i am really shooting in the dark with this)

[antto]

otherwise, the cure would be either re-programming the bootloader back onto the CPU (if you can find someone who has such a programmer device..) or buy a new CPU with pre-programmed bootloader

[danhillwwr]

Hi, I download c0nb0x V 1.00 (MACOSX) it does not work on 10.6.8 ! After two days of hard work, I download c0nb0x 0.99 mac osx and miraculously I had a sign, it work well with snow leopard Thank you for this work. PS: sorry for my English rotten

[antto]

Hi, I download c0nb0x V 1.00 (MACOSX) it does not work on 10.6.8 ! After two days of hard work, I download c0nb0x 0.99 mac osx and miraculously I had a sign, it work well with snow leopard Thank you for this work. PS: sorry for my English rotten

hi, you shouldn't use v0.99, especially if you will be working on experimental firmwares (v0.99 has a bug which can potentially overwrite the bootloader if you try to upload a big enough .hex file)

for what reason did v1.00 not work?
did the app not start at all, or you just couldn't connect it to the x0x?