Error when flashing the new firmware

Question

Error when flashing the new firmware

minimmi opened this issue 2 years ago · 72 comments

Hello,

I am currently trying to flash the latest router firmware:

https://github.com/Koenkk/Z-Stack-firmware/blob/develop/router/Z-Stack_3.x.0/bin/CC1352P2_CC2652P_launchpad_router_20221102.zip

but I always get the following error message:

What am I doing wrong? Can anyone help me?

Shamshala commented 2 years ago

Same here

Answer 1 · 2022-11-04T17:15:24.000Z

I'm getting the same.. A bit of googling suggests it may be something to do with the method that was used to compile the hex..?

Answer 2 · 2022-11-04T17:16:38.000Z

did you unzip the file?

Answer 3 · 2022-11-04T17:18:01.000Z

Yes and followed the flashing guidelines. Haven't had an issue with previous firmwares.. just this one. Please see my linked closed issue for a full screenshot of the window

Answer 4 · 2022-11-04T17:25:44.000Z

Yes and followed the flashing guidelines. Haven't had an issue with previous firmwares.. just this one

I can confirm that. With the previous firmware version everything works without problems. If I then try to flash the new in the same way, I get the error message.

Answer 5 · 2022-11-04T17:41:36.000Z

Same error here as well using the TI software to update the Sonoff Zigbee 3.0 dongle. I flashed the previous firmware to see if something was wrong with my device and it worked perfectly.

Answer 6 · 2022-11-05T15:59:12.000Z

Same here for a Sonoff CC2652P

Initiate access to target: COM6 using 2-pin cJTAG.
Reading file: C:/ATemp/ZIGBEE Firmware/Coordinator/CC1352P2_CC2652P_launchpad_coordinator_20221102.hex.
Unknown record type: 3.
Reset target ...
Reset of target successful.
Initiate access to target: COM6 using 2-pin cJTAG.
Reading file: C:/ATemp/ZIGBEE Firmware/Coordinator/CC1352P2_CC2652P_launchpad_coordinator_20221102.hex.
Unknown record type: 3.
Reset target ...
Reset of target successful.
Initiate access to target: COM6 using 2-pin cJTAG.
No response from device. Device may not be in bootloader mode. Reset device and try again.
If problem persists, check connection and baud rate.
Connecting over serial bootloader failed: No response from device. Device may not be in bootloader mode. Reset device and try again.
If problem persists, check connection and baud rate.
Failed to create device object.

Answer 7 · 2022-11-05T16:00:11.000Z

used now the stable one which works without an issue , using Texas Instruments flasher

Answer 8 · 2022-11-05T16:05:35.000Z

Just to add - this the same error when trying the router firmware

Answer 9 · 2022-11-05T22:20:17.000Z

Same here, unable to flash as per what others are saying above.

Answer 10 · 2022-11-06T13:06:18.000Z

Follow these instructions

#383 (comment)

Answer 11 · 2022-11-06T14:04:16.000Z

Reported this to TI: https://e2e.ti.com/support/wireless-connectivity/zigbee-thread-group/zigbee-and-thread/f/zigbee-thread-forum/1168418/simplelink-cc13x2-26x2-sdk-flashing-simlelink-6_30_00_84-hex-through-uniflash-fails

Answer 12 · 2022-11-06T14:08:58.000Z

Seems that the issue is specific to Uniflash 8.1.0, Uniflash 8.0.0 works fine for me.

Answer 13 · 2022-11-06T15:43:29.000Z

Downloaded UniFlash here:
https://www.ti.com/tool/download/UNIFLASH/8.0.0

I tried to flash the firmware with Uniflash, but I can't get it to work because my dongle is not recognized:

Answer 14 · 2022-11-06T17:07:12.000Z

TI Flash Programmer 2 is what I have been using (and others posting) that doesn’t work with the new firmware. I hadn’t seen Uniflash mentioned for flashing the Sonoff dongle.

Answer 15 · 2022-11-06T19:28:17.000Z

Update:

Have now tried to flash the firmware with the help of the python script as described in this video:

https://youtu.be/iCE5Z43EKpk?t=1254

It looked like everything worked out:

but after i reconnected the stick, zigbee2mqtt still shows me the old firmware:

Answer 16 · 2022-11-06T21:38:17.000Z

I'm getting the same error that others have reported.

