Skip to main content ↑ ↓
Topic: BPv3a BootLoader v4.2 upgrade problem (Read 6513 times) previous topic - next topic

BPv3a BootLoader v4.2 upgrade problem

I had just upgraded to bootloader v4.1 and also flashed in the firmware v4.1.

Firmware v4.1 works on the terminal so far.

However, later I tried to flash in bootloader v4.2 using ds30 loader. It was unsuccessful with a message of "Nothing to do". Reflashing in the firmware v4.1 also ives me the same result.

Any suggestion to solve for this?

Re: BPv3a BootLoader v4.2 upgrade problem

Reply #1 –
Hi haley0918,

That's completely normal. V4.1 is the v4 upgrade utility for the v2 bootloader. v4.2 is a v4 bootloader that you program into the chip with a PIC programmer. They're exactly the same except for the version number and how you load them. I gave them a different number so I know at a glance how a Bus Pirate go the v4 bootloader when I get support requests.
Got a question? Please ask in the forum for the fastest answers.

Re: BPv3a BootLoader v4.2 upgrade problem

Reply #2 –
Thanks for reply!

I'd also found that I can't load the other firmwares such as the OpenOCD and the STK500.

The ds30 loader can find the bootloader upon first plugin but timeout at the second scan. Whenever I want to load another hex file into the BPv3a the application just pops out a message saying "Nothing to do".

Re: BPv3a BootLoader v4.2 upgrade problem

Reply #3 –
You only get once chance to connect. After checking for the bootloader it has to be reset before you can connect again. This will be improved in a future update, but now it is the correct and intended behavior.

How are you running the ds30 Loader? It requires the settings.xml file to be present in the same folder for proper configuration. Is the 'write program' box checked? I believe that error only happens when write program is unchecked.
Got a question? Please ask in the forum for the fastest answers.

Re: BPv3a BootLoader v4.2 upgrade problem

Reply #4 –
Is it normal that the new firmware will light up the MODE and VREG leds if there's no terminal connection to it after some time?

Also when loading the bootloader from the firmware by terminal, once the terminal disconnects, the bootloader also went off after a fraction of a second. The time is too short for me to initiate the bootloader from the terminal and then move over to ds30 loader.

Re: BPv3a BootLoader v4.2 upgrade problem

Reply #5 –
No, the MODE and VREG LEDs should not light randomly.

The bootloader runs in a 10minute loop, it should not exit after a fraction of a second. What happens when you use a jumper instead of the terminal entry?

What version of the Bus Pirate are you using? When was it purchased?
Got a question? Please ask in the forum for the fastest answers.

Re: BPv3a BootLoader v4.2 upgrade problem

Reply #6 –
My version of Bus Pirate is v3a bought at SeeedStudio last month. In the Pre-order 3 batch.

Currently using bootloader v4.1 and firmware v4.1, upgraded by following instructions in the article.

When using the jumper at PGD and PGC, with no application connecting to it after physical USB connection, it seems to enter bootloader with the MODE led turned on for only 5 seconds.  With ds30 loader connecting to it for bootloader check, the MODE led lighted up continuously.

To continue from the MODE led turned off after 5 seconds without anything connecting to it, 15 seconds later the MODE led lighted up again followed by VREG led and there's also some blinks on the USB led indicating some activities going on.

Re: BPv3a BootLoader v4.2 upgrade problem

Reply #7 –
The only think I can think of is that trying to update to v4.2 might have caused a problem with some settings. It shouldn't though.

Did you test the Bus Pirate prior to upgrade?

If possible, could you please try to bootload the attached updater using the ds30 Loader. Run it like the v2 to v4 updater (open terminal, type yes). It will refresh the v4.1 bootloader to the default state.
Got a question? Please ask in the forum for the fastest answers.

Re: BPv3a BootLoader v4.2 upgrade problem

Reply #8 –
Everything was good before upgrade.

The ds30 loader could load BPv3-v2blupdaterVa3-v4.1.hex but without the write program checked so I can't get the updater into the BP hardware.

Re: BPv3a BootLoader v4.2 upgrade problem

Reply #9 –
I had the bootloader v4.1 updater loaded in using the pirate-loader.exe and executed the update in terminal.

Now the problem seems refined without the firmware.

With PGC and PGD connected and no application connecting to it, the MODE led lighted up for 5 seconds and turns off with the USB led blinking at the rate of about 1 second. 15 seconds later the MODE and VREG didn't light up as I'm suppose because I didn't load in the firmware.

Re: BPv3a BootLoader v4.2 upgrade problem

Reply #10 –
The ds30 Loader could never load the v2blupdaterva3-41,hex, it is loaded with the p24qp.exe program only. It gives an error in the output box because it contains code that would overwrite the bootloader (though the bootloader won't let that happen). Do you get that error?

Quote
The ds30 loader could load BPv3-v2blupdaterVa3-v4.1.hex but without the write program checked so I can't get the updater into the BP hardware.

When did this happen? I don;t understand what you mean.
Got a question? Please ask in the forum for the fastest answers.

Re: BPv3a BootLoader v4.2 upgrade problem

Reply #11 –
Quote
I had the bootloader v4.1 updater loaded in using the pirate-loader.exe and executed the update in terminal.

Which .hex file did you load with pirate-loader.exe? The v4.1refresh.hex I posted, or the original v2blupdaterva3-41.hex?

Quote
Now the problem seems refined without the firmware.
With PGC and PGD connected and no application connecting to it, the MODE led lighted up for 5 seconds and turns off with the USB led blinking at the rate of about 1 second. 15 seconds later the MODE and VREG didn't light up as I'm suppose because I didn't load in the firmware.

It sounds really messed up, there's no scenario where that should happen.
Got a question? Please ask in the forum for the fastest answers.

Re: BPv3a BootLoader v4.2 upgrade problem

Reply #12 –
Sorry for the mess. I overlooked the zip file you posted.

Now I had downloaded the 4.1refresh.hex into BP using ds30 loader and ran it in terminal. The same symptom still there.

Re: BPv3a BootLoader v4.2 upgrade problem

Reply #13 –
Were you able to run the 4.1refrech.hex file? Did you see the output in the terminal, type yes, and the upgrade completed. It said "success" at the end?
Got a question? Please ask in the forum for the fastest answers.

Re: BPv3a BootLoader v4.2 upgrade problem

Reply #14 –
Yes the upgrade was a success. Now the bootloader seems fine and doesn't go off after 5 seconds.

Also downloaded the v4.1 firmware and all just look fine right now. It doesn't light up the MODE and VREG leds anymore after 15 seconds without any application software connection.

Thanks Ian!