PSoC™ 4 Forum Discussions

Hello,

I am using PSOC4100S MCU CY8C4147AZI-S445 with PSOC Creator 4.2.

I want to switch Pins(P3.0(RX) and P3.1(TX))  from UART SCB to Input pins. 

I followed this link.

In this Uart port is stopped, but In Uart tx pin, it reads value 0, but on the it is 3.3V (tested with multimeter). I used following code:

temp = CY_GET_REG32 (CYREG_HSIOM_PORT_SEL3);

        // Configure UART_Rx pin to be controlled in firmware

        CY_SET_REG32 (CYREG_HSIOM_PORT_SEL3, CY_GET_REG32 (CYREG_HSIOM_PORT_SEL3) & 0xFFFFFF00);

        // Set the drive mode of UART Rx pin

        UART_1_tx_SetDriveMode(UART_1_tx_DM_RES_UP);
        //CY_SET_REG32 (CYREG_HSIOM_PORT_SEL3, temp);

Please help me for this issue.

Thank You 

I have a pin colection (number of pin= 😎 forming a 8 bit port on P0.0 to P.7. For this port is used as to interface my device in a byte way in one mode. My device also  allow to run with an SPI in serial mode. Here I have to configure the port each pin differently (input/output) to be able to connect as SPI. Each pin configuration needs 3 bit so for 8 bits this will end up in a uint32_t for configuration.

If I use each pin seperatly (number of pin =1 eight times), I will lose the possibility to write all 8 bits in one cycle... I have to generate a bif if / else construct for each bit of the byte, slowing down my write cycle.

I want to have a fast byte access and a fast bit access of each pin / port and I want to assign aome pins

case 1 to the SPI module and sone single control lines

case2 to 8 port bidirectional

and diong this in runtime.

Please tell me the name and the access posibility of this 32bit register. It would be great if you will publish all the information you are hiding how the peripheral exactly look (structure and register/flags names), how the register are named so I can use the controller bejond the methods you are offering in your API.

I have a bootloader where I set the bootloader version parameter to 0xabcd. I enter the bootloader using the bootloader command and then I check the meta data using the get metadata command, I get the right bootloader version 0xabcd. I then flash the chip with a new bootloadable using the bootloader and I reset the chip. After the chip resets, it enter the bootloader and doesn't exit until I send it a command. However when I send it enter bootloader using the bootloader command and then I check the meta data using the get metadata command, I get the wrong bootloader version. Is this expected behavior or am I missing something?

Are the PSoC4 CY8C4247AZI-M485 and the CY8C4248AZI-L485 pin for pin compatible?  Is the CY8C4248AZI-L485 a drop in replacement for the CY8C4247AZI-M485?  I have a board designed for the CY8C4247AZI-M485 and finding out more RAM is needed.  

Also, the CY8C4248AZI-L485 has USB pins that are no-connects on the CY8C4247AZI-M485.  My board is designed already.  If the CY8C4248AZI-L485 is a drop in replacement for the CY8C4247AZI-M485, what should I do with the USB pins?  Just disable these USB pins?  Thanks.

I set an EEPROM section at 0x4E00 in Bootloader.And I want to read and write  EEPROM at same address(0x4E00)in bootloaderable.The start address of bootloaderable is 0x6000.If I define the same address ,it shows that  wrong image  overlaps section .

I would like  to check where a Click happened with respect to the X axis and therefore assigning a right or a left click, having the Maximum X-Axis position=395 and the Maximum Y-Axis position=395.

I didn't find a way to access the position of where a touchdown or a liftoff happened so I decided to use the CapSense_GetXYCoordinates(CapSense_TOUCHPAD0_WDGT_ID) function. However I am not sure if the output is in the correct format to be compared with the 198 value because the device seems to not work accordingly, always displaying a left click.

How could this be corrected and would there be a better way of doing this? Maybe accessing the touchdown and the lift off positions?

POS_X= (int) (CapSense_GetXYCoordinates(CapSense_TOUCHPAD0_WDGT_ID)<<16);

click = (gestureID == CapSense_ONE_FINGER_SINGLE_CLICK) ? 1u : 0u;

if(click && POS_X<=198){
leftButtonPress = 1u;
abMouseData[0u] = (leftButtonPress ? MOUSE_LB : 0u);
}

if(click && POS_X>198){
rightButtonPress = 1u;
abMouseData[0u] = (rightButtonPress ? MOUSE_RIGHT : 0u);

Thank you for your help

I want to add OTA firmware upgrade to my project.  The original project (not developed by me) has no bootloader.  My understanding from reading through Cypress documentation is that I need to create a bootloader project and move the BLE component from the application project to the bootloader project.  When I do this my application won't compile because the BLE component is missing.  Is there a way to have a BLE component in the application project and a different BLE component (specifically for OTA) in the bootloader project?