Initiate access to target: COM3 using 2-pin cJTAG.
Reading file: Z:/Projects/Zigbee_Flash/CC1352P2_CC2652P_launchpad_router_20221102/CC1352P2_CC2652P_launchpad_router_20221102.hex.
Unknown record type: 3.
Reset target ...

I can still flash the older FW but not this new one.

Answer 17 · 2022-11-07T16:48:08.000Z

TI responded that this is a known issue of Uniflash 8.1.0, so nothing we can do from the z2m side. Use Uniflash 8.0.0 or cc2538-bsl or zigstar flasher instead.

https://e2e.ti.com/support/wireless-connectivity/zigbee-thread-group/zigbee-and-thread/f/zigbee-thread-forum/1168418/simplelink-cc13x2-26x2-sdk-flashing-simlelink-6_30_00_84-hex-through-uniflash-fails

Answer 18 · 2022-11-07T17:34:23.000Z

TI responded that this is a known issue of Uniflash 8.1.0, so nothing we can do from the z2m side. Use Uniflash 8.0.0 or cc2538-bsl or zigstar flasher instead.

https://e2e.ti.com/support/wireless-connectivity/zigbee-thread-group/zigbee-and-thread/f/zigbee-thread-forum/1168418/simplelink-cc13x2-26x2-sdk-flashing-simlelink-6_30_00_84-hex-through-uniflash-fails

As you can see in my last comment, I did the flashing with cc2538-bsl. In zigbee2mqtt I still see the old firmware.

Answer 19 · 2022-11-07T18:35:17.000Z

@minimmi Try it again, I succesfully flashed coordinator via cc2538-bsl and it works.

Answer 20 · 2022-11-07T20:43:05.000Z

Downgrading to Uniflash 8.0.0 worked for me. Thanks!

Answer 21 · 2022-11-09T17:36:04.000Z

