PSoC™ 6 Forum Discussions

the  emwin spport  the GUIDRV_LIN  driver

   I  use  GPIO to make it ,the code like this: 

#define LCD_CLR_A0() cyhal_gpio_write(pins->spi_dc, false)
#define LCD_SET_A0() cyhal_gpio_write(pins->spi_dc, true)
#define LCD_CLR_CLK() cyhal_gpio_write(pins->spi_sclk, false)
#define LCD_SET_CLK() cyhal_gpio_write(pins->spi_sclk, true)
#define LCD_CLR_DATA() cyhal_gpio_write(pins->spi_mosi, false)
#define LCD_SET_DATA() cyhal_gpio_write(pins->spi_mosi, true)
#define LCD_CLR_CS() cyhal_gpio_write(pins->spi_cs, false);
#define LCD_SET_CS() cyhal_gpio_write(pins->spi_cs, true);

/* Write 1 byte, MSB first */
void Send1(unsigned char Data) {
if ((Data >> 7) & 1) LCD_SET_DATA(); else LCD_CLR_DATA(); LCD_CLR_CLK(); LCD_SET_CLK();
if ((Data >> 6) & 1) LCD_SET_DATA(); else LCD_CLR_DATA(); LCD_CLR_CLK(); LCD_SET_CLK();
if ((Data >> 5) & 1) LCD_SET_DATA(); else LCD_CLR_DATA(); LCD_CLR_CLK(); LCD_SET_CLK();
if ((Data >> 4) & 1) LCD_SET_DATA(); else LCD_CLR_DATA(); LCD_CLR_CLK(); LCD_SET_CLK();
if ((Data >> 3) & 1) LCD_SET_DATA(); else LCD_CLR_DATA(); LCD_CLR_CLK(); LCD_SET_CLK();
if ((Data >> 2) & 1) LCD_SET_DATA(); else LCD_CLR_DATA(); LCD_CLR_CLK(); LCD_SET_CLK();
if ((Data >> 1) & 1) LCD_SET_DATA(); else LCD_CLR_DATA(); LCD_CLR_CLK(); LCD_SET_CLK();
if ((Data >> 0) & 1) LCD_SET_DATA(); else LCD_CLR_DATA(); LCD_CLR_CLK(); LCD_SET_CLK();
}

but  the frequency is just 1MHZ,the signal request almost 48Mhz, clock of CM4  is 100Mhz and the Peripherals clock drivers set 1, so the Peripherals clock can up to 50Mhz .  but when build this project ,there are some mistaks like this :

so  how to make the  frequency up to 48Mhz ,and make this mistaks dis.

Hello Community, 

I am observing a strange build problem with MCUBoot Roll back code example with ModusToolbox 2.4; 

GitHub - Infineon/mtb-example-anycloud-mcuboot-rollback: This example implements an MCUboot-based bootloader to demonstrate ‘Rollback’ to a known good image (factory app) in case of any unrecoverable error conditions with the application that is currently running.

I initially tried this example on MTB2.3.1 and everything works perfectly fine. But, when I started using this CE in MTB2.4, it throws a strange linker error. 

"arm-none-gnueabi/bin/ld.exe: Cannot find : Invalid Arugument"
Collect.exe: error: ld returned 1 exit status 

Is this a known issue or something is wrong with my build setup ? 

Thanks in Advance,

Stephan C

Hi,

from Cypress's SEGGER emWin graphics library 6.26.0 Quick Start guide, it mentions

This section provides the step-by-step instructions how to implement a simple "Hello World" application using emWin.

1. Add emWin to the project. For ModusToolbox™, add emWin to the project using the Middleware selector.

1. Now, my question is 2-fold because I don't know how to do either of the options in step 1. I want to work with vscode, so Ideally I would like to add a middleware library without having to open the eclipse IDE for MTB. Is there a way to do that?

2. but also, I don't even know how to add the emWin middleware to a project in eclipse MTB. I just created a Hello world application, and I tried right clicking on the project name to add middleware but it doesn't seem to be the right way because it is not there:

How can I add the emWin library to any given project in eclipse MTB?

3. I have a third extra question, just for understanding. Does the mtb_shared folder contain everything in advance, or it grows as you add middleware to the projects in your current workspace. I guess my question is, if you have a git repo with a MTB project, should you include mtb_shared with it, or it always contains standard files and is going to be provided by the MTB software and no need to clone it into the repository?

I'm using the CY8C6244AZI-S4D93.

Device  Configurator 4.0 generate TCPWM related code with TCPWM_ver2.  

But, Cy_TCPWM_Enable_Multiple() & Cy_TCPWM_TriggerStart () support only TCPWM_ver1.

Please advise me, Which one can support TCPWM_ver2 as the above functions?

Thanks for reading.

Dear All, 

I am using cyBLE-416045-02 BLE controller on my custom PCB. I connected MOSI and MISO pins to 9.0 and 9.1 on controller (scb2 block). and SCLK and CS pin to 5.2 and 5.3 on controller (scb5 block). Now I cannot use my spi pins since it connected to different scb. Is there any way to configure this in software side. Please help.

Dear experts,

I have a question regarding OPENOCD CLI.

All other functions have been implemented,

but the part related to External Memory Erase & Programming is not working well.

Can I get help on how to use External serial memory (SMIF)?

The below log is excerpted from cypress programmer.

----------------------------------------------------------------------------------

Warn : Adding extra erase range, 0x18019000 .. 0x1803ffff

Info : [100%] [################################] [ Erasing ]

Info : [100%] [################################] [ Programming ]

Info : wrote 604160 bytes from file C:/firmware1.hex in 8.338982s (70.752 KiB/s)

Info : ** Erasing bank 8 **

Info : Using EraseChip API to erase 'psoc6_smif1_cm0' bank, this may take several minutes...

------------------------------------------------------------------------------------------------------------------------------------------

We are getting an error trying to initialize our external 32.768 kHz ( Epson FC-135R 32.7680KA-A3) with 22pf caps. Connected to pins P0_0 and P0_1 on the CY8C624AAZI-S2D14 device.

The WCOEnable routine returns FALSE. The Cy_SysClkWcoOkay never returns true.

Hello,

I am trying to use this example https://github.com/Infineon/mtb-example-psoc6-bmi160-motion-sensor-freertos#operation for CY8CKIT-062-WIFI-BT (which is on supported devices list).

As described, I changed the INTERFACE_USED and BMI160_INTERRUPT_CHANNEL values in motion_task.h, but when i program the device and connect through Putty it is blocking after printing the first line (screenshot attached).

Any idea about what could be the issue?

We are using cy8c624AAZI-s2d14 and want to use the input PIN to count the pulses uses TCPWM "Count Signal" feature.

What is the best way to lookup which PINs are available for counter input?

The MTB device configurator only shows certain PIN being available as "Count Signal", e.g. only pin 0 and 1 are available for most of the ports as input to the counter.

How can I use the datasheet  to identify these PINs?

Based on the pattern, it appears that column ACT#12 of  Table 8. Multiple Alternate Functions might be the information I need, but I want an expert for confirm it.

And if that is true (i.e. ACT #12 is the timer count input function), what does peri.tr_io_input mean? It has not been mentioned anywhere in the document.