--- In bc2000@yahoogroups.com, "matschdreck" <matschdreck@...> wrote:
> yes, the upload procedure was interrupted. Unfortunately, i was to
> anxiuos to finish, and didn´t memorize the error prompt that occured.
> But the prompt told, that if i start the BCR again, it will just
> continue to work with the old firmware again, so i didn´t worry.
First some background explanation:
When you switch the BCR on, the BCR first checks whether the firmware on its EEPROM chip is valid, by means of a checksum.
If the firmware checksum is correct, the BCR copies the firmware from its EEPROM chip to its RAM, and then starts running from the RAM copy.
However, if the checksum is INcorrect, the BCR ignores the EEPROM firmware and enters the very basic "noOS" mode: of course this is typically the case if the previous upload procedure was interrupted, because the EEPROM firmware then consists of two unmatched parts (new + old).
So after a partial firmware upload, the BCR only keeps working with the old firmware (i.e. the RAM copy!) as long as you don't switch it off. (This is particularly relevant for the USB code.)
So what you could have tried (after the error message) was to repeat the uploading procedure BEFORE switching the BCR off (or meddling with the Windows USB driver software).
> I also watched the BCR during the upload procedure,
> and i could see the display somehow counting up, 1 -> 2 -> 3... etc,
> and when it came to 5, thats where the error prompt came. BC Manager
> also told me to look at the BCR Manual, and solve the problem before
> trying again, but i didn´t even understand the problem. I wonder if
> this information is helpful at all.
The number should run from 2 to 17. I have no idea where the error came from.
> I guess i will have to do this with a different computer. I dont have
> a MIDI connection, just laptop with usb. But i know a friend. Is
> there something i should be aware of, uploading this way?
In general there are 2 firmware upload methods:
A. Bidirectional.
This is what BC Manager's "Send firmware" routine does. In this case you'll need to connect the sound card to the BCR's "MIDI IN" and "MIDI OUT A" ("MIDI OUT B" is completely dysfunctional).
B. Unidirectional.
You can use any computer program capable of opening the firmware syx file and sending it via MIDI. So e.g. BC Manager, MIDI-OX, or even "MIDI Tools" (also downloadable from mntn-utils.110mb.com - once it's back on air...). Obviously, in this case you only need to connect to the BCR's "MIDI IN".
E.g. in BC Manager and MIDI Tools:
1. Open the MIDI System Exclusive messages window via the main window's View -> MIDI -> System Exclusive messages.
2. Open bcr2000_1-10.syx by executing File -> Insert.
3. Execute Edit -> Select all.
4. Execute Play.
I suggest you first try method A. If that somehow still fails, try method B.
Good luck!
Mark.Message
Re: "noOS"
2009-06-18 by Mark van den Berg
Attachments
- No local attachments were found for this message.