Also please try ZigStar Multitool (https://zig-star.com/radio-docs/zigstar-multi-tool/) developed for zigstar works with any CC2652p adapter.

Answer 22 · 2022-11-09T18:29:06.000Z

I used now successfully the ZigStar Multitool. Is a bit tricky for writing the firmware.
First it detects the COM Port, when starting writing you need to push the Boot button again multiple times and click on start in parallel. Suddenly it will start writing - is a bit confusing this behaviour but it worked.

Answer 23 · 2022-11-10T01:17:08.000Z

cc2538-bsl woked for me, used a windows machine, command such as:

python cc2538-bsl.py -ewv -p /dev/ttyUSB0 --bootloader-sonoff-usb .\PATH_TO_FIRMWARE.hex

Answer 24 · 2022-11-10T15:46:02.000Z

I was also successful with the python script, run from a Win11 machine to update my Sonoff Zigbee Dongle Plus:

py cc2538-bsl.py -e -w -v -p com3 --bootloader-sonoff-usb CC1352P2_CC2652P_launchpad_coordinator_20221102.hex

Answer 25 · 2022-11-10T18:59:00.000Z

I just don't know what I'm doing wrong or what it could be?! I have now flashed it again successfully with both cc2538-bsl.py and ZigStar. But every time the old firmware is displayed afterwards in zigbee2mqtt:

Answer 26 · 2022-11-10T19:08:44.000Z

I used now successfully the ZigStar Multitool. Is a bit tricky for writing the firmware. First it detects the COM Port, when starting writing you need to push the Boot button again multiple times and click on start in parallel. Suddenly it will start writing - is a bit confusing this behaviour but it worked.

Thanks for that. I was able to get mine working as well with some fiddling around.

Answer 27 · 2022-11-10T19:46:58.000Z

I just don't know what I'm doing wrong or what it could be?! I have now flashed it again successfully with both cc2538-bsl.py and ZigStar. But every time the old firmware is displayed afterwards in zigbee2mqtt:

And you are using the dev version? I never checked afterwards...

Answer 28 · 2022-11-10T20:00:44.000Z

I just don't know what I'm doing wrong or what it could be?! I have now flashed it again successfully with both cc2538-bsl.py and ZigStar. But every time the old firmware is displayed afterwards in zigbee2mqtt:

And you are using the dev version? I never checked afterwards...

Yes, I use this version:

https://github.com/Koenkk/Z-Stack-firmware/blob/develop/router/Z-Stack_3.x.0/bin/CC1352P2_CC2652P_launchpad_router_20221102.zip

I am interested in the possibility of adjusting the transmitting power, but I still do not have this option.

Answer 29 · 2022-11-10T23:26:15.000Z

But every time the old firmware is displayed

For Router firmware?

I had the same problem. It's more a z2m issue than a flashing issue.

@Koenkk recommended doing a force remove, restart, then re-pair. Worked for me.

Answer 30 · 2022-11-11T07:39:57.000Z

But every time the old firmware is displayed

For Router firmware?

I had the same problem. It's more a z2m issue than a flashing issue.

@Koenkk recommended doing a force remove, restart, then re-pair. Worked for me.

Thanks for this tip. After force remove, restart and re-pair it shows now the correct firmware.

I can confirm under these circumstances that flashing with Zigstar as well as with cc2538-bsl.py works.

But I still have no way to set the transmit power:

Answer 31 · 2022-11-11T14:43:12.000Z

@minimmi If you update to the latest development code of z2m, the option for changing the transmit power will be there:

However I don't recomment you to update to the latest dev yet, as there is a bug preventing pairing of new devices:

Koenkk/zigbee2mqtt#14925 (comment)

I've patched the code as a workaround for the time being in order to be able to test the new router firmware and setting transmit_power indeed works as intended.

Answer 32 · 2022-11-11T16:47:08.000Z

@minimmi If you update to the latest development code of z2m, the option for changing the transmit power will be there:

However I don't recomment you to update to the latest dev yet, as there is a bug preventing pairing of new devices:

Koenkk/zigbee2mqtt#14925 (comment)

I've patched the code as a workaround for the time being in order to be able to test the new router firmware and setting transmit_power indeed works as intended.

Ah ok, I didn't know that I needed the dev version of z2m for this. Thanks for your answer. Then I'll wait until the dev version is tested and officially released.

I see in your screenshot that it says 5dBm max for CC2652. Is the max transmit power not 20 dBm for CC2652 ?

Answer 33 · 2022-11-15T18:13:00.000Z

@minimmi

I see in your screenshot that it says 5dBm max for CC2652. Is the max transmit power not 20 dBm for CC2652 ?

Just now I noticed your follow-up question about the max power. I think the help text is indeed a bit misleading. My adapter is a home-made "Egony V4" stick (the module uses internally a CC2652P chip) and changing the power slider to values above 5 dBm is definitely reflected in the LQI value. As far as I'm aware, the P versions of the CC1352 / CC2652 chips can go up to 20 dBm, so the wording of the helptext might be changed to something like:

"Transmit power, supported from firmware 20221102. The max for CC1352P/CC2562P is 20 dBm and 5 dBm for CC1352/CC2652 (any higher value is converted to 5dBm)"

Answer 34 · 2022-11-25T13:27:19.000Z

But every time the old firmware is displayed

For Router firmware?
I had the same problem. It's more a z2m issue than a flashing issue.
@Koenkk recommended doing a force remove, restart, then re-pair. Worked for me.

Thanks for this tip. After force remove, restart and re-pair it shows now the correct firmware.

I can confirm under these circumstances that flashing with Zigstar as well as with cc2538-bsl.py works.

But I still have no way to set the transmit power:

I flashed an already paired sonoff ZBDongle-P with CC1352P2_CC2652P_other_router_20221102.zip router firmware using the cc2538-bsl script. All went smoothly and the firmware was flashed without issues.
As it is already reported the device shows up that is has the previous firmware.

I am using the latest release of zigbee2mqtt (1.28.2) not from the dev channel that it has the pairing issue. I forced removed the device but afterwards the device was recognized as unknown device.

@Koenkk
Is something that I should expect ?

Answer 35 · 2022-11-28T15:09:27.000Z

@nkrepo Shouldn't you be using CC1352P2_CC2652P_launchpad_router_20220125.zip with ZBDongle-P (instead of CC1352P2_CC2652P_other_router_20221102.zip) ?

I'm also using a ZBDongle-P and flashed it with the launchpad_router firmware variant, as seen in the last row of the table here:
https://github.com/Koenkk/Z-Stack-firmware/blob/master/coordinator/Z-Stack_3.x.0/bin/README.md

Answer 36 · 2022-12-01T21:08:39.000Z

Slight update here. UniFlash 8.1.1 works fine. I read that some used the SmartRF Flash Programmer 2 as I did, too.
Nope. Still v1.8.3 and still unuseable...

Answer 37 · 2022-12-02T08:06:24.000Z

Short update from my side:

cc2538-bsl.py works
ZigStar works
TI Flash Programmer v2 does not work
Uniflash 8.1.X does not work
Uniflash 8.0.0 works partially ( not for me, because stick is not recognized. For others it seems to work)

Should this stay open until it works with all methods or can it be closed, what do you say?

Answer 38 · 2022-12-02T11:22:34.000Z

had also the same issue with TI flash programmer 2 ver. 1.8.2 and was sucessful with cc2538-bsl.py ;)

