PSoC™ 6 Forum Discussions
I’d like to move the vector table away from the default starting address.
When the vector table is relocated, the debugger can’t figure out where to start.
Is something hard-coded in the debugger to point to a specific code starting address?
If starting address is not hard-coded, where is it specified?
I am trying to send continuous data in an interval of 30ms to the CySmart app. The data I am acquiring is through the ADC port. I know there is a connection interval limitation for the phone, I have taken care of that, and my algorithm is based on that constraint. However, I am using Cy_BLE_GATTS_WriteAttributeValueLocal(&serviceHandle) to send data to CySmart app, however it is not continuous and need to press the Read button every time to read the data.
Is there a way to make that continuous, like I saw one for Heart rate somewhere on the internet where it is possible to plot the data also in the app?
Can someone guide me in this?
Also, I would like to know whether the CySmart App has been taken down from the App store, I download it from some APK present in the internet.
Your help is much appreciated.
Anik SenguptaShow Less
I have this development kit CY8CKIT-062-WIF-BT. I can program and debug in Modus toolbox just fine. I want to follow the BLE tutorials in PSoC Creator. When I try to program the device, the board does not show up as a target to select.
I have updated the board to kitprog3.
Using the https://github.com/Infineon/mtb-example-wifi-mqtt-client demo project with a CY8CKIT-062S2-43012, after publishing to the client, the client stops sending a PINGREQ to the MQTT broker and the broker will send a disconnect when the client exceeds the KEEPALIVE timeout.
The expected behavior would be to keep the connection with the broker alive regardless of how often the client is published to or what is being published.
I am migrating a project to v4.0.0 of the Anycloud MQTT Client (this started before v5.0.0 was release) and I first noticed this behavior when I added a simple hardware timer that had nothing to do with MQTT. In that investigation I found that the FreeRTOS timer for the KEEPALIVE ping request fails, the client fails to ping, and the MQTT broker sends a disconnect message when the timeout is exceeded.
To repeat the issue:
This is on version 4.0.0 of the demo code, using version 2.4 of ModusToolbox, and a un-secure connection to a Mosquitto broker on my network running on an Ubuntu v20 box. The broker is set up with both secure and un-secure connections and I have noticed the failure to send a PINGREQ with both. An un-secure connection allows easy verification via Wireshark.
- Clone and checkout v4.0.0 of https://github.com/Infineon/mtb-example-wifi-mqtt-client
- Run “make modlibs” and switch the BSP to CY8CKIT-062S2-43012
- Change WiFi config to match my network
- Update MQTT broker to local network address, the port to 1883, turn off MQTT_SECURE_CONNECTION, and change MQTT_KEEP_ALIVE_SECONDS to 5. (Changing the keep alive to five seconds will reveal issue faster.)
- Not necessary, but it cleans the UART output - comment out lines 262-276 in source/subscriber_task.c in the mqtt_subscription_callback() function.
Once programmed, running, and connected, publish to the device with mosquitto_pub: mosquitto_pub -h 192.168.1.5 -t "ledstatus" -m "0123456"
The message "0123456" does not mean anything to the client as the processing of it is commented out -- I just want to see the connection work. The message gets through, but the client no longer sends a PINGREQ and the MQTT broker disconnects.
I've attached the output of the client and the relevant portion of Mosquitto broker log. Notice that the first client id is psoc6-mqtt-client8847 and after reconnecting, the id is psoc6-mqtt-client21675 which is reflected in both logs. I would've attached text files, but they are not allowed.
From the Wireshark capture, you can see that the broker closes the socket at the 13.712 s mark. This is roughly 7.5 seconds after the last PINGREQ from the client at the 6.138 s mark. 7.57 s is about 1.5 the keep alive time of five seconds set above.
Any help would be appreciated,
I am working with PSoC6 (CYBLE-416045), I want to use the Bluetooth functionality. I have a running code, which I want to test with the CySmart app - I tried the Cypress BLE Beacon which is available on google play– but I can’t connect to the PSoC6. The PSoC6 bluetooth is visible on my smartphone, but not on the app.
Is the app out of function, if so, is there any alternative?Show Less
I've a little question about the way UART works on PSOC6.
My project is on ModusToolBox and I use only low level API for UART (smartcard mode) (Cy_SCB_UART_Put() / Cy_SCB_UART_Get()).
Each time i send a byte, i have the echo and need to read this bytes to empty rx fifo.
Is it normal ? is it possible to avoid this ?
Thank you for your support,
I would like to learn PSoC 61 MCU but I can't find any demo kits which is based on PSoC 61 MCU.
Most of kits are based on PSOC 62 or PSoC 63.
Is any demo kit based on PSoC 61 MCU ?!
Thank you so much.Show Less
How can I modify only a specified section of Flash during development?
I would like to be able to program a 2nd firmware image in a location offset from an existing firmware image on a PSoC 61 such that I can test modifications to the 2nd firmware without affecting the first.
I designed a PCB around the CY8C614AAZI-S2F44 which uses USB to talk to a host. As far as I'm aware, this device is not yet supported by PSOC Creator so I've had to use the HAL API directly. The USBDP and USBDM pins on the type-B connector are connected to pins 14_0 and 14_1 respectively. I've hooked the PCB up to my computer to try to communicate and I have an oscilloscope probe between USBDP and ground.
To initialize the peripheral, I tried every combination of the following:
- Enabling the USB peripheral in the device configurator in modus toolbox
- Copying the initialization snippet in the HAL documentation
- Just calling cyhal_usb_dev_connect() without calling cyhal_usb_dev_init()
When I call the initialization function, it returns an error code and the PSOC gets stuck in an infinite loop. It seems that When I set the USB config in the Device Configurator and only call the cyhal_usb_dev_connect(), some fault occurs and I also get stuck in an infinite loop. In neither case do I see any activity on the USBDP line.
What am I doing wrong?
Sam ShersherShow Less