49 replies to this topic

[jbmaciel]

Hi all,

I was suggest by Frisk, I am starting a new thread about this issue.

I have this brand new Celestron telescope, Nexstar+ 6SE (USB), and I decide to update the firmware as I was recommended.

After running the CFM I've got this error (Update error 07-2023 1.bmp) saying the "Nexstar 6/8_AZM did not update sucessfully".

 

So I contacted the Celestron support and they sent me the following procedure:

********************************************************************************************************************************
Once you have the CFM software extracted and the driver installed, follow these steps:

1. Connect the hand control to the mount
2. Connect the hand control to the PC
3. Press and hold the Celestron logo button and the #7 while turning on the mount
4. Open CFM.jar
5. Wait for CFM to detect your devices or click on "Seek Devices"
6. Click NexStar+, then on Mount Types
7. Select the correct mount type (Alt-AZ or GEM)
8. Click on Seek devices
9. Click on update
10. Restart mount

If you receive any errors, attempt to perform an update again, but first remove CFM and its folders from your computer and attempt to perform an update using the BETA CFM, following the steps above, but instead of using the link to install the public CFM, please use the link below to install Beta CFM.

BETA CFM - http://software.cele...9.1085_beta.zip

If you continue to have issues with the beta, please remove BETA CFM and its files from your computer, reinstall the public version of CFM, and attempt the update again. If it fails this time, please provide screenshots from CFM showing the unsuccessful update.
********************************************************************************************************************************

I did the steps 1-10 with public CFM and I stiil getting the same error (Update error 07-2023 1.bmp).
So, I follow the same steps com the beta CFM and after a very brief message error saying corrupt file, it had shown that the update was successful.
But now the mount doesn't turn on, it looks dead.

The PC still recognize the "Prolific PL2303GL USB Serial COM Port", but there is no communication between the mount and the PC.

 

Then the technical support send this:

************************************************************************************************************************************
Please perform a factory reset. You can do this by holding down the 0 button while turning the mount on.
Next you will try to flash the firmware but first, close CFM, look in the folder where you unzipped CFM and delete the Packages folder. Now please start the update process again. Note it will take a few minutes for CFM to download all the packages via the Internet

************************************************************************************************************************************

 

But it didn't work, because the Nexstar+ is dead.

 

Does anyone has the firmware binaries dump, so I can flash it using a PIC/EEPROM programmer?

 

 

Thank you,

Joselito Maciel.

Attached Thumbnails

• 

[mlord]

Just RMA it.  It's under warranty, and you have done nothing wrong to it.  Returnable.

[jbmaciel]

Just RMA it.  It's under warranty, and you have done nothing wrong to it.  Returnable.

I've got this Nexstar+ when I was in US on vacation, now I am back to Brazil.

The warranty won't cover, I already talked with the technical support.

It is not a worldwide warranty, even so I would have to ship it to US and back. It is not worth, the S&H cost is very high.

 

If I don't get the files I will get a new Nexstar+ HC in Aliexpress, which will cost around $85.00 with "free S&H".

 

 

I asked for the binary files but they don't send it:

"We apologize for not being able to share the information you requested. The information is proprietary, and we cannot provide it. If you found the information another way, we are happy to hear you found the information you are looking for, but we cannot provide the information as it is proprietary."

 

"proprietary"...

 

 

Thanks,

Joselito Maciel.

[Bean614]

Hi all,

I was suggest by Frisk, I am starting a new thread about this issue.

I have this brand new Celestron telescope, Nexstar+ 6SE (USB), and I decide to update the firmware as I was recommended.

After running the CFM I've got this error (Update error 07-2023 1.bmp) saying the "Nexstar 6/8_AZM did not update sucessfully".

 

So I contacted the Celestron support and they sent me the following procedure:

********************************************************************************************************************************
Once you have the CFM software extracted and the driver installed, follow these steps:

1. Connect the hand control to the mount
2. Connect the hand control to the PC
3. Press and hold the Celestron logo button and the #7 while turning on the mount
4. Open CFM.jar
5. Wait for CFM to detect your devices or click on "Seek Devices"
6. Click NexStar+, then on Mount Types
7. Select the correct mount type (Alt-AZ or GEM)
8. Click on Seek devices
9. Click on update
10. Restart mount