Answer 39 · 2022-12-02T13:43:25.000Z

Is there some that have flash a sonoff plus dongle flashed with the new firmware?

What software is working the best.
And simple?
Noob here.

Thanks guys

Answer 40 · 2022-12-02T14:25:07.000Z

@Dylantje I find the cc2538-bsl.py script working flawless, every time. It's simple to use it too. You just need to have Python installed first, then invoke the script like this:

python cc2538-bsl.py -e -w -v -p PORT firmware.hex

where PORT is the serial port where your ZigBee device has been attached.

In Linux that might be /dev/ttyUSB0, in Windows - COM4 etc.

Answer 41 · 2022-12-02T17:01:02.000Z

@znanev
Thanks
Only never worked with python. Running on a windows pc..
Will try it, only can i brick the stick?

Prefere a windows option for me.
Perhaps a good working option

Answer 42 · 2022-12-02T19:01:23.000Z

I haven't used it, but the zigstar tool is open source, cc2538-bsl based, and the releases include both Windows and Mac GUI builds.

https://github.com/xyzroe/ZigStarGW-MT

Answer 43 · 2022-12-02T20:56:59.000Z

nkrepo
Good to notice , I have indeed flashed with CC1352P2_CC2652P_launchpad_router_20221102 , it was just a text copy paste error.
I upgraded to latest zigbee2mqtt 1.28.4 and the now the sonoff p dongle flashed with 20221102 is paired without any issue.

Answer 44 · 2022-12-02T22:46:26.000Z

Hi Guys. im trying to flash my CC2652R zzh coordinator with the new 20221102 firmware but on Uniflash it doesnt auto detect my coordinator and from their list i cant see a CC2652R. I do see a CC2652R1F and a 1F(Bootloader) any advice which one to choose?

Answer 45 · 2022-12-05T06:14:23.000Z

@znanev Thanks Only never worked with python. Running on a windows pc.. Will try it, only can i brick the stick?

Prefere a windows option for me. Perhaps a good working option

Follow the instructions in this video:

https://youtu.be/iCE5Z43EKpk?t=1254

With this I managed to do it without any problem.

Answer 46 · 2022-12-08T08:04:31.000Z

Same as yours: problems with TI flash programmer but it works with python script (I mean Sonoff 3.0 and router firmware) and now ZHA (🤫) has power transmitter slider too. Thanks @Koenkk

Answer 47 · 2022-12-10T10:56:26.000Z

I used a Hex2bin converter on the .hex file which converted it to a .bin file and was able to flash that using the TI Flash Programmer.

Answer 48 · 2022-12-14T04:16:06.000Z

I also tryed to convert to BIN, with Hex2bin, and now it works with TI Flash :-)

Answer 49 · 2022-12-14T16:25:51.000Z

I'll close this thread since it is an issue of the TI tooling and not this firmware.

Answer 50 · 2023-03-06T07:40:02.000Z

Following procedure worked for me on Sonoff ZIgbee 3.0 USB Dongle Plus (ZBDongle-P):

Converting CC1352P2_CC2652P_launchpad_router_20221102.hex to binary format using https://srecord.sourceforge.net/:
srec_cat.exe "CC1352P2_CC2652P_launchpad_router_20221102.hex" -intel -o CC1352P2_CC2652P_launchpad_router_20221102.bin -binary
Programming CC1352P2_CC2652P_launchpad_router_20221102.bin file using TI SmartRF Flash Programmer 2 (ver. 1.8.2) (target: CC2652P)

Answer 51 · 2023-03-15T05:45:51.000Z

Following procedure worked for me on Sonoff ZIgbee 3.0 USB Dongle Plus (ZBDongle-P):

Converting CC1352P2_CC2652P_launchpad_router_20221102.hex to binary format using https://srecord.sourceforge.net/:
srec_cat.exe "CC1352P2_CC2652P_launchpad_router_20221102.hex" -intel -o CC1352P2_CC2652P_launchpad_router_20221102.bin -binary

Programming CC1352P2_CC2652P_launchpad_router_20221102.bin file using TI SmartRF Flash Programmer 2 (ver. 1.8.2) (target: CC2652P)

Worked for me.

