PSoC™ 4 Forum Discussions

Hello

Is there a working example of a dmx transmitter implemented with PSoC4 and uart component?

I have found AN49187 which is a starting point however is related to PSoC1.

Thank you.

Fausto

Hello, as there is a EnterDeepSleepLowPowerMode(); function I would be wondering if there is also a function for a SleepMode instead of the DeepSleep Mode?

simply "EnterSleepLowPowerMode();" does not work.

thank you very much

I am trying to measure the current across a low side shunt as shown below.  My question is can I do this as I show in my schematic?  If I can do it what is the proper configuration of the ADC?  Do  I need to make sure I set it up a non-signed or some other configuration?

I have tried it in the signed configuration and it works fine as long as i do not ground either input.  When I ground the bottom input as shown in my schematic the ADC  only reports zero basically when i run any current through shunt.  I am using a CY8CKIT-043 prototyping board mounted to a PCB I had made for a production test project I am trying to implement.

Thanks

I tried to add a test that force the system into deep sleep mode forever, but not sure if CyGlobalIntDisable disable the different wakeup causes from deep sleep?
The code is only for measurement purpose and would require a reset/power cycle.

        CySysWdtUnlock();

        CySysWdtDisable(CY_SYS_WDT_COUNTER0_MASK | CY_SYS_WDT_COUNTER1_MASK | CY_SYS_WDT_COUNTER2_MASK);

        CySysWdtLock();

        uint8_t isr_stat = CyEnterCriticalSection();

        CyGlobalIntDisable;

        CySysClkWriteHfclkDirect(CY_SYS_CLK_HFCLK_IMO);          

        CySysClkEcoStop();

        CySysPmDeepSleep();

        CyExitCriticalSection(isr_stat);  

Just a PSoC Analog Co-processor based board (CY8C4A45LQI-483) for testing and I'm currently having issues programming it (Seeing the generic -> FAILED! PSoC device is not acquired! Check connection of the chip to the programmer).

After further inspection it turned out that the board is using P3.2,P3.3 for the SWD interface instead of P0.0, P0.1 as shown in the reference design (CY8CKIT-048).

However the chip's datasheet specifies that P3.2/P3.3 can also be used for SWD .

Question:
* how do I configure PSoC Programmer/Creator to use cpuss.swd_data:1/cpuss.swd_data:1 (P3.2/P3.3) for programming instead of cpuss.swd_data:0/cpuss.swd_data:0 (P0.0/P0.1)

The system tab only offers on SWD option in the Programming/Debugging -> Debug Select drop down.

I'm using:

PSoC Creator  4.1 Update 1 (4.1.0.3210)

PSoC Programmer  3.27.1.3121

Thanks

System Tabs:

Documentation Excerpt:

I can download released hex file into my board PSOC4014 successfully,

But when i goback to debug the project in PSoC Creator 4.2 with the same cable connection, I can not see any devices in "Select Debug Target".

When I Press the "Port Acquire" button, nothing happen.

Please help me ~~~ Thanks

Hello everybody,

I'm trying to use the module CYBLE222014-01 in my PCBs.

They are flexible PCBs, made with kapton substrate.

We are encountering some problems with the reflow soldering process, the pcb changes size due to the heat and the module cannot stick to the pads properly.

Are there any documents you know, which can explain the methods to solder this module?

Does anybody already tried to solder it on a flex pcb?

Thank you in advice!

Cheers.

Andrea

We are trying to program the CYBLE-022001-00 device with your MiniProg3 programmer with your CYBLE-022001-PROG module that the device goes in using your PSoC Programmer Software Version 3.26.0.2791. We are setting the programmer settings as shown here in below screen capture-

The device passes the programming process BUT if we do a stand-alone verify or stand-alone checksum the device fails against the firmware file. I noticed that during the programming process is shows “Doing Protect” so I thought maybe the device was being protected in some way BUT I did a read of the device and as you will see in the log that nothing is being protected that I can see. This programming tool is new to us so I am at a loss as to why the device passes the programming process but fails the stand-alone verify or stand-alone checksum processes. Please take a look at what I have provided and advise.