PSoC™ 4 Forum Discussions

Hello all,

 I want to be able to read the voltage difference of 2 electrodes over Bluetooth using Psoc 4 BLE. Are there any already existing codes that do this?  I'd appreciate any help or tips as I am just starting.

Hi, I'm developing a project involving the PSoC4 and UART using SCBs.

I have the following code that echos the sent bytes on the terminal.

"

int main(void)
{
/* Start UART operation */
UART_Start();

/* Transmit header to the terminal */
for(;;)
{
if(UART_SpiUartGetRxBufferSize() != 0ul) {
uint32 data = UART_SpiUartReadRxData();
UART_SpiUartWriteTxData(data);
}
}
}

"

I want to receive a numerical value throught UART interface and convert it to another range of values, but I can´t get it to recgonize the received bytes as a number and not as individual. 

Thanks for considering my question,

Nuno Vicente

For a line of product that originally used CY8C4248LQI-BL483 (BLE 4.1) then switched after 1000s were sold to CY8C4248LQI-BL583 (BLE 4.2), what options exist to continue to support OTA upgrades for all products in the line?

The preference would be for a single firmware that could be loaded onto all products regardless if they contain BL483 or BL583.

When switching to the BL583, the bootloader portion for the BL583 was changed to match the BL583. The bootloader on the fielded BL483 parts remains as BL483. When performing OTA on the BL583, CySmart insists on changing the bootloadable to 583 as well.

Is there a way to allow the bootloader to load the bootloadable portion from either build?

Note: Response to a simlar question did not offer a workable solution.
"How do I use the BLE 4.1 stack instead of the BLE 4.2 stack on a PSOC4 CY8C4248xxx-BL583 part?" @ https://community.cypress.com/t5/PSoC-4-MCU/How-do-I-use-the-BLE-4-1-stack-instead-of-the-BLE-4-2-stack-on-a/m-p/199994

Hi everyone,

I was using this project to measure throughput of the PSoC4 devices  https://www.cypress.com/blog/problem-solver/project-024-bluetooth-low-energy-throughput-pushing-limits.  

When I test it on the CY8C4248LQI-BL583 (the red board comes with the PSoC4 kit), the throughput is 269kpbs, same as what is mention in the link.

However, when I test the same project on the Cyble-214015-01, the throughput seems much lower, 167kpbs when on battery and 218kpbs when I plugged in the charger (it was on the PCB with a battery and a charging port for the battery). I am trying to optimize the throughput for this device so is there any ways to improve it on the Cyble-214015-01?

Also, I aim to transfer an amount of 40MB stored on an external serial flash through BLE to my laptop. What would be the best way to do it? Thankss!

Anybody has an ideas how we could get PSoC Creator happy again ?

Following is the callstack displayed on the dialogbox ...

