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
你好rony，我打了电话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,
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
解决方法：将值更改为别的东西
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.
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. 你have a short code to show us how to get the data?
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
你好rony，有一个解决方法。基本套件上的UART实现有一些限制，这意味着使用外部USB到UART电缆CNA克服了这一点。
The cable we used to connect the Basic DK’s serial port was a FTDI USB-RS232 TTL cable (part no: TTL-232R-3V3).
此外，应制作对源代码的一些更改，以便将正确的引脚连接到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，输入，PID_UART1_RX，FALSE）;
应该指向正确的端口和引脚。此外，应将“输入”值更改为“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
不幸的是，它甚至没有start.
我在第120行的突破点in：hardfault_handle.c。
119:if ((GetWord16(SYS_STAT_REG) & DBG_IS_UP) == DBG_IS_UP)
120：__asm（“Bkpt＃0 \ n”）;
121: else
122: while(1);
Any clue?
你好rony，我打了电话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）;//将UART Rx设置为Input_pull-up
//GPIO_ConfigurePin( GPIO_PORT_0, GPIO_PIN_5, INPUT, PID_UART1_RX, false );
还有另外两件事要照顾：
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
解决方法：将值更改为别的东西
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.
我能够发送串行数据，我可以在DSP应用程序中看到它，但在使用Blueloupe应用程序时我无法看到它。
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.
你have a short code to show us how to get the data?
嗨，我试图在基本上运行这个演示。您有更好的信息有关如何进行的吗？
我使用2014-12-05周五的指令进行了基本工作的演示。谢谢。
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.
您能否提供有关如何引导套件（SPS主机）并连接TTL-232R-3V3的更多详细信息？
Thank you in advance.