PSoC™ 6 Forum Discussions
What are the minimum requirements that an MCU must have to support the SDIO interface of a hosted WiFi/BLE module?
For example, how can I tell if a CY8C6247BZI-D44T can be paired with a CYW43012 based Murata 1LV or a CYW4343 based Laird 450-0159 or 450-0152?
Greg
Show LessDears,
I am unable to find "Tool Settings" under C/C++ Build as shown in some tutorials, manuals for Modus Toolbox IDE. Where are these settings in Modus Toolbox IDE - 2.4.0 version ? In previous release it was under Project Properties: C/C++ Build -> Settings as shown on this picture:
And for comparison - In 2.4.0 release the "Tool Settings" tab is missing:
Thanks in advance and Best Regards
Radim
Show LessHello! Im currently trying to read a JSON file in my psoc project for the cyproto-063-BLE but i cannot get it to work.
I have a JSON file that im trying to include in the project, read from and extract the data, im using the tiny-json parser (https://github.com/rafagafe/tiny-json). The parser works as intended, if i manually store the JSON as a string, i can parse and extract data as i please. The issues arise when i try to include the .json file into the project and open/read from it.
Here is a code snippet
static const char filename[] = "test.json";
FILE *file = fopen ( filename, "r" );
char buffer[128];
fread(buffer, 128, 1, file);
printf("line = %s\r\n", buffer);
fclose(file);
json_t what[32];
json_t const* json2 = json_create( buffer, what, sizeof what / sizeof *what );
char const* name = json_getPropertyValue(json2, "Name");
printf( "Name: %s.\r\n", name );
I have included the file under source files, as well as added the filepath to Project->Build settings->CM0+->Compiler->Additional Include Directiories.
Following the debugger the program crashes at line "fread(buffer, 128, 1, file);"
Does anyone have any input on how to read and store the JSON file in psoc programmer, the file opening and reading works well when isolated in a regular C file ran through the terminal. I'll attach a test project where i try to read a json test file and print it to serial monitor using UART. Relevant header and json files are in a folder in the project called External_Code.
Any help is greatly appreciated!
//Arvid
Show LessHi All,
Could any of you help me in setting the sampling frequency of the PSOC6 chipset ADC to 2KHz?
The minimum clock frequency the ADC can take in is 1.7MHz and I am unable to find a reasonable way to lower the sampling frequency.
Any suggestions are welcome. Thanks in advance.
Show LessDear Receiver,
I followed the following guidence to create a "customer BSP".
ModusToolbox 2.2 and later: Make a Custom BSP - KB... - Infineon Developer Community
But I can't create a "Empty PSoC 6 App" project because there are no this item for me to select.
One thing make me feel confused is ,,, in the guidence there have "Empty PSoC 6 App" item. But in my MTB, no this item.
Attached pictures are my process. Could you please help me to check it ?!
Do you have a suitable method that can guide me to develop a BSP ?!
Thank you so much.
Show LessHi,
I was trying to sample signal from a signal generator and was using the ADC to sample the signal.
I noticed that at 100Hz, there were 10 samples per cycle, and I was getting a good waveform for the same. So, I felt that the sampling frequency may have been 1Khz, so I went on to change the SPS in the ADC, but whatever value I change it to, it seems to be not working. I do not want any averaging as such, but I also tried using averaging and that also did not work.
I am attaching the configuration of my ADC as well as the output from the ADC on an UART.
Could you please help me on the same?
Thanks in advance.
Show Less
I'm really struggling to get the die temp working for the SAR in the PSOC6. I've looked at the example project and the other post on the forums. I'm not able to easily intergrade those examples into my project.
The steps to switch configurations between my application settings and the settings for the die temp are not clear. It's not as simple as just changing the P1 switch in the MUX registers. I have tried creating multiple configurations in my code and switching between them as shown in the CE220974, but I am not able to successfully switch to the die temp. I have spent several days trying to get this to work.
Can any one list the steps needed to use the die temp or a working SAR configuration that I can switch to?
The SAR on the PSOC is quite complex and I really wish with there was an API to set up the Die temp and switch between a working die configuration and my application.
Currently, in my code I'm just checking if the conversion is done in the main loop (no interrupts at the moment) and then after getting the result I switch over to the next configuration back and forth. For the die temp configuration I'm using the defined configuration in the example project.
Show LessHello, I am currently having trouble trying to complete one of the first tasks for the hello world exercise. Mainly because am using a Macbook and am unfamiliar with how the terminal works here. After opening up the Terminal on MacOS, I am trying to select the KitProg3 COM port and then set the serial port parameters to 8N1 and 115200 baud.
Show LessHello, I have an inquiry regarding Uart - DMA Interrupt.
I understand that DMA-Rx interrupts depending on the setting value.
For example, if you set the "Number of data elements to send" value to 10, an interrupt occurs when 10 is received.
Then, if you set it to 10 and divide it into 6 or 4 instead of 10, is there a function that can cause interruption for each case?
For ST, Interrupt of Uart may occur when the signal from Rx is in Idle state (=Transmission Interrupt).
If you wait for the DMA buffer to fill, and then generate and process interrupts, a large amount of incoming data is missing.
Is there a way to solve this problem?
Please give me a lot of advice.
I'm running two tasks on PSoC6 Wifi BT Pionner kit, using FreeRTOS and I would like to get the run time statistics of the tasks and print on the UART terminal.
- Stack Usage
- Task State
- Priority
- Abs Time (absolute time)
This is the total 'time' that the task has actually been executing (the total time that the task has been in the Running state). It is up to the user to select a suitable time base for their application