Answer 52 · 2023-04-02T21:00:55.000Z

Following procedure worked for me on Sonoff ZIgbee 3.0 USB Dongle Plus (ZBDongle-P):

Converting CC1352P2_CC2652P_launchpad_router_20221102.hex to binary format using https://srecord.sourceforge.net/:
srec_cat.exe "CC1352P2_CC2652P_launchpad_router_20221102.hex" -intel -o CC1352P2_CC2652P_launchpad_router_20221102.bin -binary

Programming CC1352P2_CC2652P_launchpad_router_20221102.bin file using TI SmartRF Flash Programmer 2 (ver. 1.8.2) (target: CC2652P)

Worked for me.

How to use srecord? I have no idea! Have download it but there is noch app to open and use for converting it.

Answer 53 · 2023-04-06T18:25:30.000Z

Download srecord from sourceforge, unzip and execute srec_cat from bin folder as per the the command line example above.

Answer 54 · 2023-04-16T15:24:26.000Z

This is what i did:

Install ‘SRecord’
Open power shell with administrator tight
Guide to the ‘SRecord’ install folder ‘C:\Program Files\srecord\bin’
Copy the firmware (CC1352P2_CC2652P_launchpad_router_20221102.hex) to above folder
Run this command to start converting the files
.\srec_cat.exe "CC1352P2_CC2652P_launchpad_router_20221102.hex" -intel -o CC1352P2_CC2652P_launchpad_router_20221102.bin -binary

Answer 55 · 2023-04-19T22:35:18.000Z

A Big Thanks to You!!!

This is what i did:

Install ‘SRecord’

Open power shell with administrator tight

Guide to the ‘SRecord’ install folder ‘C:\Program Files\srecord\bin’

Copy the firmware (CC1352P2_CC2652P_launchpad_router_20221102.hex) to above folder

Run this command to start converting the files
.\srec_cat.exe "CC1352P2_CC2652P_launchpad_router_20221102.hex" -intel -o CC1352P2_CC2652P_launchpad_router_20221102.bin -binary

Answer 56 · 2023-05-03T13:56:20.000Z

This is what i did:

Install ‘SRecord’

Open power shell with administrator tight

Guide to the ‘SRecord’ install folder ‘C:\Program Files\srecord\bin’

Copy the firmware (CC1352P2_CC2652P_launchpad_router_20221102.hex) to above folder

Run this command to start converting the files
.\srec_cat.exe "CC1352P2_CC2652P_launchpad_router_20221102.hex" -intel -o CC1352P2_CC2652P_launchpad_router_20221102.bin -binary

It worked! Thanks!

If anyone is crazy enough, here is the firmware bin file so you can flash with Flash Programmer 2:
(I AM NOT RESPONSIBLE FOR THIS FILE, USE AT YOUR OWN RISK)

Answer 57 · 2023-08-07T01:47:21.000Z

5. .\srec_cat.exe "CC1352P2_CC2652P_launchpad_router_20221102.hex" -intel -o CC1352P2_CC2652P_launchpad_router_20221102.bin -binary

Worked like a charm thanks for the heads up :)

Answer 58 · 2023-08-08T11:13:10.000Z

This is what i did:

Install ‘SRecord’

Open power shell with administrator tight

Guide to the ‘SRecord’ install folder ‘C:\Program Files\srecord\bin’

Copy the firmware (CC1352P2_CC2652P_launchpad_router_20221102.hex) to above folder

Run this command to start converting the files
.\srec_cat.exe "CC1352P2_CC2652P_launchpad_router_20221102.hex" -intel -o CC1352P2_CC2652P_launchpad_router_20221102.bin -binary

CCS already has all the necessary utilities for making a bin file. You can add this line in project settings Project>Properties>Build>Steps>Post-build steps

"${CCS_INSTALL_ROOT}/utils/tiobj2bin/tiobj2bin" "${BuildArtifactFileName}" "${BuildArtifactFileBaseName}.bin" "${CG_TOOL_ROOT}/bin/tiarmofd" "${CG_TOOL_ROOT}/bin/tiarmhex" "${CCS_INSTALL_ROOT}/utils/tiobj2bin/mkhex4bin"

As shown in the picture below

Answer 59 · 2023-08-08T14:08:18.000Z

Just to share my experience:

SmartRF utility works fine, although it appears necessary to convert to bin format. I used 'hex2bin'

- The Sonoff stick drops out of boot mode very quickly - within 20 seconds. So you need to keep plugging it back in whilst holding down boot button for 5 seconds or so. This must be repeated for every attempt