If you receive any errors, attempt to perform an update again, but first remove CFM and its folders from your computer and attempt to perform an update using the BETA CFM, following the steps above, but instead of using the link to install the public CFM, please use the link below to install Beta CFM.

BETA CFM - http://software.cele...9.1085_beta.zip

If you continue to have issues with the beta, please remove BETA CFM and its files from your computer, reinstall the public version of CFM, and attempt the update again. If it fails this time, please provide screenshots from CFM showing the unsuccessful update.
********************************************************************************************************************************

I did the steps 1-10 with public CFM and I stiil getting the same error (Update error 07-2023 1.bmp).
So, I follow the same steps com the beta CFM and after a very brief message error saying corrupt file, it had shown that the update was successful.
But now the mount doesn't turn on, it looks dead.

The PC still recognize the "Prolific PL2303GL USB Serial COM Port", but there is no communication between the mount and the PC.

 

Then the technical support send this:

************************************************************************************************************************************
Please perform a factory reset. You can do this by holding down the 0 button while turning the mount on.
Next you will try to flash the firmware but first, close CFM, look in the folder where you unzipped CFM and delete the Packages folder. Now please start the update process again. Note it will take a few minutes for CFM to download all the packages via the Internet

************************************************************************************************************************************

 

But it didn't work, because the Nexstar+ is dead.

 

Does anyone has the firmware binaries dump, so I can flash it using a PIC/EEPROM programmer?

 

 

Thank you,

Joselito Maciel.

"I decide to update the firmware as I was recommended.".....?????????

 

Why on earth would you update it??  It was new!  You should ALWAYS test a New product  ( ANY new product! ), as Delivered!  If there's an issue, as I've warned in dozens of Posts, you can get a refund or replacement instantly. BUT....if you immediately 'Update' it, without first testing as-is, the Manufacturer/Retailer can justifiably claim that YOU caused the issue!  Further, the update you did might have had Nothing whatsoever to do with your version your mount!  I can't imagine who would possibly recommend that you update immediately. 

    Listen, "If it ain't broke,  don't fix it! ".

[mlord]

The binary files are in the CFM Packages directory.

[mlord]

"I decide to update the firmware as I was recommended.".....

 

Why on earth would you update it??

In this case, the manufacturer recommends that one update it.  This IS covered by warranty.  It IS BROKEN FROM THE FACTORY, which is why the updates are there and recommended by Celestron.

 

The only issue here is a grey market purchase, which makes using the warranty difficult.  Otherwise, it would be very straightforward.

 

The best time to update firmware is IMMEDIATELY on receipt of new gear, while it is under warranty in case something Bad Happens.

Edited by mlord, 04 August 2023 - 08:01 PM.

[Bean614]

In this case, the manufacturer recommends that one update it.  This IS covered by warranty.  It IS BROKEN FROM THE FACTORY, which is why the updates are there and recommended by Celestron.

 

The only issue here is a grey market purchase, which makes using the warranty difficult.  Otherwise, it would be very straightforward.

 

The best time to update firmware is IMMEDIATELY on receipt of new gear, while it is under warranty in case something Bad Happens.

"The best time to update firmware is IMMEDIATELY on receipt of new gear, while it is under warranty in case something Bad Happens."

I respectfully disagree.  First, whether a car, camera, stereo, anything,  it should be immediately tested as-is, as delivered!  THAT removes all questions about who is at fault!

Next, I  think most on CN, who are not IT Engineers or Managers, nor 'digital junkies', might tend to agree with "If it ain't........".

[mlord]

I'll follow the manufacturer's recommendation, because IT IS BROKEN, and IT NEEDS FIXING. 

 

But that's not the issue here. The only issue in this thread is a grey market one, meaning the warranty is almost worthless.

[Bean614]

