|
Hi Folks,
?
搁别苍é, as usual, has been busy with Gemini improvements. The new Bootloader is an update to the original one that was created when 2GB SD cards were all that was available :)
?
The new bootloader isn't required if your Gemini is working fine. You can skip it if you don't care about the benefits listed below, or if you feel uncomfortable performing the update.
?
The update process itself is about as complicated as the L6 upgrade to the new servo firmware, and requires:
?
- A 20 pin ULINK2 emulator/programmer -- about $30 from Amazon
- Keil ULink-2 software (runs on Windows)
- MB_BL_2024.uvproj bootloader project file
?
Detailed Instructions can be found here:
?
The new bootloader is based on a modern version of Keil middleware and helps with the following:
- Faster boot-up time for Gemini
- Better compatibility with different types and larger size SD cards
- Resolves the issue with the dreaded M:Curr_Gem.bin file for those who have experienced it
?
Be careful if you decide to update your Gemini. Follow instructions!
?
Regards,
?
? ? -Paul
?
|
|
|
Big thanks to 搁别苍é, Paul, David and all the Gemini team for providing such support to the system. I have not encountered the M: file issue, and do not know what this issue is, may be because my Gemini II is still on L6.02, thus in principle I should stay away from this. The computer engineer inside me however is curious about the update process. Can this update be fatal and the Gemini II be bricked if not performed exactly or if power fails during the process ?? When you use a JTAG connector is because easier software based firmware updates have failed so, I think that even if the Gemini II gets bricked it could be recovered using a JTAG programmer (much as it happens when programming a FPGA), but I am not sure if this is the case.
?
Regards,
Daniel??
|
On Mon, Apr 7, 2025 at 07:36 PM, Daniel wrote:
Big thanks to 搁别苍é, Paul, David and all the Gemini team for providing such support to the system. I have not encountered the M: file issue, and do not know what this issue is, may be because my Gemini II is still on L6.02, thus in principle I should stay away from this. The computer engineer inside me however is curious about the update process. Can this update be fatal and the Gemini II be bricked if not performed exactly or if power fails during the process ?? When you use a JTAG connector is because easier software based firmware updates have failed so, I think that even if the Gemini II gets bricked it could be recovered using a JTAG programmer (much as it happens when programming a FPGA), but I am not sure if this is the case.
I doubt you could brick a Gemini by bad or interrupted programming. I assume it's possible if you don't align the connector pins the right way. If you do connect it correctly, you should be able to reprogram the bootloader even after a failed attempt. I updated three Gemini units this way, and one had a corrupted bootloader when it was sent to me and would not start. The reprogramming fixed it right up.?
?
|
Can someone share a link to the exact programming device needed??
I went to Amazon just now, and it was far from obvious.
On 2025-04-07 17:31, Paul Kanevsky
wrote:
Hi Folks,
?
搁别苍é, as usual, has been busy with Gemini improvements. The
new Bootloader is an update to the original one that was created
when 2GB SD cards were all that was available :)
?
The new bootloader isn't required if your Gemini is working
fine. You can skip it if you don't care about the benefits
listed below, or if you feel uncomfortable performing the
update.
?
The update process itself is about as complicated as the L6
upgrade to the new servo firmware, and requires:
?
- A 20 pin ULINK2 emulator/programmer -- about $30 from Amazon
- Keil ULink-2 software (runs on Windows)
- MB_BL_2024.uvproj bootloader project file
?
Detailed Instructions can be found here:
?
The new bootloader is based on a modern version of Keil
middleware and helps with the following:
- Faster boot-up time for Gemini
- Better compatibility with different types and larger size SD
cards
- Resolves the issue with the dreaded M:Curr_Gem.bin
file for those who have experienced it
?
Be careful if you decide to update your Gemini. Follow
instructions!
?
Regards,
?
? ? -Paul
?
--
Michael A. Covington, Ph.D.
Consultant, Covington Innovations, Athens, Georgia, USA
|
Everything, including the Amazon link, is in the instructions. Here’s the link:
?
ULINK2 Emulator Original Firmware Support for MDK5.0 Cortex M4 Gold Plating 11 x 5.5cm
?
On Mon, Apr 7, 2025 at 11:16 PM, Michael A. Covington wrote:
Can someone share a link to the exact programming device needed?? I went to Amazon just now, and it was far from obvious.
?
On 2025-04-07 17:31, Paul Kanevsky wrote:
Hi Folks,
?
搁别苍é, as usual, has been busy with Gemini improvements. The new Bootloader is an update to the original one that was created when 2GB SD cards were all that was available :)
?
The new bootloader isn't required if your Gemini is working fine. You can skip it if you don't care about the benefits listed below, or if you feel uncomfortable performing the update.
?
The update process itself is about as complicated as the L6 upgrade to the new servo firmware, and requires:
?
- A 20 pin ULINK2 emulator/programmer -- about $30 from Amazon
- Keil ULink-2 software (runs on Windows)
- MB_BL_2024.uvproj bootloader project file
?
Detailed Instructions can be found here:
?
The new bootloader is based on a modern version of Keil middleware and helps with the following:
- Faster boot-up time for Gemini
- Better compatibility with different types and larger size SD cards
- Resolves the issue with the dreaded M:Curr_Gem.bin file for those who have experienced it
?
Be careful if you decide to update your Gemini. Follow instructions!
?
Regards,
?
? ? -Paul
?
--
Michael A. Covington, Ph.D.
Consultant, Covington Innovations, Athens, Georgia, USA
|
Thanks!
On 2025-04-07 23:32, Paul Kanevsky
wrote:
toggle quoted message
Show quoted text
Everything, including the Amazon link, is in the
instructions. Here’s the link:
?
ULINK2 Emulator Original Firmware Support for MDK5.0 Cortex
M4 Gold Plating 11 x 5.5cm
?
?
Detailed Instructions can be found here:
?
|
I doubt you could brick a Gemini by bad or interrupted programming. I assume it's possible if you don't align the connector pins the right way. If you do connect it correctly, you should be able to reprogram the bootloader even after a failed attempt. I updated three Gemini units this way, and one had a corrupted bootloader when it was sent to me and would not start. The reprogramming fixed it right up.?
?
?
Thanks for your answer. In instructions it is specified that a microSD card higher than 8Gb is needed. I assume that this implies that the new bootloader do not work for smaller cards, including those delivered by the Gemini II. In this case is enough to just copy one card to the another using a PC ??? Furthermore, is there? any file format restriction to the larger microSD or can we use just a single partition FAT32 formatted?
?
Regards,
Daniel
?
|
Daniel,
The 8 GB was chosen by Tanya Kennelly since it works w/o any
problems for the new boards she upgraded. You can give your old SD
card a chance and report here.
Regards,
搁别苍é
Am 08.04.25 um 13:42 schrieb Daniel via
groups.io:
toggle quoted message
Show quoted text
I
doubt you could brick a Gemini by bad or interrupted
programming. I assume it's possible if you don't align the
connector pins the right way. If you do connect it
correctly, you should be able to reprogram the bootloader
even after a failed attempt. I updated three Gemini units
this way, and one had a corrupted bootloader when it was
sent to me and would not start. The reprogramming fixed it
right up.?
?
?
Thanks for your answer. In instructions it is specified that
a microSD card higher than 8Gb is needed. I assume that this
implies that the new bootloader do not work for smaller cards,
including those delivered by the Gemini II. In this case is
enough to just copy one card to the another using a PC ???
Furthermore, is there? any file format restriction to the larger
microSD or can we use just a single partition FAT32 formatted?
?
Regards,
Daniel
?
|
I am one of those people with the M:? file issue so I will definitely be doing this update.
?
Question-After updating the bootloader, do I just need to power up Gemini and then that M: file issue will resolve itself?
?
Already placed my Amazon order for the connector.
?
And again, thanks to all that provide ongoing support for Gemini.
?
?
Chris N
|
On Tue, Apr 8, 2025 at 08:29 AM, criscopenneys wrote:
Question-After updating the bootloader, do I just need to power up Gemini and then that M: file issue will resolve itself?
?
I know that the M: file will no longer be created by the firmware update process, but I don't know for sure if you'll be able to just delete it after the bootloader update (搁别苍é, do you know?)?
?
If you can't remove it, you may need to format the SD card, and then you can update it directly from GFU with all the files (or copy them to the card). After that one time, you should be able to flash new firmware without the M: file reappearing.
?
|
On Mon, Apr 7, 2025 at 02:31 PM, Paul Kanevsky wrote:
Hi Folks,
?
搁别苍é, as usual, has been busy with Gemini improvements. The new Bootloader is an update to the original one that was created when 2GB SD cards were all that was available :)
?
The new bootloader isn't required if your Gemini is working fine. You can skip it if you don't care about the benefits listed below, or if you feel uncomfortable performing the update.
?
The update process itself is about as complicated as the L6 upgrade to the new servo firmware, and requires:
?
- A 20 pin ULINK2 emulator/programmer -- about $30 from Amazon
- Keil ULink-2 software (runs on Windows)
- MB_BL_2024.uvproj bootloader project file
?
Detailed Instructions can be found here:
?
The new bootloader is based on a modern version of Keil middleware and helps with the following:
- Faster boot-up time for Gemini
- Better compatibility with different types and larger size SD cards
- Resolves the issue with the dreaded M:Curr_Gem.bin file for those who have experienced it
?
Be careful if you decide to update your Gemini. Follow instructions!
?
Regards,
?
? ? -Paul
?
?
My favorite little birdy told me about this a couple weeks ago.? I think it is worth doing if you are one of the impatient people or like me (okay so I'm impatient) just want to keep up to date on code revisions.? I'm a sucker for the latest and greatest LOL.?
?
--
Chip Louie Chief Daydreamer Imagination Hardware?
Astrospheric - South Pasadena, CA?
|
Thanks Gents
?
I have a G2 tallboy on the way...ARM is hot.?? So needs new ARM and i'll try the new bootloader.?? I'll report back....shouldn't be to long
?
cheers
--
Brendan
|
I have an update on the instructions provided.
?
I ordered the ULINK2 programmer and downloaded both software packages. ?Here is what I learned.
?
1. ?Failed the first time as the Keil link 2 software didn't download the legacy packages for the processor used in the G2. ?I was able to download the package as suggested by Keil so that was resolved.
2. ?I received the could not load file error message when doing the Flash and Download selections from the menu bar. ?See attached photo.
?
For reference I also ttached a photo of the ulink2 programmer attached with the G2 powered on.
?
Please let me know what you think is the next step.
?
Thank you.
?
?
?
?
|
Hi Don,
?
Check a few settings in Keil debugger:
?
1. Goto Flash->Configure Flash Tools... menu. Click on Device tab. Check that the correct device is selected: NXP/LPC2388/ARM
2. Then, inside the same window click Target tab. Check that ARM Compiler is selected as Compiler Version 5.
3. Go to Debug tab. Near the top, the second radio button Use: ULINK2/ME ARM Debugger should be selected
4. Under the same Debug tab, click Settings... button next to the "Use:" selection in step 3.
?
If your ULINK2 is connected to Gemini and Gemini is turned on, you should see the ULINK2 device name shown under JTAG Device Chain.
If it shows an error, you may not have a good connection. Check cable and pin alignment.
Try changing the max JTAG Clock on the same screen to 100KHz instead of 1MHz. Your goal is to see the ULINK2 device shown as connected. Then, you can proceed to Flash->Download
?
?
?
?
|
Hi Don
?
i looked at old boot loader and new one. ?This latest download appears to be missing some Kiel project support files. ?For example my old bootloader has the “BL_SD.axf” file it uses but the latest download doesn’t appear to have this. ? ?I think it’s missing …..but as I haven’t yet tried the new bootloader I may be wrong. ? ?I have done the old one quite a few times though.?
?
Not really sure. ?Rene’ and Paul are best to make the call on this.?
cheers
--
Brendan
|
Bren, I think you're right. The project file that Losmandy made available is just part of the package and is missing some extra files.
?
On Thu, Apr 10, 2025 at 07:15 PM, Brendan wrote:
Hi Don
?
i looked at old boot loader and new one. ?This latest download appears to be missing some Kiel project support files. ?For example my old bootloader has the “BL_SD.axf” file it uses but the latest download doesn’t appear to have this. ? ?I think it’s missing …..but as I haven’t yet tried the new bootloader I may be wrong. ? ?I have done the old one quite a few times though.?
?
Not really sure. ?Rene’ and Paul are best to make the call on this.?
cheers
--
Brendan
|
I was caught cross posting whips you were posting.?
Bbad internet juju!
?
cheers
--
Brendan
|
On Thu, Apr 10, 2025 at 07:43 PM, Brendan wrote:
I was caught cross posting whips you were posting.
?
Yes, there are a few files missing that should be included. The full bootloader was a compressed zip file with this project file and some additional files under the Objects folder. I asked 搁别苍é to send the complete file, and will post the update here as soon as I get it.
?
Don -- until then, please don't worry about trying all the settings I posted earlier: that's not going to help.
?
Regards,
?
? -Paul
|
In step 2, looks like the ARM compiler version 5 is missing.?
|
Paul Kanevsky
Ryan Noonan
Chip Louie
Don Klase
