eZ430-Chronos-433 Firmware for new models

Hi,

I'm in the same position as you. 433Mhz Chronos 01/2013 production without CD (Why is there no CD? In most of the online documentation they make reference to the CD. Even though I have been able to find what I needed in the TI website, I still feel I am missing something).

Instead of using the IAR to flash the firmware I used the Firmware Update Tool from BM Innovations: http://www.bm-innovations.com/index.php/ez430-chronos . But after the new firmware I have the same problem, the accelerometer and altitude meter do not work.

I read in another post that to be able to use the Wireless BSL update, you have to update the  RF Access Point that comes with the Chronos using an external debugger that you have to buy. Investigating the Firmware Update Tool that I have used, it seems it also flashes some sort of update in the RF Access point, but the Wireless Update does not work after that.

I'm also interested in firmware to make the Chronos work again, either newer or older (the one I have now, according to the Firmware Update Tool is 1.5)...

Thanks in advance!

Same problem here with the 868Mhz version. Need an advice to reset the firewall. Accelerometer, Altitude and Syncfunction doesnt work (wireless Update didn't work too)

Hi,

Same watch here (433Mhz), same problems.

Fortunatly I did a firmware dump with mspdebug before doing anything.

You can find it here : git@github.com:jcsaaddupuy/ez430-original-firmware.git

You'll be able to flash it with mspdebug.

mspdebug -q rf2500 "prog ez430.hex"

This won't work for other frequencies than 433Mhz.

And also, I'm very interested in having the new firmware/Drivers or at least some informations about the new hardware...

I'm very interested in programming this watch, but loosing functionalities by just writing a Hello world is not an option :)

Same with me but the documentation says that there is no need to update for the equipment after April 2010, I believe. Ours is from January this year.

I have another question. I bought the 433 version because it said worldwide but, as I live in Europe, I should habe bought the 868 version. I still have got a clear answer from TI on this matter but it seems that, for example, Zigbee components work with 868 in Europe and I will not be able to communicate. Is this so ? Can someone please enlighten me ?

Thanks

Rogerio Neiva said:

I bought the 433 version because it said worldwide but, as I live in Europe, I should habe bought the 868 version.

However, 433 is quite crowded and it is even allowed to permanently send on 433MHz. On 868, only one channel is allowed for 10% duty cycle and all others are 1% or even 0.1% only.

Rogerio Neiva said:

Zigbee components work with 868 in Europe and I will not be able to communicate. Is this so ?

Hey all,

Same here with a white-PCB version 915 of the Chronos. I was still able to get the Control Center software working on my Mac (OSX 10.8 Mountain Lion) using old instructions, but the wireless update does not work there, either. I just wanted to update to a version that would do stuff like display seconds along with the time or display the day of the week, but both the Windows and OSX/Linux version of the Control Center say "Failed to start wireless update."

Is anyone getting any help on this? Kind of sad when one of the coolest aspects of the watch doesn't work at all.

Alternately, any clear instructions on flashing using the other dongle (I assume that is what I can do?) Do I just Flash a text file the same way the wireless would do it, but disassemble the watch and use the emulator dongle instead? I have various tool-chains installed (CCS, MSP430-GCC, etc.) but am still brand new to this. I've used Energia to program the MSP430 Launchpad chips, I just am not sure what the easiest step-by-step is for the Chronos. I don't mind getting my hands dirty on this, but currently, as a hobbyist, I don't really know where to start.

Thanks,

JoeK

After catching up on the Wiki I answered a bunch of my own questions.

I can use the BM Uploader to update the BSL firmware and the "regular" firmware on the watch by taking the watch apart and using the USB dongle (the non-RF one). I was NOT, however, able to have the RF update and regular update run at the same time if I used any other firmware than the ones provided by the BM tool (I edited the script and got other firmwares on there). So, the wireless and regular firmware are now the latest as found in the Chronos Console folders, but I had to apply them separately. I was able to comment out Step 4 and then Step 5 and it said it was successful.

Wireless updating from the console still throws the "Failed..." error, though. And now if I go to the rfBSL option on the watch, click down to "Conf" and then down once more, it hangs at the "run" screen. Total lock. I just take the battery out and out it back in and things are back.

Acc and Sync work (but those worked before, too). Calibrating the temperature seems odd. When I use values between 70-75 F, the watch saves but temperature stays at around 67F. If I then set the temp to 77F and sync, the temperature jumps up to 77 on the watch.  ???  So, unless I get the watch to 77F (in reality), it is hard to get it to sync. The whole temp sensor seems a little flaky overall, but without being able to do some sort of ice water calibration, I don't suppose it is that easy for a one-point calibration to do much good.

I'm not sure how good the altitude is, either, but before it seemed to keep creeping up, while now it is staying put (so far).

Anyway, I am able to flash the watch (the hardwired way) and still at least have Sync working after that. I'll see if I can get OpenChronos or OpenChronos-ng compiled and try loading one of those sometime...

Thanks,

JoeK

Hello,

I got a ez430 chronos 433 MHz, no CD and the rfbsl updater did not work. The bm update tool FET error.

Did you found a solution?

Thanks

Nope, I never did find a solution, wireless still doesn't work.

I can use the BM tool to get new firmware on the watch, though, when taking it apart and using the physically hooked-up solution. Though, I think now if I try to activate rfbsl at all, I get a hard lock-up (removing the battery and putt it back gets it reset)...

I'm enjoying the watch, and we'll see what OpenChronos-NG comes up with. I might flash that on there when they have an official release (and I can get it compiled  *smile*).

Thanks,

JoeK

Hi guys,

I'm experiencing the same error situation. I got a 433MHz chronos (production date is 01/2013, PO 4512156074) which works fine with the preloaded firmware, communication with the Chronos Control Center 1.2 (newest download from TI) works stable in ACC and SYNC mode, but wireless update does not!

After selecting the firmware file and a click on the "Update Chronos Watch" button the text "Status: Starting wireless update" shortly appears, but then it states "Status: Failed to start Wireless Update". As it is independent of the state of the watch, e.g. if it's showing the time & date or is in rFbSL-Mode, I suppose it's a problem with the firmware of the RF stick.

Any suggestions to get the wireless update working?

Thanks in advance,

TFR

I too am having the problems everyone is describing. I was able to load the original firmware after installing another version. This got the acceleration and pressure sensor working again, but wireless update never has worked. I'm going to try some more stuff when I get home

Thanks,

John

Hi,

I posted a service request (#1-1018302483) related to our wireless update problem to get an answer from TI directly, but:

(1) The first answer was a template, of course completely without any information related to the request:

"... In order to resolve your inquiry, we would advise you to utilize the knowledge and experience available on our e2e forum.  Our e2e community is constantly reviewed and managed by TI specialists according to product and is further supported by over 50,000 engineers from around the world sharing their knowledge and experience.  If you are already a member of our e2e community, you can post your question directly on our MSP430 Ultra-Low Power 16-bit Microcontroller Forum. If you are not yet a member of our e2e community, please click here and follow the instructions to become a member. Please visit also our EZ430-Chronos Wiki page, where you can find there information about hardware, development software and accessories, discussions and much more on the Chronos Watch..."

(2) After asking if they were trying to kid me the answer was:

"... I am very sorry you feel that way, but the advices you received in our template are the only ones I can give you, as we don´t have available engineer for support of this product. You can also send a reminder on the E2E forum..."

So, unfortunately it seems that we are on our own for the time to come...

Until TI finds someone who knows about their product...

In the meantime: Did anyone find out the cause for the wireless update failure? As I read in the watch's manual, the chronos control software has to be started, and after the wireless update is initiated by the software talking to the RF stick the watch has to be put into rfbsl mode. Since my software fails to start the wireless update procedure, I suppose it's a problem between the software and the RF stick firmware, not a problem of the watch itself.

Does anyone know: Is an older chronos control software available that works with current RF sticks, or the other way, does the current software work with older RF sticks? Or has anyone written some home-build software to do a wireless code update?

Well that's helpful. :(

Has anyone tried updating the firmware for the dongle? I'm not sure how to go about that, but I've seen mention of it somewhere. Maybe we somehow got a batch of old dongles with an older firmware on them?

I emailed one of my friends who used to work for TI and he said we probably won't get help anywhere but here. He did say that the engineers do visit the forum and try to answer questions on a regular basis, and are encouraged to by the company, so maybe we can keep this thread near the top for max exposure. This seems to be limited to very recent watches. Do any of us with the problem have one that's older than 2013?

JTD

I was under the impression this issue is only with the newer "white" PCB set for the Chronos (assuming the white is indeed newer). I also assumed several folks bought this when there was a TI Deal for it (recently, all in 2013), and that deal seemed to consist of TI sort of "re-issuing" the product (or simply clearing it from inventory -- who knows).

That's why I bought it, anyway, and everything except wireless firmware updates appears to work for me.

To be honest, if the lower half of the watch had a mode where it would show seconds (at the same time the top showed hrs/min), that is all I want.  *smile* I want to see hours, minutes, and seconds, together, by default -- having the seconds off on it's own (and only as a secondary display) makes it clear that engineers designed this thing.  *smile*

...just doing my part to keep the thread active!

JoeK

Hi again,

I've done some investigations (and had a bit of "luck" because TI delivered 2 watches to me that have production codes which are 3 years apart from each other):

With my Chronos Control Software installation (running on Windows 7 32-Bit) that is currently linked at the chronos wiki homepage as version 1.8 (but says version 1.2 in it's window title ;-), the situation is as follows:

- The software completely works with a 868 MHz RF stick delivered together with a black PCB chronos, production code 52/2010. Wireless update works stable.

- The software works only in ACC / PPT / SYNC mode with a 433 MHz RF stick delivered together with a white PCB chronos, production code 01/2013. Wireless update does NOT start at all.

Another member of this forum gave me some advice pointing in the same direction, that older chronos sets work, newer do not: http://e2e.ti.com/support/microcontrollers/msp430/f/166/p/265185/928875.aspx#928875

Conclusion: It seems to be a firmware bug of the RF sticks of the newer chronos sets... Maybe TI manufacured them using an older firmware version... Unfortunately I do not have a CC debugger to verify that thesis (yet ;-). Maybe some other forum member could test if the wireless update works after doing the RF stick firmware update procedure as described on the chronos wiki page?

Tobias,

Thanks for the concise summary -- it is the same experience for me (white PCB). Everything works in the control software except the rfBSL firmware update.

If by updating the RF firmware you mean the operation the BM Updater software CAN do, I have updated the RF on the watch. It didn't appear to help. Hm, though actually I may have been updating the firmware on the other stick, the hard-wired loader? Not sure. The page at:

http://www.bm-innovations.com/index.php/ez430-chronos

has the program and instructions, and it is all about the hard-wire stick being hooked to the watch. This is the script text for a 915 watch:

==========================================================

// Test 1:  Init FET
TEST_START;                      Init FET and identify device for programming;
MSP430_INIT_FET;
TEST_EVALUATE;            testresult;==;1;AUTO;BREAK;

// Test 2:  Erase main memory (and keep info memory with calibration values)
TEST_START;                      Erasing main memory;
MSP430_ERASE_MAIN_MEMORY;
TEST_EVALUATE;            testresult;==;1;AUTO;BREAK;

// Test 3: Erase BSL memory
TEST_START;                      Erasing BSL memory;
MSP430_ERASE_BSL_MEMORY;
TEST_EVALUATE;            testresult;==;1;AUTO;BREAK;

// Test 4: Program BSL firmware
TEST_START;                      Programming BSL firmware;
MSP430_FLASH_BSL_MEMORY;  firmware/ez430_chronos_rfbsl_915MHz_1_0.txt;
TEST_EVALUATE;            testresult;==;1;AUTO;BREAK;

// Test 5: Program watch firmware
TEST_START;                      Programming firmware;
MSP430_FLASH_MAIN_MEMORY; firmware/ez430_chronos_915MHz_1_5.txt;
TEST_EVALUATE;            testresult;==;1;AUTO;BREAK;

// End of test
MSP430_CLOSE_FET

==========================================================

(and it all works, you can even run the updates separately, and can replace the firmware files with whatever you want to try.)

In looking at this again, this all appears to be for the watch, firmware for the RF boot-strap loader and then the main firmware for the watch. I was able to update the main firmware to a couple other custom firmwares (and could see the differences in the watch), but none of them made the rfBSL update work any better from the Control Center. Lack of success ranged from the standard error we are all seeing to initiation of the rfBSL stack on the watch leading it to be completely locked up.

What none of this addresses is the firmware on the wireless access point dongle. It is apparent it can communicate as evidenced by Acc, Sync, and Ppt working. There's just something awry with the wireless update aspect, and I am not sure how to change the firmware on that stick.

Thanks,

JoeK

Hi Joseph,

thanks for that information. That points out into the same direction I mentioned in my post before, that it's not a problem of the watch, but of the combination of chronos control software and the RF USB stick that is delivered with the current chronos sets.

I came to the same conclusion because the chronos control software initializes the update procedure using the old USB RF stick, even if the addressed watch is not in range. Using the same software with the RF stick of the newer chronos set results in the initialization error mentioned in the previous posts.

So, yes, it seems to me to be a firmware problem of the USB RF sticks, maybe some functionality that's only used by the rfBSL procedure of the chronos control software is not implemented there.

I can't completely compare my old an new chronos set, because I got an old 868 MHz version, and a new 433 MHz one. The RF sticks look completely different, not only the antenna geometry. It seems a bit strange to me that the older 868 MHz stick is a one-chip-solution using a CC1111 SoC, and the stick of the newer 433 MHz set is nearly twice as big (ok, due to the bigger antenna), using 2 major chips, one is a CC1101, the other may be a M430F5509, it's hardly readable.

433 MHz: NOT working in rfBSL mode: PCB version is BM-USBD5-V1.1, 2 Chips (CC1101, M430F5509)

868 MHz: rfBSL mode OK, PCB version is BM-USBD1-V1.3, 1 Chip (CC1111).

(1) Could all of you who have other working / not working RF sticks be so kind to post their PCB version and chipsets (if they differ from mine)? Maybe we can get a pattern out of that information which PCB versions, chips, etc. are working or not...

(2) Has anyone updated the RF stick firmware using a CC debugger, and tested the rfBSL update after that?

Greetings,

TFR

Excellent point about the older RF access point initializing (without error) even when watch is not in range. Point the finger pretty squarely at those couple square inches of PCB.  *smile*

Thanks,
JoeK

I also have one with a date of 01/2013, but a 915 MHz model.

I am able to update the watch using the hardware method and continue to have no sucess with the rf update method.   I am working under the impression that its a hardware/software problem with the RF usb dongle.  I am now working to update it to current code from software just released in 04/2013.

Joseph Kaufman said:

having the seconds off on it's own (and only as a secondary display) makes it clear that engineers designed this thing.

The fact that the seconds are a separate mode shows that there were 'software designers' at work. The job was to show hours, minutes and seconds. And there was no explicit requirement to show them all at once. So the resulting software shows hours, minutes and seconds, fulfilling the expressed (but not the implied) requirements, even if the result is not really usable.
(It's surprising that hours and minutes show up simultaneously).

Hi,

im also hawing this watch(model 868, seal dt 02/09/13,white PCB), and also the same problems (no wireless update, nor in Win nor in Ubuntu). I was able to update the watch firmware using http://www.bm-innovations.com/index.php/ez430-chronos  and virtual machine running WinXP SP2 x32. But after the update the thermometer and barometer didn't work. :( Then I performed the hack like approach(mentioned by Joseph Kaufman) to flash the watch whit openchronos-ng (compiled under ubuntu -> http://sourceforge.net/p/openchronos-ng/code/ci/master/tree/ ) Now I have at least working thermometer and the clock should be more accurate  (http://sourceforge.net/p/openchronos-ng/wiki/Feature%20matrix/) but by by barometer,accelerometer and remote ppt control, but also by by annoying hard meter,speedmeter,calories. 

I don't understand how did they plan to make this watch "attractive development kit" "to increase the accessibility of flexible and innovative development systems to a broader audience" if it is so hard to update ?

Hi,

I'm one of the customer impacted by the "failed to start wireless update" control center message.

Is there any chance to get the wireless update working ? it is a major feature of this development system, and without it, the interest of the system drops dramatically.

Additionaly, watch buttons do not work when device is powered by msp-ez430 usb stick.

In this state, this development system is frustratingly quite unusable. not a big deal for the money involved, but a big deal for the waste of time, where projects are stucked.

It would be nice from TI to let us honestly know if this system is still supported or not, so that we can move to something else.

Thanks a lot

Bruno

I too am still having the same problems and the same doubts about TI's support of this product. 

5040.ez430_chronos_433MHz.txt

compiled latest from sources V1.7  for eZ430-Chronos v1.1 - white PCB

altitude meter , accelerometer  are working 

Hi, 

Please i have the same problem for wireless communication and wireless update with ez430-433 chronos watch and i even use chest strap to communicate with watch but it fails.Did anybody got the solution

I've got a new Chronos in the Black Friday deal, the 868MHz with the white pcb, and was also having troubles updating via wireless.

But I found the solution and think this is the right place to share as this thread was one of the first google results while looking for it.

I had to update the RF Access Point firmware with the version included with the latest Control Center (included in the "Recovery" folder). It has to be done using the Ez430 Programmer. I got the drivers for it from the IAR kickstart (under "drivers\TIUSBFET\eZ430-UART\" if you don't want to do a full installation).

Connect the RF A.P. to the Programmer as shown in the page 46 of  the "eZ430-Chronos User's Guide" included with the Control Center. I managed to get a good connection without soldering the header to the RF A.P

I've then used the Eloptronic's Lite FET-Pro430 software for programming. Then it's just opening the correct version firmware, select the MSP430F5509 Microcontroller and click  "AUTO PROG". Done! You can now do wireless updates.

Thanks!

I've successfully upgraded the RF Access Point with mspdebug under Linux (Ubuntu 12.04) and now Wireless Update works:

$ mspdebug rf2500
...
(mspdebug) prog Recovery_eZ430-Chronos_AP_868MHz_2_2-white_PCB.txt
Erasing...
Programming...
Writing 4096 bytes at a000...
Writing 4096 bytes at b000...
Writing 4096 bytes at c000...
Writing 4096 bytes at d000...
Writing 3717 bytes at e000...
Writing  340 bytes at ee86...
Writing   46 bytes at ffd2...

no need to install anything else than mspdebug (the version shipped with Energia works just fine), the firmware can be found in the SLAC388, choose the one that matches your AP frequency.

http://www.ti.com/lit/zip/slac388

Hello, I have tried to upgrade my RF Access Point using mspdebug under Linux Fedora 18.

I get the following error :

$ ./hardware/tools/msp430/bin/mspdebug rf2500
MSPDebug version 0.20 - debugging tool for MSP430 MCUs
Copyright (C) 2009-2012 Daniel Beer <dlbeer@gmail.com>
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Trying to open interface 1 on 013
rf2500: warning: can't detach kernel driver: No such file or directory
Initializing FET...
FET protocol version is 30394216
Configured for Spy-Bi-Wire
Set Vcc: 3000 mV
Device ID: 0x3a80
fet: unknown device
msg28_data: [0x1a bytes]
    3a 80 12 12 08 0a f4 bf 93 46 15 00 1e 00 f8 fe
    ef ff 91 04 11 00 1a 00 04 05
fet: identify failed
Trying again...
Initializing FET...
FET protocol version is 30394216
Configured for Spy-Bi-Wire
Sending reset...
Set Vcc: 3000 mV
Device ID: 0x3a80
fet: unknown device
msg28_data: [0x1a bytes]
    3a 80 12 12 08 0a f4 bf 93 46 15 00 1e 00 f8 fe
    ef ff 91 04 11 00 1a 00 04 05
fet: identify failed

Any idea of what I am missing?

Alessandro Pasotti : can I have the log of what you get when you launch the mspdebug command?

Thanks in advance.

Hi,

sorry but after being sure that it was working, I de-soldered the small connector from the programmer and I didn't made a copy of the logs.

I remember having seen some errors when mspdebug started but at the end it worked. Sometimes it takes several seconds to attach the driver and sometimes it works on the second run.

Hello,

Congratulation for your results, I have a recent 433 mHz watch (february 2013) so a white pcb one. I would like to ask you two things:

- Can you send me the firmware 433 for the RF access point, I installed and uninstalled the control center multiple times without finding it, so if someone could post a link I would be really grateful.

- If I understand the whole problem, it is basically a problem in the access point firmware so we have to change it: We take the new firmware, connect the RF programmer to the access point. Then we install the software Eloptronic's Lite FET-Pro and set the programming parameters for the MSP430F5509, open the firmware and it should update it on the access point using the programmer after we click on AUTO PROG. Did I misunderstand the problem somewhere?

Thank you very much, it will help me a lot as an electronic student

Christian

I've added the firmware to my profile: http://e2e.ti.com/members/3904187/files/default.aspx

You could find it in the control center install directory: "C:\Program Files\Texas Instruments\eZ430-Chronos\Recovery\RF Access Point\" (or "C:\Program Files (x86)\..." if 64bit windows).

You understood the solution correctly. You're only missing that you have to install the drivers for the programmer. They're available with the IAR kickstart: http://www.ti.com/tool/iar-kickstart

Perfect. Now I can update wirelessly.

Did these steps (see posts in this thread):

- solder programming connector on access point (connect the CORRECT way to programmer, seems reversed)

- installed mspdebug

- run 'mspdebug rf2500' as root and 'prog <file>' to accesspoint

Thanks all!

Jos��� Ara��� said:

I've added the firmware to my profile: http://e2e.ti.com/members/3904187/files/default.aspx

Use MSPDebug version 0.22

Hey

I have a recent product (white board).
I have doubts about the connection between the emulator and the AP. There are 6 pins on the emulator and only 4 on the AP. Which of the 6 need to be connected ? If I trust the page 46 of user's guide, that would be pins 2-5. Can anyone confirm or invalidate this ?

Also, I'm not sure how to install the driver for the emulator.  Wasn't it installed during Chronos control center installation, at the same time as the ones for the AP ? If not, where can I find the driver for the emulator ?

I have only a basic knowledge of electronics and IT, sorry if I'm not clear.

Thank you

Thanks a lot! That totally worked.

Now, I am able to do wireless update without any problems.

Jos��� Ara��� said:

I've got a new Chronos in the Black Friday deal, the 868MHz with the white pcb, and was also having troubles updating via wireless.

But I found the solution and think this is the right place to share as this thread was one of the first google results while looking for it.

I had to update the RF Access Point firmware with the version included with the latest Control Center (included in the "Recovery" folder). It has to be done using the Ez430 Programmer. I got the drivers for it from the IAR kickstart (under "drivers\TIUSBFET\eZ430-UART\" if you don't want to do a full installation).

Connect the RF A.P. to the Programmer as shown in the page 46 of  the "eZ430-Chronos User's Guide" included with the Control Center. I managed to get a good connection without soldering the header to the RF A.P

I've then used the Eloptronic's Lite FET-Pro430 software for programming. Then it's just opening the correct version firmware, select the MSP430F5509 Microcontroller and click  "AUTO PROG". Done! You can now do wireless updates.

It is pins 2 to 5, just as it is shown in the picture.

You can get the drivers for ez430 programmer in IAR Kickstart under '\drivers\TIUSBFET\eZ430-UART'. 

These drivers won't get installed with the Access point driver setup.

Emilien Rubattel said:

Hey

I have a recent product (white board).
I have doubts about the connection between the emulator and the AP. There are 6 pins on the emulator and only 4 on the AP. Which of the 6 need to be connected ? If I trust the page 46 of user's guide, that would be pins 2-5. Can anyone confirm or invalidate this ?

Also, I'm not sure how to install the driver for the emulator.  Wasn't it installed during Chronos control center installation, at the same time as the ones for the AP ? If not, where can I find the driver for the emulator ?

I have only a basic knowledge of electronics and IT, sorry if I'm not clear.

Thank you

The way I see it: TI has taken our money and delivered a product that DOES NOT WORK AS ADVERTISED! Period.

To add insult to the injury, they didn't bother to get their act together and put all the drivers/software/how-tos in one place.

Do the words "shame" and "deceit" ring any bells at TI?!

Thank you :) Worked perfectly :)

Jos��� Ara��� said:

I've got a new Chronos in the Black Friday deal, the 868MHz with the white pcb, and was also having troubles updating via wireless.

But I found the solution and think this is the right place to share as this thread was one of the first google results while looking for it.

I had to update the RF Access Point firmware with the version included with the latest Control Center (included in the "Recovery" folder). It has to be done using the Ez430 Programmer. I got the drivers for it from the IAR kickstart (under "drivers\TIUSBFET\eZ430-UART\" if you don't want to do a full installation).

Connect the RF A.P. to the Programmer as shown in the page 46 of  the "eZ430-Chronos User's Guide" included with the Control Center. I managed to get a good connection without soldering the header to the RF A.P

I've then used the Eloptronic's Lite FET-Pro430 software for programming. Then it's just opening the correct version firmware, select the MSP430F5509 Microcontroller and click  "AUTO PROG". Done! You can now do wireless updates.