I'll tell a quick story, as I've purchased MANY brand new scopes/mounts/accessories from Celestron.  2 years ago I bought a new mount from a well-known authorized dealer.  I was told to update it immediately!  I received the mount, set it up and tested it indoors with 'dummy' alignments, then set it up outdoors the next night, and tested it again.  ZERO issues, and specifically, NO sign at all of the 'issue' that the update was supposed to 'correct'.  I called Celestron (yes, telephone!) directly, as they knew me well, and I had spoken to the agent many times in the previous 4 or 5 years.  He asked me for the Serial Number, and then said "Oh, you have one of the newer versions, and we already took care of that issue.  We just haven't had time to notify the Dealers or Consumers".  

[jbmaciel]

"I decide to update the firmware as I was recommended.".....?????????

 

Why on earth would you update it??  It was new!  You should ALWAYS test a New product  ( ANY new product! ), as Delivered!  If there's an issue, as I've warned in dozens of Posts, you can get a refund or replacement instantly. BUT....if you immediately 'Update' it, without first testing as-is, the Manufacturer/Retailer can justifiably claim that YOU caused the issue!  Further, the update you did might have had Nothing whatsoever to do with your version your mount!  I can't imagine who would possibly recommend that you update immediately. 

    Listen, "If it ain't broke,  don't fix it! ".

"Why on earth would you update it??"

 

Because that is the way it is.

 

I work with electronics since always (maybe 40 years), and I will tell you, there is no such a thing as final version, there is always something to fix, something to improve...

 

Thank you,

Joselito Maciel.

[jbmaciel]

The binary files are in the CFM Packages directory.

Yes, I know, but those are modules that should be burned in a specific sequence (or position in the EEPROM) which I don't know.

I need a memory dump, for example, the PIC controller (PIC18F85J10) has 32KB flash memory, I need the image of this flash memory.

 

Actually the Nexstar+ has 3 Flash memories:

1) 8KBytes Serial EEPROM (24LC64)

2) 32KBytes Flash built in on PIC microcontroller (PIC18F85J10).

3) 2MBytes Flash PROM (MX29LV160D).

 

Thank you,

Joselito Maciel.

[mlord]

Yes, I know, but those are modules that should be burned in a specific sequence (or position in the EEPROM) which I don't know.

I need a memory dump, for example, the PIC controller (PIC18F85J10) has 32KB flash memory, I need the image of this flash memory.

 

Actually the Nexstar+ has 3 Flash memories:

1) 8KBytes Serial EEPROM (24LC64)

2) 32KBytes Flash built in on PIC microcontroller (PIC18F85J10).

3) 2MBytes Flash PROM (MX29LV160D).

Do you have an easy way to extract those images from a working handset?

[Frisk]

Mark I have to disagree with you on this. There may be bugs but unless they impact you they aren't worth fixing particularly for older mounts. Add on the constant problems updates cause for new and even experienced users it is not good to recommend updating.

 

This is an SE mount. Whatever is in the HC is going to be fine for it and the MC hasn't been updated for years.

 

It takes quite a bit of reading and research on multiple webpages ‐ very few of which belong to Celestron ‐ to understand the potential benefits and risks of updating PARTICULARLY with CFM.

 

It is laughable to argue that updating makes sense when Celestron inevitably points people to an old BETA version of CFM to attempt to fix what the latest version breaks.

 

Face reality. We are seeing HCs dropping like flies. 

 

The last thing a new user should do is attempt a firmware update. 

Edited by Frisk, 05 August 2023 - 06:35 AM.

[Frisk]

A version 4 HC will also work with your mount. You would use HCUpdate to put the firmware on that version HC.

 

I would recommed MCUpdate rather than CFM for the mount motor controls but there are issues if you try MCupdate through a V5 (Plus) HC. V4 is fully compatible. Still you should not require motor control updates. 

 

Also do not use the beta version of CFM on your MC without deleting the Nexstar45 and  68 packages to avoid CFM hosing your mount. (Turn off network to prevent packages from downloading and set CFM to offline).

 

Be sure to study nexstarsite.com before doing *any* firmware updates so you have all  the details.

Edited by Frisk, 05 August 2023 - 07:57 AM.

[jbmaciel]

Do you have an easy way to extract those images from a working handset?

