CC2564C: Service packe problem

I have reboot (power off and re-power on) the CC2564 after the RF test. However, I still cannot run the sample code on the CC2564C

Is this issue resolved.. As, mentioned in the other post there is no Flash on the CC2564, upon reset the firmware patches need to be reloaded..'

Thanks

This issue is not resolved. Below is my testing procedure
1. Put the CC2564 EM on the STM platform and I can run demo code successfully
2. Remove the CC2564 EM from STM platform, and fly wire on the CC2564C EM (including uart port, shuntdown pin and power supply pin).
3. Use a FTDI usb to uart cable to connect the CC2564C EM to computer
4. Run the initscripts-TIInit_6.12.26.bts and initscripts-TIInit_6.12.26_ble_add-on.bts by using the HCI tool and then perform RF test.
5. Remove all the fly fire on the CC2564C EM and them plug the CC2564C EM to the STM platform. (During this step, all the CC2564 EM power pins and IO pins are disconnected and reconnect to STM platform.
5. The demo code cannot be run .

Humm.. It is not clear, what you mean by fly wire.
Can, you take firmware logs to ensure the device is properly booted each time?
processors.wiki.ti.com/.../CC256x_Logger_User_Guide

Thanks

Fly wire mean solder the wire on CC2564 EM uart port, shutdown pin, power supply pin, and connect to DC power supply FTDI usb to uart cable.

Attached please find the CC2564 log file

cc2564c.zip

I just plug the CC2564EM to the STM platform for above test (throught the on board connector). No wire soldering for above test

Hello,

Can you please attach a log file - so i can go over it and see exactly what could be the issue.

Chen

Attached please find the log file.

cc2564c_st_demo_code.zip

Hi,

According to the .lgr file you've sent you are not using the correct EM board.

The chip revision on this board is 7 - which means CC2564B and not CC2564C.

Chen

I have try both CC2564B and CC2564C. They has similar issue

Hi,

Please add the exact initscript you are using and the lgr file for that run.

From what i could see - you are trying to download a wrong initscript file to the wrong chip - which would not work.

Having said that - i could not see you download the initscript at all - which means the version running on the board is the one on the ROM device.

Can you please send an exact description of your system (exact parts) - don't even download anything as a first stage and the system should run fine from the ROM (it doesn't include any bug fixes).
Once we will get that phase working - the next step would be to make sure you are downloading the correct initscript.

Thanks,
Chen

Hi,
When we run the STM demo code, we don't need to download the initscript. Right? we just plug the CC2564EM to STM platform EVK, and start to run the demo code. (the log file I attached before is the case when I want to run the STM demo code
I run the .bts initscript only when I want to do the RF test. In this case, I run the initscript by using the HCI tool but not the STM platform EVK. ( I have not taken the log for this step because I can run the RF test sucessfully

Below is my testing procedure. The log file is taken at step 5
1. Put the CC2564 EM on the STM platform and I can run demo code successfully
2. Remove the CC2564 EM from STM platform, and fly wire on the CC2564C EM (including uart port, shuntdown pin and power supply pin).
3. Use a FTDI usb to uart cable to connect the CC2564C EM to computer
4. Run the initscripts-TIInit_6.12.26.bts and initscripts-TIInit_6.12.26_ble_add-on.bts by using the HCI tool and then perform RF test.
5. Remove all the fly fire on the CC2564C EM and them plug the CC2564C EM to the STM platform. (During this step, all the CC2564 EM power pins and IO pins are disconnected and reconnect to STM platform.
5. The demo code cannot be run .