Hello Rony, i just checked with the development team : it will work fine with the BASIC kit as long as you have it running as a 2 wire UART (and not 4 wire). BR JE_Dialog.
I will start by simulating the uart and filling the input fifo myself to check the amount of data I can xmit every second through the ble. When that works I will add the uart interface which I am already using with my amateur implementation. I also use 2 wires. Thanks
Hello Rony, I have a call with the develoment team tomorrow to clear up the issue : 4 wire implementation is fine, but as per email, 2 wire I'm getting conflicting feedback. BR JE_Dialog
here is the feedback i have on running the DSPS with 2 wire on BASIC kit :
When running the DSPS keil application without a UART cable connected the software will run into the fault handler. The reason of the failure is that UART RX signal is in an undefined state. This is solved by changing the configuration of the pin from INPUT to INPUT_PULLUP: In file: periph_setup.c,
Function: set_pad_functions():
GPIO_ConfigurePin( GPIO_PORT_0, GPIO_PIN_5, INPUT_PULLUP, PID_UART1_RX, false ); // set UART Rx to input_PULL-UP
When testing between a DSPS device role and the Android phone application the tool does not recognize the default BDaddress.
Workaround:
In file: nvds.c; .NVDS_TAG_BD_ADDRESS
Workaround: Change the value to something else
The issue will be fixed in the next revision of the Android application
3)
When transmitting the value "0x00" from DSPS-device (PC terminal +DevKit) to android, The value 0x00 and following data will not be displayed if the total number of bytes is smaller than 8-byte.
The root cause of this is in the DSPS device firmware and will be fixed for the next release.
Made some progress. I am able to send serial data and I can see it in the DSPS application, but I cannot see it when using Blueloupe app. Is there a reason for that or am I missing something? Thanks
When the central side DSPS is active, it will immediately connect to the peripheral when the peripheral starts advertising. BlueLoupe is not intended for eavesdropping, so it will not display any details of a connnection between two other entities. If you stop the central device, you should see theperipheral advertis immediately.
I am trying to connect without DSPS in the Android side but using our app or BlueLoupe. BlueLoupe can connect all right but gets no notifications. I can see the data with Software I got from Nordic being updated on handle=18 but not through the notifications. Do you have a short code to show us how to get the data?
I have the demo working on the Basic using the instructions from Fri, 2014-12-05. Thanks. This demo is lacking documentation and proper support for the basic.
Hello fordp, as the documentation indicates, it only supoprts the EXPERT kit right now. There is a workaround for BASIC as outlined, but its not in the documentatin yet. We're working on updating this, so thanks for the feedback. BR JE_Dialog
Hello Rony, I will have to check on the final release : let me come back to that.
BR JE_Dialog
你好,罗尼,有一个解决方案。有一些limiations on the UART implementation on the BASIC kit which means using an external USB to UART cable cna overcome this.
The cable we used to connect the Basic DK’s serial port was a FTDI USB-RS232 TTL cable (part no: TTL-232R-3V3).
Also, some changes to the source code should be made in order to connect the correct pins to the UART:
In the “periph_setup.c” file
In the “GPIO_reservations” function, lines:
(51) RESERVE_GPIO( UART1_TX, GPIO_PORT_0, GPIO_PIN_4, PID_UART1_TX);
(52) RESERVE_GPIO( UART1_RX, GPIO_PORT_0, GPIO_PIN_5, PID_UART1_RX);
should point to the correct port and pins that will be connected to the FTDI cable.
Also, in the “set_pad_functions” function, lines:
(68) GPIO_ConfigurePin( GPIO_PORT_0, GPIO_PIN_4, OUTPUT, PID_UART1_TX, false );
(69) GPIO_ConfigurePin( GPIO_PORT_0, GPIO_PIN_5, INPUT, PID_UART1_RX, false );
should point to the correct port and pins. Additionally, “INPUT” value should be changed to “INPUT_PULLUP”.
BR JE_Dialog
OK.
我将试一试和报告。
Hello Rony, i just checked with the development team : it will work fine with the BASIC kit as long as you have it running as a 2 wire UART (and not 4 wire). BR JE_Dialog.
I will start by simulating the uart and filling the input fifo myself to check the amount of data I can xmit every second through the ble.
When that works I will add the uart interface which I am already using with my amateur implementation.
I also use 2 wires.
Thanks
Unfortunately it doesn't even start.
I get to a breakpoint in:hardfault_handle.c at line 120.
119:if ((GetWord16(SYS_STAT_REG) & DBG_IS_UP) == DBG_IS_UP)
120: __asm("BKPT #0\n");
121: else
122: while(1);
Any clue?
Hello Rony, I have a call with the develoment team tomorrow to clear up the issue : 4 wire implementation is fine, but as per email, 2 wire I'm getting conflicting feedback. BR JE_Dialog
Hello Rony,
here is the feedback i have on running the DSPS with 2 wire on BASIC kit :
When running the DSPS keil application without a UART cable connected the software will run into the fault handler. The reason of the failure is that UART RX signal is in an undefined state. This is solved by changing the configuration of the pin from INPUT to INPUT_PULLUP:
In file: periph_setup.c,
Function: set_pad_functions():
GPIO_ConfigurePin( GPIO_PORT_0, GPIO_PIN_5, INPUT_PULLUP, PID_UART1_RX, false ); // set UART Rx to input_PULL-UP
//GPIO_ConfigurePin( GPIO_PORT_0, GPIO_PIN_5, INPUT, PID_UART1_RX, false );
There are two other things to take care of :
When testing between a DSPS device role and the Android phone application the tool does not recognize the default BDaddress.
Workaround:
In file: nvds.c; .NVDS_TAG_BD_ADDRESS
Workaround: Change the value to something else
The issue will be fixed in the next revision of the Android application
3)
When transmitting the value "0x00" from DSPS-device (PC terminal +DevKit) to android, The value 0x00 and following data will not be displayed if the total number of bytes is smaller than 8-byte.
The root cause of this is in the DSPS device firmware and will be fixed for the next release.
BR JE_Dialog
Made some progress.
I am able to send serial data and I can see it in the DSPS application, but I cannot see it when using Blueloupe app.
Is there a reason for that or am I missing something?
Thanks
Hi Rony,
When the central side DSPS is active, it will immediately connect to the peripheral when the peripheral starts advertising. BlueLoupe is not intended for eavesdropping, so it will not display any details of a connnection between two other entities. If you stop the central device, you should see theperipheral advertis immediately.
I am trying to connect without DSPS in the Android side but using our app or BlueLoupe.
BlueLoupe can connect all right but gets no notifications.
I can see the data with Software I got from Nordic being updated on handle=18 but not through the notifications.
Do you have a short code to show us how to get the data?
Hi I am trying to get this demo running on the Basic too. Do you have better information on how to get it going?
I have the demo working on the Basic using the instructions from Fri, 2014-12-05. Thanks.
This demo is lacking documentation and proper support for the basic.
Cheers.
Hello fordp, as the documentation indicates, it only supoprts the EXPERT kit right now. There is a workaround for BASIC as outlined, but its not in the documentatin yet. We're working on updating this, so thanks for the feedback. BR JE_Dialog
Hello,
I would like to replicate the demo of SPS using the BASIC kit and TTL-232R-3V3 cable.
Can you please provide more details about how to boot the kit (SPS host) and connect TTL-232R-3V3 to it?
Thank you in advance.