Keyfob configurable as "Network processor"?

The HostTestRelease is the project which implements a Network Processor. This has to be flashed on the dongle. The application side is implemented by BTool.

In order to configure the UART, I think you can program a CC2540EM with the HostTestRelease and specifying the CC2540EM configuration.

"has to be flashed on the dongle" ... "program a CC2540EM"

I can't quite decode what you're saying. What I was asking about was the keyfob.

Also, I was looking for specific steps (since this seems to be a common request here): I simply want to add BT LE to an existing (unrelated) embedded project.

The keyfob has extra I/O lines already wired the unused header, so it would be perfect for testing purposes.

To me, the "network processor" configuration is the way some of us would like to evaluate the CC2540... even the way to use it in a production device!

Ideally, somebody already has a hex file for this "network processor" configuration on the keyfob. I'm surprised it wasn't in the TI-supplied hex files.

The keyfob is practically the same as the dongle but with some peripherals.

If you want specific steps, you will not find any guide, perhaps you can use several posts altogether, starting with:

http://e2e.ti.com/support/low_power_rf/f/538/p/116809/470842.aspx#470842

You can install the IAR evaluation version and open the file in:

C:\Texas Instruments\BLE-CC2540-1.1a\Projects\ble\HostTestApp\CC2540

Make the UART changes, compile and flash.

The TI solution is adaptable to a lot of types of apps, so they provide general applications the user can adapt and restrict.

Bye.

Thanks for the reply.  I found that post (and all the others) that deal with this question, hence my post.

Hey TI guys, this is for you: Why not make it easier on those who want to evaluate adding BT LE to their existing designs? You've already gone most of the distance with the user-friendly mini devel kit, and the super-helpful forum!

Granted, the CC2540 mini eval kit is for professionals, but this professional is up to his neck in other embedded projects, with no one else available to create a working/tested network controller configuration.

I will be spending many hours understanding the HCI as it is... why make it even harder by requiring setting up an (expensive or temporary) devel system to even get to the first step? Just setting up a new devel system typically takes 1-2 (even more) days. I only need to make a case to mgmt to commit to the TI part, not do a complete science project!

The HCI documentation states that a serial connection is the main use case for using HCI.... so where's the support?

I will be checking out BlueRadio for external access to the HCI functions. Seems like someone gets it.

Forum posters, this is  for you: I would be willing to pay someone for a hex file that allows the keyfob to talk to another microcontroller using a serial connection, and I think others might too, judging by the posts on the issue. Any takers?

:)

I would take the offer but I have plenty of job. Good luck and nice proposal. You can create also a wiki entry to ease the work for incoming posters :) Meanwhile, perhaps you can mark the answer as validated in order to have a cleaner forum.

Bye Andy!

Thanks, Willis. That's a fair answer for now.

Looking forward to the improvements, but nervous about my time-to-market.

(My project is due before 6 months)

So, how did it go? I also need a finished hex file for the network processor using a physical UART.

Or if I must do it by myself where do I start?