PSoC 4 MCU

現在 製品試作に実装しテスト中ですが
UARTでフレーミングエラーがまれに発生しており 原因と対策を検討中です
型番：CY8C4147AZI-S475

質問は
UARTのMedian Filterが どういう仕組みで 外来ノイズに対して 有効なのかどうかを知りたいです

PSoC UARTのデータシートについて
Document Number: 002-20171 Rev. *B  Page 138 of 216
の Median filter の項目についてですが
This parameter applies 3 taps digital median filter on input path of RX line. This filter reduces thesusceptibility to errors.
The default value is a Disabled.
このパラメーターは、RXラインの入力パスに3タップのデジタルメディアンフィルターを適用します。
このフィルターは、エラーの影響を受けやすくします。 デフォルト値は無効です。
と 機械翻訳では ”エラーが起きやすくなる” ような 意味になるのですが
実際にはどうでしょう？ また それを使用した時の 弊害はあるのでしょうか？

I have a CYBT-213043-EVAL board and the  CYBT-213043-Mesh board. I downloaded the Eclipse  IDE for modus toolbox 2.2 and opened the Mesh application and the RFComm application.  I was successful building, programming and running both applications using the USB connection for each board.  I now want to modify and debug each application. I purchased and received the CY8CKIT-005 miniprog4  kit to accomplish the debug.   I downloaded the software for the  CY8CKIT-005 miniprog4 kit and I believe I was successful.  1st question, is this the correct kit to perform debug?  2nd question, is there documentation to show how to physically connect the 5 pin or 10 pin connector of the CY8CKIT-005 miniprog4  kit to the eval boards?  3rd question, is there specific manual for debugging? 

Hi,

What happens to PSoC4 if RS-232 serial cable is unplugged during a bootlodable update by the bootloader via UART? Does the bootloader keep waiting for the next UART reception?

Since it's only halfway written to Flash, it may lead to corruption of the bootlodable. But if PSoC4 is reset and the Host System sends the bootloadable image again, I think it's possible to update the bootloadable.

Best regards

uint8 ProgramData(uint32 address, uint8* data, uint32 length)
{

.........

}

I want to define this function in ram so that after hardwa reset it will  disappear. I tried to change the link file add a section in ram area and use "CY_SECTION".It builded successfully but it failed in programming.It showed that the hex file not correct.Could somebody tell me how to modfiy this code?🤔

I have a running USB project with only a USB block in TopDesign. And I have a second complete project with pinning and pheriperals but USB does not work. I compared both USB settings and did not find any difference. Ist there a way to clone this projects that I will get the USB in second project working by overlaying both projects

I am trying to connect to a PSOC4 BLE device via PC using Cypress DLL. 

When I try to pair to the device, the DLL function (result.Device.Pair) returns a "fake"  success,  because the device does not show  that pairing did succeed at that moment.

Questions:

1. Is there a way to know if pairing truly succeeded? Checking device side  is not an option.

2. If not, how long does "result.Device.Pair(cyPairSettings)" take?

3. This is another issue, why does sometimes GattMtuExchanged (..) does not occur? 
(after running :Peripheral_.GattClient.ExchangeMtu(cyGattExchangeMtuInfo);)

Thanks!

Hello.

Attached project uses 2 PWM components.

PWM makes square wave, and this square wave is stopped or started by PWM_Timer interrupt.

Attached pptx file is waveform of this square wave.

Sometimes it takes some time for voltage level to reach GND when square wave is stopped.

Please confirm red circle of attached pptx file.

Q1)

Could you please let us know reason why this behavior occurs?

Does this behavior occur if PWM is stopped when voltage level is high?

Why doesn't voltage level go to GND immediately?

Q2)

Could you please let us know solution to this behavior?

I want to immediately set voltage level to GND regardless of timing that PWM_stop is called.

Best Regards.

Yutaka Matsubara

I am using the USB HID example from cypress. On the Cy8CKIT-059 (psoc5) it is running fine. I have to use CY8C4247AZI-L485 in a custom board.The system is self powered. I connected D+  D- and VUSB to the pins of the USB connector. I can programm but USB enumeration is not completed. The flow hangs in the while loop

int main(void)
{
uint16_t OUT_COUNT;
uint8_t* response;
CyGlobalIntEnable; /* Enable global interrupts. */

/* Place your initialization/startup code here (e.g. MyInst_Start()) */

/* Start USBFS operation with 5-V operation. */

USBFS_1_Start(USBFS_1_device,USBFS_1_5V_OPERATION); // USBFS_1_3V_OPERATION

while(USBFS_1_bGetConfiguration() == 0x00)
{
/* Waiting for device to be configured */
}

I also tried the 3V operation. I checked the USB configuration  and tried all options avaliable

also using P0.0 with a voltage divider connected in parallel to VUSB. What do I miss? How can I get  the device running?

I've got some code I've been writing that I now want to convert over to be able to upgrade Over The Air.

The code has the BLE component set up as a Client and Server profile.  The Client profile is configured with a Current Time Service, to enable syncing of the time in my code whenever it is accessed via a central device.  In the Server profile, I've got various custom services along with all the normal ones (Device Information, Generic Attribute, Generic Access, etc).

The Server profile is also set up to stuff some data into the Scan Response Packet, to make it easier to get data across to the Client without requiring a connection.  Connection is reserved for firmware updates (if I can get this to work!)

The code, as a non-OTA arrangement, compiles and works fine.  Until I attempt to convert it over to an OTA Fixed Stack Bootloadable version.  I've done this before, just not with the CTS functionality included, and its always worked.  I've followed all the steps outlined in the OTA Guide (AN97060), but I'm still not getting the Bootloadable code to compile.  Its throwing up a bunch of errors associated with the CTS functionality, even though I've made sure I've included the appropriate header files, etc.

The particular things its getting errors on are:

• CyBle_GetClientState()
• CYBLE_CLIENT_STATE_DISCOVERED
• cyBle_ctsc

I can see that these are all defined in the Bootloader source code (in BLE_eventHandler.h & BLE_cts.c and BLE_cts.h), but for whatever reason, my Bootloadable code isn't seeing them.

Any ideas what I'm doing wrong??

Cheers,

Mike