Softdev 132 questions

[scrungy_doolittle]

I am struggling to understand how to use a Soft Device 132 on a BT832 fanstel part. I need to have the uart come out on pin 1 and 2, and have hardware handshaking enabled. I cannot find which I/I pins are available under the softdevice 132. The desired configuration is a hardware controlled uart, with a connect signal on an I/O pin, a Sleep status signal on an I/O pin, a DATA/CMD input pin that will put the device into command mode for AT commands, and data pass through mode, and a DATA ready output pin. In this configuration, I believe I can replace the RN4020 module that we used in a prior failed product. The fanstel firmware has no source, and no documentation. They have hex file BT832_AT_3in1PC18113.hex which says it has soft device 1320v6.6.6 +BT832_AT_UART without 32k buffer+bootloader. But no information on how one could use it. Ultimately, the goal is to have code running on the BT832, that controls another device, with a serial port, and I/O lines.

What pins are available on the SD132 when using a 52832 device?
How do you configure them?
How can you add custom code to the soft device?  Is there a tutorial somewhere?

And how do I do a soft reset?

How do I manage to reconfigure the code so that the uart is mapped to two of the castellated pins (1 and 2) and that the uart has hardware flow control brought out to a pair of pins on the castellated package. 

The BT832 castellated pinout   1= SDA 2=SCL 3-4 xtl 5 =P002, 6= P003 7=NFC1 8=NFC2 11=P013 12= P018 13=P020 14=P021 15=SWCLK 16=SWDIO.

[scrungy_doolittle]

The PCA10040 h file applies only to the dev board.

The issue right now, is that I am not developing code, rather I am *working on a schematic*.  I want to set the BT832 up in a similar way to the RN4020 initially, so that it functions as a simple bluetooth uart, at 115,200 baud, with hardware handshaking.  Once we have it running, then I want to add code to the module, to capture all traffic in from the bluetooth, and manage what goes out to the bluetooth.  The device that it is connected to, will periodically transmit status information to the BT832 over the serial port, using a hardware delimited protocol (The BT832 will have to monitor a line, and that should generate an interrupt).  The BT832 will then repackage the information into a packet to send to the bluetooth link. In addition it will accept command packets from the bluetooth, manipulate them and repackage them to be sent to the uart to the device under control.  I need a certain number of input and output linesI prefer to use the castellated pins so we don't have to try to deal with the LGA pins. Lines needed other than the TX/RX lines, are   connect output, true when something connects, a reset line to reset the module, a CMD/DATA line, a line  for a hardware delimited packet (i.e. the line goes high, the packet goes out the uart to the bluetooth, and then the line goes low.  A second handshaking line for a status line to indicate the length of the packet.  A line that tells me when the device is in sleep mode, and a line that can wake the device out of sleep mode.  That is 6 I/O pins. Near field communication is nice, but not necessary.  Our assembly house can build the LGA connections, but it would be nearly impossible to replace the module if we went that route.

I was not talking about modifying the bluetooth stack, but adding user application code later, such that it can capture all bluetooth traffic, enforce limits on who can connect, and control a secondary device.  I don't understand the mechanics of doing that.

More importantly, I cannot find any information on what pins on the nRF52832 are tied up by the bluetooth stack.  Does it use a pin for connection status?

Does it use rts/cts for it's uart?

What determines the pin usage on the module (which while it is not a nordic module, IS based on a nordic nRF. 

[awneil]

scrungy_doolittle said:

The PCA10040 h file applies only to the dev board

You would create your own version for custom hardware

scrungy_doolittle said:

I cannot find any information on what pins on the nRF52832 are tied up by the bluetooth stack.

AFAIK, It doesn't use any - other than dedicated pins like antenna, crystal, etc.

Again, the way to prototype this & work this stuff out would be with a DK ...