Yes, I have a PIC/EEPROM programmer.which can read/extract that content.

[mlord]

Yes, I have a PIC/EEPROM programmer.which can read/extract that content.

Well, if it can read from that huge QFP processor inside the Nexstar+ hand-controller, I'd like to know more.  Might pick one up, at which point I could dump the chip contents for you.

Edited by mlord, 05 August 2023 - 09:37 AM.

[jbmaciel]

Well, if it can read from that huge QFP processor inside the Nexstar+ hand-controller, I'd like to know more.  Might pick one up, at which point I could dump the chip contents for you.

Actually it is not huge, it is pretty small, and most of new ICs are serial programmed, not parallel.

I mean, even if the microcontroller is 16bit, you don't need 16 data lines connected to flash, usually it needs 2 lines "serial data" and "clock".

The Nexstar+ microcontroller (PIC18F85J10) uses ICSP (In Circuit Serial Programming) connection to be flashed.

 

PIC ICSP provides 6 connections from the pic ICSP programmer to your board as follows :

1. VPP (or MCLRn) Programming voltage (usually 13V).
2. Vcc Power (usually 5V).
3. GND Ground (zero volts).
4. PGD - Data usual port and connection RB7.
5. PGC - Clock usual port and connection RB6.
6. PGM - LVP enable usual port and connection RB3/RB4.

 