System.NullReferenceException: Object reference not set to an instance of an object.
at CyDesigner.Common.ProjMgmt.Model.CyPrjMgmtComponentMgr.AreCustomizersAllowed()
at CyDesigner.Common.ProjMgmt.Model.CyPrjMgmtProjectPSoCExe.AreCustomizersAllowed()
at CyDesigner.Common.Db.CyS3Db.CyInst.GetCustomizerProviderImpl(CyCompName compName, CyInstBindContext ctx, String schName)
at CyDesigner.Common.Db.CyS3Db.CyInst.GetCustomizerProvider(CyCompName compName, CyInstBindContext ctx, CyInstCustomizerProvider& custProvider)
at CyDesigner.Device.FitLib.DesignWideResources.Components.CyComponentsModel.GetIsDesignWideComponent(CyPrjMgmtProjectPSoCExe proj, CyComponentMaster master, CyCompName compName, CyElabInstBindContext context, Boolean checkLatesetIfDoesNotExist)
at CyDesigner.Device.FitLib.DesignWideResources.Components.CyComponentsModel.GetSelectedSupportedComponentsBySource()
at CyDesigner.Device.FitLib.DesignWideResources.Components.CyComponentsModel.GetSelectedSupportedComponents()
at CyDesigner.Device.FitterPSoC.M0S8.DesignWideResources.Clocks.CyM0S8ClockInfoWdtIsr.DRC_GenerateIsr(CyHobtoClockModel model, CyElabInfo info)
at CyDesigner.Device.FitterPSoC.M0S8.DesignWideResources.Clocks.CyM0S8ClockInfoWdtIsr.CheckDRCs(CyHobtoClockModel model, CyElabInfo info)
at CyDesigner.Device.FitterPSoC.Common.DesignWideResources.Clocks.CyHobtoClockInfo.CheckDRCs(ICyClockModel model, CyElabInfo info)
at CyDesigner.Device.FitLib.DesignWideResources.Clocks.CyClockModel`1.SolveClocks()
at CyDesigner.Device.FitterPSoC.Common.DesignWideResources.Clocks.CyHobtoClockModel.ReloadDWRInfo(CyDWRChangeType changeType)
at CyDesigner.Device.FitterPSoC.Common.DesignWideResources.Clocks.CyHobtoClockModel.InitializeDeviceInfo(ICyDcDevice device)
at CyDesigner.Device.FitterPSoC.M0S8.DesignWideResources.Clocks.CyM0S8ClockModel.InitializeDeviceInfo(ICyDcDevice device)
at CyDesigner.Device.FitLib.DesignWideResources.CyResourceModel.Initialize()
at CyDesigner.Device.FitLib.DesignWideResources.CyResourceFactory.CreateModels(ICyResourceModelMgr dwrMgr)
at CyDesigner.Common.ProjMgmt.DWR.CyDWRMgr.CreateResourceModels(ICyDcDevice device)
at CyDesigner.Common.ProjMgmt.DWR.CyDWRMgr.UpdateSelectedDevice(ICyDcDevice device)
at CyDesigner.Common.ProjMgmt.DWR.CyDWRMgr.ProjectFullyLoaded(CyPrjMgmtProjectPSoCExe proj)
at CyDesigner.Common.ProjMgmt.Model.CyPrjMgmtProjectPSoCExe.PerformGlobalUpdates()
at CyDesigner.Common.ProjMgmt.Model.CyPrjMgmtPrjFactory.LoadProject(CyPrjMgmtProjectSerialize serializedData)
at CyDesigner.Common.ProjMgmt.Model.CyPrjMgmtPrjFactory.OpenThruDocMgr(CyPrjMgmtProjectSerialize serializedData)
at CyDesigner.Common.ProjMgmt.Model.CyPrjMgmtPrjFactory.GetProjectInstance(CyPrjMgmtProjectSerialize serializedData, Boolean openInUi)
at CyDesigner.Common.ProjMgmt.Model.CyPrjMgmtProject.LoadProjects(ICyProjectContainer container, IList`1 unloadedProjects, Boolean useFactory, Boolean openInUi)
at CyDesigner.Common.ProjMgmt.Model.CyPrjMgmtWrkspc.LoadProjects(Boolean useFactory)
at CyDesigner.Common.ProjMgmt.Model.CyPrjMgmtWrkspc.DeserializationCleanup(CyPrjMgmtWorkspaceSerialize serializedData)
at CyDesigner.Common.ProjMgmt.Model.CyPrjMgmtWrkspc.Restore(ICyBaseContainer parent, CyPrjMgmtWorkspaceSerialize serializedData)
at CyDesigner.Common.ProjMgmt.Model.CyPrjMgmtXmlSerializationTools.RestoreObject[T](ICyBaseContainer parent, IXmlSerializable serialized)
at CyDesigner.Common.ProjMgmt.Model.CyPrjMgmtWrkspc.Load(String canonicalName, Boolean useFactory)
at CyDesigner.Common.ProjMgmt.CyPrjMgr.CheckandOpenWorkspace(String item)
at CyDesigner.Common.ProjMgmt.CyPrjMgr.OpenItem(String item)
at CyDesigner.Common.ProjMgmt.CyPrjMgr.LoadItemDeferred()
at CyDesigner.Common.ProjMgmt.CyPrjMgr.m_framework_Idled(Object sender, EventArgs e)
at System.EventHandler.Invoke(Object sender, EventArgs e)
at CyDesigner.Common.Base.CyBasic.RaiseEvent(EventHandler eventToRaise, Object sender, EventArgs eventArgs)
at CyDesigner.Framework.CyDesignerFramework.ApplicationIdled(Object sender, EventArgs e)
at System.EventHandler.Invoke(Object sender, EventArgs e)
at System.Windows.Forms.Application.ThreadContext.System.Windows.Forms.UnsafeNativeMethods.IMsoComponent.FDoIdle(Int32 grfidlef)
at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr dwComponentID, Int32 reason, Int32 pvLoopData)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
at System.Windows.Forms.Application.Run(Form mainForm)
at CyDesigner.Framework.Run.Main(String[] args)

