Displays 17 after firmware update

3 posts / 0 new
Last post
Wedge-destroyer
Wedge-destroyer's picture
Displays 17 after firmware update

So I got a bcr2000 for free from the owner of an AV company, it sends no0S signal. So I download the editor and patch everything up via midi with two good cables. It talks to the editor, and sends the file but after completing the transfer the screen on the BCR just reads 17. I've tried closing down the editor before power cycle (incase it was a U setting), and it comes back noOS. I've power cycled with the editor open, same results. I've tried every button on it prior to power cycle to see if that helps. 

Anybody have a clue or do I have a fancy new paperweight?

 

Thanks 

Chris

Mark van den Berg
Mark van den Berg's picture

First some background information that might help:

  • "BC Manager Manual.pdf" section 10 "The B-Controls window", "MIDI -> Maintenance -> Send firmware" (currently pp. 59-60)
  • "BC MIDI Implementation.pdf" section 22.1 "Bootloader mode" (currently p. 138)

So I download the editor and patch everything up via midi with two good cables.

Just to be clear: you've used BC Manager's (bi-directional) "Send firmware" operation?
(Incidentally: on which operating system? Windows or macOS?)

after completing the transfer the screen on the BCR just reads 17

The BCR's firmware consists of 64 KiB. This is sent in 16 segments of 4 KiB each. Each segment is sent as 16 MIDI System Exclusive messages, each containing 256 firmware bytes.
When the BCR has received the 16th SysEx message of a segment, the BCR returns a "Firmware Reply" SysEx message indicating either success or failure. (Furthermore, in case of failure the BCR's display briefly shows "Err5". Did you ever see that?)
After receiving a segment, the BCR's display shows the number of that segment. Since the (always-present) bootloader code on the BCR's EEPROM chip occupies segments 0 and 1, the first firmware segment has number 2, and the last firmware segment has number 17. So it's perfectly normal that at the end of the "Send firmware" operation the BCR's display shows "17".

I've tried closing down the editor before power cycle (incase it was a U setting)

Since your BCR is in bootloader mode ("noOS"), it isn't in any U or S operating mode: these modes are only defined if the BCR's "full" operating system is running, which can't be the case until you've switched the BCR off, then on again.
So it's totally irrelevant whether you terminate BC Manager before switching the BCR off and on again.

Whenever the BCR is switched on, its bootloader code (on its EEPROM chip) first checks whether the firmware (also on its EEPROM chip) is correct (specifically: whether the firmware matches a stored checksum). If the firmware is not correct, the BCR's display shows the infamous "noOS". If the firmware is correct, the BCR copies the firmware from the EEPROM chip to its RAM chip, then transfers control to that copy in RAM: only then is the "full" operating system running.
So that's why you always need to restart the BCR after uploading firmware to it.

I've tried every button on it prior to power cycle to see if that helps.

Don't bother: all the BCR's buttons (and encoders) are dead in noOS mode.

As far as I know, BC Manager's bi-directional "Send firmware" operation should work when the BCR is in noOS mode.
However, in theory your (USB-to-)MIDI interface might exhibit "MIDI Thru": in that case the Firmware Reply messages sent by the BCR are sent back to the BCR, and this might mess up the firmware upload process.
So you might try to upload the firmware unidirectionally:

  1. Remove the cable connected to the BCR's MIDI OUT A socket. (This ensures that your MIDI interface won't cause any MIDI Thru effects.)
  2. From BC Manager's main window, open the "System Exclusive messages" window via View -> MIDI.
  3. Load the BCR's firmware file (bcr2000_1-10.syx) via File -> Insert.
  4. Select (highlight) all (256) messages (e.g. via Edit -> Select all).
  5. Select the correct "Output device".
  6. The default "Delay/message" setting of 100 msec should probably work, but to be on the safe side you might want to raise it to 200 msec or so.
  7. Send the selected messages to the BCR by pressing the Play button.
  8. Watch how the BCR's display reacts during the transfer. (For one thing, it should never say "Err5".)
  9. When the BCR's display has settled at "17", switch off the BCR, then on again: hopefully the display no longer shows "noOS".

If this doesn't work either, there might be a hardware fault in your EEPROM chip. (The fact that your BCR displays "noOS" proves that at least the bootloader section of the EEPROM chip is working correctly. But of course the hardware fault might be restricted to the firmware section.)

Hope this helps,
   Mark.

Wedge-destroyer
Wedge-destroyer's picture

Im using windows 10, all midi is routed through a presonus audiobox, i reviewed the manuals last night while working with it. So far ive tried the BC editor, as well as Behringers (even through reports say it doesnt work). Ive tried the BC, Bome, and SysEx!, to send it via sysex and have attempted all three with and without Midi A connected. 

I have watched in each case, there was no errors from the BCR at all. Just ticks along until 17, I power cycle and noOS everytime. Regardless of if it is in noOS or Load settings. 

I decided at one point to look inside every thing appeared shipshape. Of interesting note is the chip it self has s sticker v1.10 on it.

So it may be the eprom itself, now to find a burner or someone with one i guess.

Thanks for the help

Chris