We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.
I have a bootloader that update my firmware via USB.
The problem is that the current bootloader (or most) reset the uC after update.
I can't allow the uC to reset since the host application has a handle to the USB. I can release the handle and capture it again but preferably not. The other reason is, that this is a for product, and on USB release and connect, the PC (Windows) makes that sound that might confuse the product user.
I did post a similar message on Silabs forum since it is an Silabs device (although 8051) and USB related.
Is there anybody who would be so kind to help me with this problem please.
I will give more info, if necesarry.
Thnx in advance
at issue here is a number of factors a) the bootloadre will use much of the DATA segment, so restarting where you left off is impossible b) the bootloader will affect many SFRSs so restarting where you left off is impossible
It IS possible (someone did it for some chip using serial) to handcraft your own bootloader, but it is not a task you should take lightly
Why is it a problem that you must let the user know that an update "makes that sound". The user should know that updating is not 'normal operation'. I hope the user does not have to update on a regular basis.
Erik
As a user, I would expect to hear that sound if I update an USB device. If not, I would assume that something went wrong.
Why?
After an update, the hehaviour of the device might have changed. It might even report itself as something else. What chance would the PC software have to respond to the new firmware, if the PC doesn't make a reconnect?
All true
But the user doesn't know that a firmware update is taking place. He pressed a button on the host application and suddenly the PC generates a USB disconnect and connect sound.
So for us who know what is happening it is fine.
But for the guy who pressed the button and doesn't know, would wonder which USB device on his PC made that sound.
Understand the situation?
Are you saying that "I will not tell the idiot that pressing a button is to update the thingy. I will only tell the idiot to press a button. That what he is doing is a program update is no concern of his"? If that is true I am exteremely happy that I am not a customer of yours.
Neither I or the user will be an idiot, only the guy who press the update button is an idiot, becuase there is no update button. The button is not a function a firmware update but a function of selecting an algorithm.
The user doesn't have to know an update is taking place. He only needs to know wheter initializing the new algorithm was successful or not.
1) Then tell him that "initializing the new algorithm" will make a noise when done
What is so terribnle about that?
2) what is o terrible about the user knowing "update is taking place."
Thanks to all of you guys. I know have several opinions and it seems to be OK if the USB makes the connect/disconnect sound during firmware upgrade.
Although I would have preferred it without the sound but will accept the sound as part of the upgrade.
Cheers
MC