Answer 60 · 2023-08-25T14:58:21.000Z

I started by trying to use UniFlash but got confused looking for the right chip to choose for sonoff zigbee dongle plus...
so I did the .hex -> .bin using srecord and everething was OK!

Answer 61 · 2023-12-15T21:35:14.000Z

I was able to avoid installing Python.

There's a workaround with ZigStarGW on Windows.

Plug the dongle and hold the button 20 seconds
Try to flash and get "timeout" message
Unplug and plug the dongle immediately
Try to flash again and it'll work

Texas Instrument is crappy.

Answer 62 · 2023-12-19T02:51:39.000Z

I was able to avoid installing Python.

There's a workaround with ZigStarGW on Windows.

Plug the dongle and hold the button 20 seconds

Try to flash and get "timeout" message

Unplug and plug the dongle immediately

Try to flash again and it'll work

Texas Instrument is crappy.

wow, this solution really worked
thank you very much....

MUITO OBRIGADO.....

Answer 63 · 2024-01-09T05:37:59.000Z

I was able to avoid installing Python.
There's a workaround with ZigStarGW on Windows.

Plug the dongle and hold the button 20 seconds

Try to flash and get "timeout" message

Unplug and plug the dongle immediately

Try to flash again and it'll work

Texas Instrument is crappy.

wow, this solution really worked thank you very much....

MUITO OBRIGADO.....

I can't believe it. This was the only solution that worked. I tried flashing my brand new CC2652P with Flash Programmer 2, the Python way (both using Windows and Linux), and this way was the only method that actually worked. You MUST unplug and replug immediately after seeing the Timeout error message at the bottom of the application and you must have held the Boot button down for 20 seconds

Big thanks @gravelfreeman and @gamajunior

Answer 64 · 2024-01-09T19:25:11.000Z

It's a complete non sense but hey, if we don't want our home to get spied on stupid companies cloud we gotta rely on the china scrap for automating our home. What a time to be alive! I wish that Zigbee or any other tech to become a standard so we stop doing stuff like this.

Answer 65 · 2024-01-09T20:25:01.000Z

@gravelfreeman Zigbee is standardized (see the spec here) but unfortunately a lot of devices don't conform very well or use undocumented custom messages over the protocol. That has little to do with programming firmware on specific coordinator hardware however.

If you want devices that conform more solidly to a spec and "just work" I think you probably want z-wave. It's a lot more tightly controlled (at least until very recently) and works on a much less congested lower frequency so there are less problems with interference. Z-wave devices are significantly more expensive however, and there are less of them available.

Answer 66 · 2024-02-25T22:42:27.000Z

This is what i did:

1. Install ‘SRecord’

2. Open power shell with administrator tight

3. Guide to the ‘SRecord’ install folder ‘C:\Program Files\srecord\bin’

4. Copy the firmware (CC1352P2_CC2652P_launchpad_router_20221102.hex) to above folder

5. Run this command to start converting the files
   .\srec_cat.exe "CC1352P2_CC2652P_launchpad_router_20221102.hex" -intel -o CC1352P2_CC2652P_launchpad_router_20221102.bin -binary

Thanks! Worked for me for updating from version 20210708 to 20230507. Version read out is updated accordingly on the following page: Zigbee2MQTT - Settings - About: Coordinator revision

Answer 67 · 2024-05-03T02:26:29.000Z

if you're having trouble converting from hexadecimal to bin.

Answer 68 · 2024-10-19T22:42:05.000Z

Anyone coming here in 2024 for the latest version, then here is the powershell command for bin file conversion. And it worked perfectly.

.\srec_cat.exe "CC1352P2_CC2652P_launchpad_coordinator_20240710.hex" -intel -o CC1352P2_CC2652P_launchpad_coordinator_20240710.bin -binary

Answer 69 · 2024-10-24T20:56:45.000Z

Anyone coming here in 2024 for the latest version, then here is the powershell command for bin file conversion. And it worked perfectly.

.\srec_cat.exe "CC1352P2_CC2652P_launchpad_coordinator_20240710.hex" -intel -o CC1352P2_CC2652P_launchpad_coordinator_20240710.bin -binary

can you give extra guide please

Answer 70 · 2024-10-27T16:05:48.000Z

Read a few posts up: #397 (comment)

Follow the instructions in the next two or three posts (and adjust the command for the correct firmware name) and you'll be fine. I just did it myself.