I recently purchased the XBee Pro programmable dev kit (XBP24-BZ7B-DK). I followed the getting started instructions found in the document titled “Getting Started Guide - XBee-PRO® ZB Programmable Development Kit”.
I was able to get all the devices recognized by windows. However, I was not able to load the boot loader into the module.
Whenever I “run” the program, an error window “Power Cycle Dialog” pops up.
It says: “The target MCU is not responding. Please turn MCU power off…”
I tried to on and off the development board, debugger, etc, but the error message still pops up.
Yes, I am following the procedure described by you. However, after i had OFF and ON the power to the development board by extracting and then attaching the USB cable, the same “Power Cycle Dialog” shows up again.
Hi shsh, did you solve this problem? If so, it would be nice to tell us how you managed it and what the problem was.
It’s normal to see that dialog but not continuously. I remember I had a similar problem but it was because the program was setting the XBee in Sleep Mode inmediatly after power-on, so I solved it pushing the commissioning button.
Does this only happen when trying to flash a bootloader or with any other example?
Another thing you may try is pushing reset button instead of power-on/off (sometimes, it works).
I have unstalled CW 10.1 and installed CW 6.3 but the same message appears. It ocurrs either in coordinator API or router API firmware. So, does not depend on the sleep mode…
Any other comment or advice will be very appreciated! Thank you!
Are you using the Programmable XBee Development Kit?
When launching the project in CW10.1, what do you see in the Console view? Is it something like this?
Info: Windows NT detected.
Info: USB HCS08/HCS12 MULTILINK detected - Flash Version 5.84
Info: Frequency change to ~0hz.
Info: Frequency change to ~0hz.
Info: Frequency change to ~0hz.
Info: Frequency change to ~0hz.
Info: Frequency change to ~0hz.
Info: Frequency change to ~0hz.
Info: Frequency change to ~0hz.
Info: Frequency change to ~0hz.
Error: Can not enter background mode.
Info: Frequency change to ~0hz.
Info: Frequency change to ~0hz.
Info: Unable to initialize PEDebug.
Have you checked the debugger is correctly attached to the XBee Interface Board? The red cable of the ribbon cable corresponds to the Pin 1 of the debug connector.
If it is correctly attached, could you post the part number of your XBee module? You will find it in the back side stick of the module. It should start with XBP24…
Anyway, the kit cames with 2 programmable XBee modules. Have you verified if the other module works?
Actually, I have a DigiMesh kit, and also I bought a programable ZigBee module XBP24. As the interface boards are the same, I use one of the boards with the programable module. As I only have one programable module I could not try the second. However, I will receive today another 2 new modules, so I can test these also.
In ever case, following the instructions to access the bootloaeder (using RTS and Break lines) I never get the expected console menu as you posted, but only three lines:
.EM250 Bootloader. v20 b09
.
.1. upload ebl
.2. run
.3. ebl info
.BL > .
When trying to upload a binary file using XModem, the file starts to upload but never ends to upload.
That is the bootloader of the radio chip, it seems you are not able to communicate with the programmable chip of the XBee module for any reason. It could be a hardware problem.
Anyway, just to verify your module is programmable, could you post its part number? but the complete number. I.E.:
I need to verify it, but I am afraid that part number does not correspond with a programmable XBee module.
I have here a couple of XBee modules with the following part number XBP24BZ7WIT-, and none of them are programmable. The programmable version of that module has this part number: XBP24BZ7WITB (notice the B). I think in your case it should be XBP24BZ7UITB, but I am not sure.
I’m almost sure you are right, this code seems to be for a non programmable module. The last letter should be a ‘B’. When I bought the module, I just look at the final numbers to be ‘003’ and not ‘004’.
You require making contact with and obtaining help from service provider, just calling them they will fix it. This message generally happens when you attempt to connect to the internet. The error come into view and the connection fails. Your hard drive is dreadful. You’ll have to obtain a new one.