Other Parts Discussed in Thread: CC2540
Hello,
I'm trying to develop an application that will allow control of a CC2540EM discrete module from an ethernet enabled MCU. I am using a slightly older DKLM3S9B96 board to do the serial to ethernet conversion, running modified code from the stellaris rdk-s2e module for doing the S2E conversion. The CC2540 module is connected to the main board's expansion header.
Using Tera Term, com0com, and com2tcp I am able to see serial data coming out of the UART port on the Stellaris board (UART1 module that I've confirmed to work on PD0/PD1 and PC6/PC7 for RX/TX). Connecting Tera Term to the virtual com port, and then to the board through com2tcp results in proper character output out of both the PD0/PD1 and PC6/PC7 UART ports, depending on which I've chosen to enable. Characters can also be sent back through the ethernet connection from another Tera Term terminal connected to the board's UART1.
The problem I am having right now is that BTool will not conect to the CC2540, or even show dumped packets. Keeing the UART connected to the PC shows no output coming from the UART when BTool tries to connect, when it sounds like some packets should be going through. Afterwards in BTool I always get the error:
GAP Device Initialization Timeout.
Device May Not Function Properly.
I've tried running BTool with both options of No Flow Control, and RTS/CTS enabled, making sure to set up the Stellaris pins properly to accept RTS/CTS flow control.
I've also tried flashing both the USB Dongle, and regular HostTest Applications onto the CC2540, which was the application that sounded like what I wanted.
So does anyone have any idea what could be going on? I find it really weird that the serial connection fails with BTool but not a terminal.
Please let me know if theres any more information I could add that might be helpful. I haven't spent too much time with the BLE side of things, and I know theres a lot links in the chain that could get mangled