I have been told for the past couple of weeks that I am doing something wrong and that is why I am not getting the best out of the SRF05EB Kits and IAR Compiler for the CC2540 chip.
I have given up debugging my modified software (of the SimplePeripheral project), have updated to Stack v1.3 and updated C compiler as much as IAR will let me..
I have taken IAR and TI's advice and ditched my efforts to develop on top of the reference designs and reverted back to demo boards and code, still no luck!
I'd like to know if anyone has had any success DEBUGGING with this setup.. By debugging, I mean set break points, read register values, step through the code etc....
I can compile - with no errors, Click Download and Debug in IAR, get as far as HAL_BOARD_INIT [in main()], run the code and Connect to device using BTool.
This is using the SRF05EB v1.8 with Evaluation Module CC2540DK_EM, connected to my PC/IAR via USB....
When I run the code, I can see 'Advertising' and using BTool I can connect and see 'Connected' on the LCD.
I can then query by UUID and extract Attribute-descriptions as follows (and this works)... Reading Characteristic UUID of 0x2901
I get:
Characteristic 1
Characteristic 2
Characteristic 3
Characteristic 4
Characteristic 5
I can repeat the above as many times as I want and get the above set of results....
When I attempt to 'WRITE Characteristic' to 0x0025 (change value of Characteristic 1), the system locks up.
[Note, when second SRF05EB is used as Central (Instead of BTool), this value Characteristic1 is incremented and displayed on LCD when joystick is pushed upwards - to demonstrate information passing from Server to Client...
I had been able to do this with my code (modified - adaptation of Simple Peripheral project for my project) before, at the time I was happy to build and generate HEX files and flash my test units.
When I got to a point of moving forward and developing code, I decided I needed the use of a Debugging Tool, so I bought a CCDebugger.
IAR has told me that CCDebugger is not recommended to Debug with IAR. They suggest using the SRF05EB as THE DEBUGGER TOOL of choice. After two weeks of to and fro-ing to IAR Tech Support, I told them what I thought of their Tech-support and they have stopped responding to my calls.
Now that they have my money!! Disgraceful Frigging Bandits!!!
TI has contradicted IAR's claims and neither IAR nor TI can provide any constructive input to solve the problems I am experiencing...
I would appreciate if anyone reading this post would help by writing a few lines in response to confirm or otherwise about your experience of using IAR and CCDebugger to develop and test, code with for the CC2540/CC2541 chips using the TI BLE v1.2 or 1.3 Stacks.
Ps.
I'm not stupid and have considered that this may be something to do with what I have or have not done but that is not the point. You expect a bit more than COMPLY COMPLY COMPLY (Pay for, register, don't calls us, use the forums, e-mail tech-support, endure the dongle and associated Licensing software, do exactly as we tell you to -register ..... ladida) before we even consider talking to you about your £1600 purchase AND by the way, keep telling us what is wrong with our products so that we can fix it and re-sell it to you in what we will call the next MAJOR update.....
I will NEVER use IAR Compilers or any other IAR products ever again.I have grievances against TI too, for allowing IAR to monopolize this range of RF ICs.....
Thank you.