Hi everyone, 

I am using the CYBLE-222005 module to sending a resistive-based temperature sensor. Instead of building an external voltage divider circuit, I am using a current source (IDAC) that feeds a fixed small amount of current (< 300 μA) directly into the resistive sensor, and then I am reading the output change in RAW ADC and correlating it with the change in the resistance of my sensor which is acting as a variable resistor. 

Please check the schematic I am using below  

Now, I would like to actually expand it and sense form an array of 4 of that same resistive sensor at the same time, but I realized PSoC that I have only has two internal IDACs, so that might be limiting. 

The question is,  can use this same method to sense all 4 sensors at the same time. If so, what would be the arrangement? 

Can you please suggest a way in which I can measure 4 resistive-based sensors using CYBLE-222005? preferably using the internal components of the PSoC as much as possible 

Thank you and |I appreciate your help 

Hi Everyone, 

I have a small issue with this Soc - C8YC4147AXI-S475 , I tried to enable the WCO PLL to have an accurate SYSCLOCK for the CAN but I don't know how to enable it. 

Below you can see the warning :

Here my clock design

In my hardware design , I  have a external crystal of 32.768 KHz between P0.5 and P0.4 . 

I added this code in the main 

CySysClkImoStart();
CyDelay(500);
CySysClkWcoStart();
CyDelay(500);
CySysClkImoEnableWcoLock();

Actually its impossible to receive or transmit CAN Message , I'm supposed this issue is the problem. 

its really annoying because with this soc - CY8C4247AZI-M485 ,  you can trim the IMO directly in the system clock

Thank for your help . 

I need your opinion(s) on terminal emulator programs that you use with your Creator projects.

I've been using PuTTy and have had no difficulty with Creator 4.2 and the CY8CKIT-042 Pioneer Kit.

However, my students have run into an irritating phenomenon that happens with no regular pattern.  The phenomenon we see is that the single line of output from their program keeps repeating over and over - filling the screen,....  

We've checked -- this is not an infinite loop in their program.  The "fixes" which work are in order...

(1) switch to a different USB port  - (not always possible with newer laptops).

(2) Close and restart Creator.

(3) Turn off and then turn the computer back on.

(4) Run your program on a different PSoC eval board.

This issue seems to occur only with PuTTy which was chosen primarily because it's "no cost".  

So -- I'm asking for any recommendations and/or experiences you've had with terminal emulators.

Thanks

Hello,

I would like to use the CY8CKIT-149PSOC prototyping kit to test my slider design. The idea is  to separate  the original slider part from the kit. Then I solde  2,54mm pin header connector female on processor part of the kit, and a 2,54mm male connector on my slider board. Then I can connect them, provided that the pinout of my slider board is compatible with the processor part of the kit.

The kit is designed with a snap-away form-factor, so the separation should be possible without damage.

Do you think  it is possible?