PSoC™ 4 Forum Discussions
Hello,
I have created a custom service on the BLE profile, which should hold multiple characteristics.
After I created the first characteristic, everything is working just fine, service and characteristic are showing in CySmart and my 'self built' android app.
However, when I add a second characteristic or service (in the same way as I did with the first characteristic or service) this second characteristic or service is not showing.
I tried both adding a second custom characteristic to the custom service and adding a second custom service with it's own custom characteristic.
Can anyone please help me out on what I'm missing? Problem may be in the UUID's, but if so, I wouldn't know which rules to follow to fix it.
I have attached a screenshot of my profile, I am using the following UUID's;
Service - Milivolts - 00000000-0000-1000-8000-00805F9B34F0
Characteristic mVmeten - 00000000-0000-1000-8000-00805F9B34F1
Custom Descriptor - 00000000-0000-1000-8000-00805F9B34F2
Service - MiliAmpere - 00000000-0000-1000-8000-00805F9B34F3
Custom Characteristic- 00000000-0000-1000-8000-00805F9B34F4
Custom Descriptor - 00000000-0000-1000-8000-00805F9B34F5
Any support would be much appreciated
Show LessI'm working my way through some PRoC/PSoC BLE projects. I'm on to the Day020_BLE_UART project from the 100 projects in 100 days list. The project talks about reprogramming the BLE-USB Bridge. I'm wondering where I can find the correct default program for the BLE-USB Bridge, so it will work as expected after I'm done doing anything that requires me to reprogram it. I am using the CY8CKIT-042-BLE Bluetooth® Low Energy (BLE) Pioneer Kit and I see on the page for that kit, there are two .hex files for the BLE-USB Bridge. Are these the files I'm looking for, and which one of the two is the way to go?
Thanks
Show LessHello,
can me somebody help please?
I need store the device name during scaning. My problem is, that I don't know the length of field for the name. For example, I find the 10 devices, but every device has different name.
Can I find somehow the length of field for the device name during scaning?
Thx
Show LessI need code to check battery. I opened "BLE_Battery_Level" example and run it. When I connected input to real pair of 1.5V batteries (2.56V) it measure 0 voltage. Are this example is working ?
Where I can get real working example for check battery ?
Show LessHi,
I started a few days using this kit and have been doing some experiments. Now I'm trying to do the example project named "OpAmp_PSoC4_Example", but I'm not getting the expected result.
In the pdf file of that example project it says that I have to "Power cycle the device". This means that I have to select the "Power cycle" programming mode in PSoC programmer?
I am only programming this kit using the onboard programmer (KitProg) and it only supports "reset" programming mode. I don't know if this is the problem and if have to get MiniProg3 (that I think it supports "power cycle" programming mode).?
PS: I am powering this kit just using the USB port.
Show LessHello Guys, This is Gaurav. I want to merge two different programs of BLE into one single PSoc Creator Workspace.
I'm using a PSoc4 042 BLE Kit. Both should work one at a time and controlled by the BLE phone app.
Both the programs i want to operate I've attached below.
Please guide.
Thank you, Guys, in advance for your every help!
Show LessHi,
I have been having great luck with the Fixed BLE Stack option. I have run into a single snag however. I am finding that my BOOTLOADABLE project, after calling CyBle_GattsNotification():
- cyBle_busStatus always equals zero.
- The CYBLE_EVT_STACK_BUSY_STATUS is never triggered.
The matching BOOTLOADER project does work. Any thoughts? I have tried BLE component version 2.30 and 3.10 without any luck. I can confirm that the notifications are being sent when CyBle_GattsNotification() is called in both the BOOTLOADABLE and BOOTLOADER projects.
Thanks.
- Chris
Show LessI'm interested in learning if the following project functionality/configuration can be achieved with PSoC Creator:
A) A bootloader which supports OTA Update functionality using Cypress's bootloader / bootloadable approach as detailed in AN97060, preferably with a fixed stack, as the device I want to use (CYBLE-012011) doesn't have 256kB, so the upgradeable stack could only be achieved by using a more expensive device or with external memory, both of which I'd prefer to avoid.
B) The application would be using both Broadcaster and Observerer roles. The Broadcaster would be dynamically updating the manufacturer specific data in the advertisement packet, and the Observer would be looking for a special message to indicate it should switch into the bootloader for a firmware update.
Essentially I'm looking to create a beacon which also supports OTA firmware update, so any if any of the gurus out there could #1 confirm that this is achievable and #2 give me any pointers as to the best way to approach configuring a project / CyBLE block(s) to get this setup, that would be very much appreciated.
Thanks so much for your time.
Cheers,
-Jonathan
Show LessHello,
can me somebody help, please?My problem:
I need send maximum packet - it is 512byte - in one MTU .
I found this document:
http://www.cypress.com/knowledge-base-article/maximum-packet-size-according-mtu-kba203312
So, for my dates remain 509 (= 512 - 3) bytes. But in Profiles - I have have the Custom charakteristics with the field - uint8[]. Which length of field has to be? 509bytes?
Thank you
Show LessMy project doesn't fit into the UDBs. The workaround with the control file doesn't work as mentioned. Any idea?
The placer is not able to place all of the carry chains without backtracking. It fills one UDB bank to 15/16 and the other to 7/8 and cannot place the final 2-datapath chain. As a workaround, add a control file to the TopDesign component (in Workspace Explorer's Components tab) with the following lines: ATTRIBUTE placement_force OF \Timer_ADPActiveTime:TimerUDB:sT16:timerdp:u0\ : LABEL IS "U(2,0)"; ATTRIBUTE placement_force OF \Timer_OutputPeriod:TimerUDB:sT24:timerdp:u0\ : LABEL IS "U(3,1)"; ATTRIBUTE placement_force OF \Timer_OutputActiveTime:TimerUDB:sT24:timerdp:u0\ : LABEL IS "U(0,1)"; This will fill the datapaths in the second UDB bank and allow the placer to assign the remaining datapaths.
Show Less