I have successfully implemented the functionality of my project using Capsense (MatrixButtons) and have seen good results in Tuner and can print the results using Tera Term. Now I need to use the BLE component in order to implement these. I tried the Example Code for CE218137_BLE_Proximity_RTOS, and I was thinking that Proximity is also a feature of Capsense, and I thought that maybe I could just refer to it to implement my functionality? Or is there a better example code I can learn from?
Using CE218137_BLE_Proximity_RTOS as an example, I can successfully connect and see the values change at CySmart. But what I want is to print them in the serial port and see them from the Tuner, not just see a value from CySmart; because we need to print them for subsequent personalized data processing and visualization. Is this something that can be realized? I need to be pointed in the right direction as there is so much BLE sample code and manuals here.
Thanks for your help!
Hello Infineon Community
I have a few questions about the XMC Pinout Tool.
First of all I wanted to ask if the XMC Pinout Tool runs with the free Java version (Oracle Java SE v17 LTS) without restrictions?
Secondly, I would like to ask whether the Java licence for e.g. Java Update 8 381 is included with the Pinout Tool, as this Java version normally incurs licence costs.
Thanks a lotShow Less
we have some questions about the BLE stack.
Here are some details about our setup:
Chip: CY8CPROTO-063-BLE (CYBLE-416045-02)
Modus Toolbox: 3.1.0
BLE Stack: 3.8.0 (WICED/AIROC BLE)
1. In the default configuration, the BLE stack is used in dual-core mode, i.e. BLE controller on CM0p with predefined image CM0P_BLESS, BLE stack on CM4, and IPC for communication between the two CPU cores.
Is it possible to move the whole BLE functionality (BLE controller + BLE stack) to CM4 core, and use predefined image CM0P_SLEEP on CM0p?
I found some examples and documentation for using PSOC Creator and the old BLESS stack, but none for Modus Toolbox and the new WICED/AIROC BLE stack.
2. Is there a project implementation available, for building and modifying the CM0p image CM0P_BLESS on our own?
I've noticed the DPS310 pressure sensor now has "not for new design" label in the product finder. Can you please recommend alternatives in similar price range?
Also, are there any information regarding the DPS310 status available? For how long it will be produced, supported etc.? I've tried to find it but without any success.
Thanks and have a nice day!
I am working with a motor with a current rate of 45 Amps and I have set the motoring current limit to 90% and over-current for internal gatekill comparator as 75A. I am using a 3mohm shunt resistance. The motor is rated to run at 3000 RPM but I have set to run it only at a max of 2500RPM, and when i I try to Run at 2100 RPM I face Gatekill error even at No load condition. I have checked the external comparator using an external Oscilloscope, where there is no error signal being generated. When I check with the scope in MCEDesigner the error is generated above 30Amps, I have the doubt over the internal comparator. Plz Help me in this regards.Show Less
I've written my SPI initialization code for the cyusb3kit-003 as follows:
/* SPI initialization for application. */
CyU3PReturnStatus_t CyFxSpiInit(uint16_t pageLen)
CyU3PReturnStatus_t status = CY_U3P_SUCCESS;
/* Start the SPI module and configure the master. */
status = CyU3PSpiInit();
if (status != CY_U3P_SUCCESS)
/* Start the SPI master block. Run the SPI clock at 8MHz
* and configure the word length to 8 bits. Also configure
* the slave select using FW. */
CyU3PMemSet((uint8_t *)&spiConfig, 0, sizeof(spiConfig));
spiConfig.isLsbFirst = CyFalse;
spiConfig.cpol = CyTrue;
spiConfig.ssnPol = CyFalse;
spiConfig.cpha = CyTrue;
spiConfig.leadTime = CY_U3P_SPI_SSN_LAG_LEAD_HALF_CLK;
spiConfig.lagTime = CY_U3P_SPI_SSN_LAG_LEAD_HALF_CLK;
spiConfig.ssnCtrl = CY_U3P_SPI_SSN_CTRL_FW;
spiConfig.clock = 4000000;
spiConfig.wordLen = 8;
status = CyU3PSpiSetConfig(&spiConfig, NULL);
However, when I load and run the code on the device and check the SPI clock pin with an oscilloscope, I don't see 4 MHz. Instead, I'm getting an inexplicable value like 1.9 kHz. What could be the reason?Show Less
I recently got a BGT60TR13C DEMO board for my research. I have downloaded the Python API and the radar fusion GUI, which both work well and are quite useful. However, I have some questions regarding the parameters of the radar sensor itself. For real-time applications, I need to know more about the chirp and frame design. Below is a screenshot of my configuration of the sensor:
As you can see, now we have some known parameters:
chirp_repetition _time = 591μs
frame_repetition_time = 0.04 sec
ADC_sampling_frequency = 2 MHz
num_samples_per_chirp = 64
num_chirps_per_frame = 64
However, I have some confusions in the following questions, could you confirm whether my understanding is correct? If not, could you provide the right answer?
a) The chirp repetition time here is actually the up-chirp time + the inter-chirp idle time, right?
b) As ADC_sampling_rate * num_samples_per_chirp = 32 μs, comparing with the chirp_repetition_time 591 μs, this is weirdly small. Does that mean the up-chirp time is actually 32 μs and the rest of the time is just the inter-chirp idle time? In this case, the sensor's duty cycle is less than 10%, this can't be true. Is there a possibility that the actual up-chirp time is a fixed value and it is much longer than my calculation, you are just sampling some of the data from the start of the chirp based on the setting of num_samples_per_chirp? Where can I find these parameters, such as the actual up-chirp time, inter-chirp idle time, and the inter-frame idle time?
c) As chirp_repetition_time * num_chirps_per_frame = 0.037824 sec, so the inter-chirp idle time is : frame_repetition_time - 0.037824 = 0.002176 sec. Is this correct? Did I miss anything in the calculation?
d) Is there a way to get the actual time index of each ADC data point? Or you normally just use the entire frame data as one measurement of range-doppler and the small time differences in real-time can be neglected? In this case, it is equivalent to getting 25 measurements per second, and the time index for the measurement is simply 0.04 * chirp number.
e) This question is specifically related to the python api. The rx_mask will determine which receiver is activated. For example, When rx_mask = 1, the R1 is activated. But how this actually works? It seems like rx_mask = 7 will activate all receivers 1,2, and 3. What if I want to select receiver 2 or 3 solely?
Thank you very much for your time and patience, and I am looking forward to your replies.
Lithium battery protection board project, high-side NMOS tube controls charging/discharging circuit. Now, a gate driver chip, IRS25752LTRPBF, has been selected. After returning the sample for debugging, it was discovered that after the MCU gave a high level signal, this chip did not work, and there was no output. The driving circuit is as follows:
Can you help analyze what is wrong with this circuit?