PSoC™ 4 Forum Discussions

Has there been an update to the CYBLE-222014-01 Bluetooth module from Bluetooth version 4.2 to version 5.1?

On the website it states that the Bluetooth version is 4.2, but on the documentation last revised on 7th May 2021, it states that Bluetooth version 5.1 is being used.  Revisions to the document do not make reference to this change. 

A leading electronics website is also showing the 4.2 version. CYBLE-222014-01 Cypress Semiconductor | Mouser Europe

Could someone please explain this discrepancy?

Hi,

I am working on a project where porting SMT32+ChibiOS software into PSOC4+FreeRTOS
I have CY8CKIT-046 Pioneer kit which is based on PSOC 4200L
I did extensive research and my only IDE option is PSOC Creator (MTB doesn't support PSOC 4200)

The problem that I am facing right now is that setting up interrupts on GPIO
https://www.cypress.com/file/127121/download
I read this document thoroughly and looks like my only option is to set each GPIO pin with GUI

However, I prefer to configure it by code.

On ChibiOS, I was able to configure it like this

palSetPadMode(GPIOD, 1, PAL_MODE_INPUT_PULLDOWN);
palSetPadMode(GPIOB, 0, PAL_MODE_OUTPUT_PUSHPULL);
palSetPad(GPIOB, 0);
palReadPort(GPIOD);

Can I do something like this on PSOC Creator?

Thanks,

Hi 

Do you know this fwarning: Function SARDAC.vplus is reachable through the analog routing fabric, but using this pin may lead to routing congestion ?

Best regards

LuBe

Hello,

We have a PSOC 4 MCU and we are using it as a peripheral. 

We are trying to measure the RSSI with the function CyBle_GetRssi after we are connected to our BLE dongle (using CySmart 1.3). 

It is very unstable and usually, it gives completely unreliable data going all over the range and even exceeding the given range of -85 to 5 db. 

In rare cases, it gives the correct data but once we move our device it suddenly stops becoming accurate and data that is completely unrelated gets printed all the time. 

Our code is fairly simple. Every second (once we are connected) we do the following:

int8_t scRSSI = CyBle_GetRssi();
uint8_t ucRSSI = scRSSI*(-1);
iprintf2_ISR(True,E_DEBUG_CODE,"[BLE] ### RSSI : -%d, %x",ucRSSI, scRSSI);

Here is the type of data that we get (as an example):

01/01 00:00:09.967 [BLE] ################# RSSI: -141, 73

01/01 00:00:11.009 [BLE] ################# RSSI: -49, ffffffcf

01/01 00:00:12.010 [BLE] ################# RSSI: -219, 25

01/01 00:00:13.013 [BLE] ################# RSSI: -57, ffffffc7

01/01 00:00:13.977 [BLE] ################# RSSI: -142, 72

01/01 00:00:15.009 [BLE] ################# RSSI: -50, ffffffce

01/01 00:00:15.980 [BLE] ################# RSSI: -43, ffffffd5

01/01 00:00:16.970 [BLE] ################# RSSI: -43, ffffffd5

01/01 00:00:17.972 [BLE] ################# RSSI: -213, 2b

01/01 00:00:19.008 [BLE] ################# RSSI: -206, 32

01/01 00:00:19.978 [BLE] ################# RSSI: -22, ffffffea

01/01 00:00:21.007 [BLE] ################# RSSI: -192, 40

01/01 00:00:22.009 [BLE] ################# RSSI: -100, ffffff9c

01/01 00:00:23.012 [BLE] ################# RSSI: -8, fffffff8

01/01 00:00:24.007 [BLE] ################# RSSI: -92, ffffffa4

01/01 00:00:25.010 [BLE] ################# RSSI: -6, fffffffa

01/01 00:00:26.008 [BLE] ################# RSSI: -91, ffffffa5

01/01 00:00:26.978 [BLE] ################# RSSI: -175, 51

RARELY it is reliable like here (which matches the RSSI measurement in the CySmart 1.3 program): 

01/01 00:00:16.008 [BLE] ################# RSSI: -34, ffffffde

01/01 00:00:17.007 [BLE] ################# RSSI: -34, ffffffde

01/01 00:00:18.014 [BLE] ################# RSSI: -34, ffffffde

01/01 00:00:18.979 [BLE] ################# RSSI: -34, ffffffde

01/01 00:00:20.008 [BLE] ################# RSSI: -34, ffffffde

01/01 00:00:20.973 [BLE] ################# RSSI: -34, ffffffde

01/01 00:00:22.007 [BLE] ################# RSSI: -34, ffffffde

01/01 00:00:23.012 [BLE] ################# RSSI: -34, ffffffde

01/01 00:00:24.007 [BLE] ################# RSSI: -34, ffffffde

01/01 00:00:25.006 [BLE] ################# RSSI: -34, ffffffde

01/01 00:00:26.007 [BLE] ################# RSSI: -34, ffffffde

01/01 00:00:27.007 [BLE] ################# RSSI: -34, ffffffde

Any idea why this is completely unreliable?

Thanks,

Eyal

Hi

We use CY8C4245PVI-482 in one of our product lines and having trouble obtaining more due tot he current shortages. Can someone recommend an alternate 4200xx part that may still be available in stock somewhere. We have enough for next 3 months or so and need to have more by the time they run out.

We use the SSOP-28 package but can redo the board to accommodate QFN or TQFP.

The requirements are not stringent. It needs 18 x Digital IO and a single 8 bit or higher resolution ADC or OP amp comparator would be ok instead. RAM and ROM are not critical, the code is small and just handling IO states in real time without need for large buffers. 48MHz is good but again, we can run at lower speed if required.

Thanks

Hello Everyone,

Software : PSoC Creator 4.4

Kit : CY8CKIT-145-40XX

Project : CE224820_PSoC4_CapSense_Slider_Gestures

CapSense Lib. Ver.7.0

Hw device: Linear slider with 5 segments

Hi All,

I am developing an HSSP programmer using a PSoC5 LP microcontroller to program any PSoC4 devices. For this, I downloaded the "001-84858_AN84858" example project. But the HexFileParser application "C# Application" is throwing the following error while generating parser .c and .h file which to be used in the final project.

ERROR DETAIL

===========

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.ArgumentOutOfRangeException: Index and length must refer to a location within the string.
Parameter name: length
at System.String.InternalSubStringWithChecks(Int32 startIndex, Int32 length, Boolean fAlwaysCopy)
at HexFileParser.FormHexFileParser.ParseFlashProtectionData()
at HexFileParser.FormHexFileParser.buttonParser_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.9151 (WinRelRS6.050727-9100)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v2.0.50727/mscorlib.dll
----------------------------------------
HexFile Parser
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Users/Ace%20Gas%20Analysers/Downloads/001-84858_AN84858/C%23%20Application/CY8C42xx_CY8C41xx%20family/HexFile%20Parser.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.9149 (WinRelRS6.050727-9100)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.9149 (WinRelRS6.050727-9100)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.9149 (WinRelRS6.050727-9100)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.9149 (WinRelRS6.050727-9100)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.