To avoid soldering pins, you can use a ICSP clip (ICSP Clip 1.jpg) (https://pt.aliexpres...ayAdapt=glo2bra)

 

I am getting a new programmer, because mine is a kind of outdated. (https://pt.aliexpres...ayAdapt=glo2bra)

 

If I don't find the files I will get a new HC ($85 Aliexpress) to extract de binaries and to try to fix this one.

 

 

Regards,

Joselito Maciel.

Attached Thumbnails

• 
• 
• 
• 

Edited by jbmaciel, 05 August 2023 - 02:22 PM.

[jbmaciel]

A version 4 HC will also work with your mount. You would use HCUpdate to put the firmware on that version HC.

 

I would recommed MCUpdate rather than CFM for the mount motor controls but there are issues if you try MCupdate through a V5 (Plus) HC. V4 is fully compatible. Still you should not require motor control updates. 

 

Also do not use the beta version of CFM on your MC without deleting the Nexstar45 and  68 packages to avoid CFM hosing your mount. (Turn off network to prevent packages from downloading and set CFM to offline).

 

Be sure to study nexstarsite.com before doing *any* firmware updates so you have all  the details.

I already tried that, the HC is dead. It is not detected in any way, nothing shows in the display.

 

Probably that was the mistake, I setted the CFM online.

 

 

Thanks,

Joselito Maciel.

[mlord]

So for the hand-controller, which test clip?

 

I think it may be the 6-pin 2.54mm spacing one?

Or different?

 

Thanks

[mlord]

I can get the programmer gizmo from Amazon Canada for only slightly more than from AliExpress, and it would arrive within a day or two of ordering.  So if you are confident that the XGECU T48 will do the job, then I'll get one and use it to dump the flash contents.  But I'm on the road now for another 10 days, so this will not happen until around August 15.

 

My real interest is in seeing if it can be used to dump and reprogram a similar chip on an Evo mount main board.

 

Cheers

Edited by mlord, 05 August 2023 - 08:06 PM.

[jbmaciel]

So for the hand-controller, which test clip?

 

I think it may be the 6-pin 2.54mm spacing one?

Or different?

 

Thanks

Yes, that is the one I ordered: Single row / 6 pin / 2.54mm.

 

Regards,

Joselito Maciel.

Attached Thumbnails

• 

[jbmaciel]

I can get the programmer gizmo from Amazon Canada for only slightly more than from AliExpress, and it would arrive within a day or two of ordering.  So if you are confident that the XGECU T48 will do the job, then I'll get one and use it to dump the flash contents.  But I'm on the road now for another 10 days, so this will not happen until around August 15.

 

My real interest is in seeing if it can be used to dump and reprogram a similar chip on an Evo mount main board.

 

Cheers

I never used this T48 programmer but by the documentation and support (http://www.xgecu.com/en/Index.html), it looks very good and the all ICs are in the supported device list.

It is a mid range, there is a T56 (top of line) that is faster and with a bigger device list..

 

You may also need the 8 pin SOIC adapter for the serial EEPROM 24LC64 (this one I already have from the old programmer). You have to see if the Evo mount has those.

 

I am not sure about the Evo mount, but I am assuming that in the Nexstar, the bootloader is in the serial EEPROM or PIC18F85,

If I get the bootloader restored then I get to run the CFM again, if not we will have to deal with nand flash (MX29LV160D), then we need to get a TSOP 48 pin adapter for that.

 

Regards,

Joselito Maciel.

Attached Thumbnails

• 

[mlord]

I can get the programmer gizmo from Amazon Canada for only slightly more than from AliExpress, and it would arrive within a day or two of ordering.  So if you are confident that the XGECU T48 will do the job, then I'll get one and use it to dump the flash contents.  But I'm on the road now for another 10 days, so this will not happen until around August 15.

 

My real interest is in seeing if it can be used to dump and reprogram a similar chip on an Evo mount main board.

The chip on the Evo is not on the supported list.  But I will get the T48 programmer regardless -- Amazon Canada no longer has it, so I've ordered it from AliExpress, with delivery here around the end of August.

 

There is something wrong with the latest "bootloader" portion of the Nexstar hand-controllers -- it no longer works reliably with CFM, which would explain how several attempted CFM updates have failed here recently.  I investigated by purchasing a spare new controller with warranty, and attempted to update it.  No luck whatsoever using the USB cable, but it did update once over Wifi when connected to my Evo mount.  I tried again after that, and bricked the hand-controller -- nothing on the display, totally dead.  And returned under warranty now.

 

As I may someday want to update my primary hand-controller, I'm getting the T48 so that I can create back-up images that could later be restored.

 

Cheers
 

[jbmaciel]

The chip on the Evo is not on the supported list.  But I will get the T48 programmer regardless -- Amazon Canada no longer has it, so I've ordered it from AliExpress, with delivery here around the end of August.

 

There is something wrong with the latest "bootloader" portion of the Nexstar hand-controllers -- it no longer works reliably with CFM, which would explain how several attempted CFM updates have failed here recently.  I investigated by purchasing a spare new controller with warranty, and attempted to update it.  No luck whatsoever using the USB cable, but it did update once over Wifi when connected to my Evo mount.  I tried again after that, and bricked the hand-controller -- nothing on the display, totally dead.  And returned under warranty now.

 

As I may someday want to update my primary hand-controller, I'm getting the T48 so that I can create back-up images that could later be restored.

 

Cheers
 

If you get the back-up images please share with me, so I can try to wake up my HC.
Thank you.

 

Joselito Maciel

[mlord]

Okay, so I have the T48 here, software/driver installed, firmware updated.

Now working out how to connect it to the PIC in the hand-controller.  The software shows this:

 

 

But the earlier pin-out given for the 6-pins (J8) on the hand-controller appears to be wrong for this PIC.

Here is my hand-controller, with pins soldered onto the 6-pin ICSP pads.

I have traced the 6-pins to the PIC chip, and now labelled what is actually there.

Quite different from what was posted earlier:

 

 

So now, my instinct would be to unplug the hand-controller from the mount, and then connect its 6-pin ICSP header as follows:

 

1 (VDD)   -->  T48 pin-13

2 (GND)   -->  T48 pin-16

3 (PGM)   -->  nothing

4 (MCLR)  -->  T48 pin-1

5 (PGC)   -->  T48 pin-3

6 (PGD)   -->  T48 pin-5

 

EDIT: Did that, and it worked.  It also worked when I used USB power instead of the VDD line.

I now have a 32KB flash image of the bootloader from the hand-controller.

 

 

Notice that I used individual jumper wires, rather than the fancy 16-pin connector that came with the T48:  they number the pins incorrectly on their diagrams, so it was easier for me to keep things correct by using my own individual jumper wires.

Edited by mlord, 26 August 2023 - 10:14 PM.