• State
  • Locked Locked
  • Replies 8 replies
  • Subscribers 54 subscribers
  • Views 1715 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Driver problem with IAR EW 8.10 and CC2530/RF05EB

Andrew19474
Intellectual 780 points
Other Parts Discussed in Thread: CC2530, CC2530EM

I had been using CC2530 and RF05EB using Windows 7 x64 and had been having intermitent driver issues when downloading and/or debugging.

I was instructed to install the new TI win7 x64 drivers which I did and as far as the OS is concerned these appear to be correct and in order and the devices are connecting and disconnecting fine.

I was advised that to get EW 8051 to recognise the new driver(s) I must install a particular patch OR upgrade to version 8.10.

I upgraded to v8.10 and now the problem seems to have worsened.  The driver errors are now consistent rather than intermittent and I have not once managed to load programs or debug.

Does any one have any ideas what I may be doing wrong or may have left out?

Thanks.

  • 0
    Guru 31280 points

    Hi Andrew,

     

    What exactly are the errors you seeing?

     

    Br,

    Igor

  • 0 in reply to Igor Sherer
    Intellectual 780 points

    Actually to be fair, I am getting slightly different errors now:

    1. Fatal error: Failed to initialize communication.  Check connections and hardware
    Session aborted!

    OR

    2. Drive message box remains for ever, application not responding

    I just tried another board and that seems to be working ok.  Sometimes the debugging is very slow performance, but I am so far not getting the intermitent failures I was getting with v7.6 and the old drivers.   However the first board is recognised by the OS.  The LCD looked dim, so I switched to usb power, but the same failures occurr.  I tried the reset button, but no avail.

    EDIT#1: Since this occurred I have used TI's Flash programmer (which recognised the connected boards) to update the Firmware on both boards

    Could this be a permanent problem with the board that some how is only picked up EW or do you think there may be a solution?  Or at least some kind of other confirmatory test I could make?

    Thanks

  • 0 in reply to Andrew19474
    Guru 31280 points

    Hi Andrew,

     

    Since you familiar with the flash programmer... Have you tried to download a FW

    to cc2530EM using the programmer and the more important question, do you

    experiencing the same problems with the programmer?

     

    Br,

    Igor

     

  • 0 in reply to Igor Sherer
    Intellectual 780 points

    To be honest, I'm not really that familiar with Flash Programmer.  I just wondered if anything else could see the board and so I thought of the flash programmer and on start up the sfw directed me to single click upload the latest firmware, which I did successfully on both boards.

    However I shall definitelt try to do what you suggest.

    Is it pretty clear to use, or do I need some pointers?  Do I need to use the d51 and map file as some kind of input to some other 'process' first and use the output of that 'process' to flash?

    I'll take a look at the guides.

     

     

  • 0 in reply to Andrew19474
    Intellectual 780 points

    Ok,

    I uploaded the cc2530 sniffer hex image.

    Imediately after that, close flash programmer, reopened the exact same ew project rand download and debug and it all worked fine. (at the moment ;-) )

    When previously working, I would always get driver not responding briefly and then ok, I guess that's just some kind of lag on my system.

    Does any one have any thoughts on why this may (causally or conicidentally?) have fixed it?  If so, it may just help my understanding for future bizarre behaviour.

    Many thanks

  • 0 in reply to Andrew19474
    Guru 31280 points

    Hi Andrew,

     

    My guess, previous FW download gone wrong.

     

    Br,

    Igor

  • 0 in reply to Andrew19474

    1. Fatal error: Failed to initialize communication.  Check connections and hardware Session aborted!  

    always it is usb problem.

    it may be the drive problem, when i open a sample by the Packet Sniffer ,TI,the driver has no problem ,but after this when i debug by IAR V7.51 ,the reeor occurs,

    the debug driver updataed (IAR v 810), so i   select  the older   driver ( V 7.51) .


  • 0 in reply to pengbo zhao
    Guru 31280 points

    Hi,

    You have a backward comparability.

    What exactly you are trying to debug? What sample poject (from what version of stack) with what

    version of IAR compiler?