Dears.

We are using GX3 to implement “ethernet to usb new module”.

This module is HW-implemented in USB 2.0 Only (Vbus, D+, D-) and When this module is hooked up to the computer,

PC device driver “Cypress GX3 Superspeedto Gigabit Ethernet BridgeController” is brought it up successfully in Network Adapter, device manager as the following. Then, when I tried to run “GX3 EEPROM configuration Utility” and press the "program" button to write configuration paramters like Mac address anD so on to the EEPROM, it pops up the error like “Open Device Fail”.

Could you tell me what happened inside of it ? Please give us any tips to get through it.

Thanks,

WonjinHan.

Hi All,

Merry Christmas and happy holidays.  My professional development project has hit a block.

Purchased a CY8CKIT-064S0S2-4343W kit and am working with ModusToolbox v2.2.0. 

I have hit an issue when trying to provision the device.  I get the following error when I try to do the provisioning as spelt out in the the Provisioning Guide documentation.

Everything seems to be ok but it fails with this error message

"

2020-12-29 14:24:59,073 : C : ERROR : Early Production Units detected, please get earlier version of tools by running 'pip install --upgrade --force-reinstall cysecuretools==2.1.0'. Check the log for details

Error: Failed processing! "

This error is also returned if I try and run the entrance-exam command.

Based on the responses, I am sure that the hardware is communicating with my pc.  I can't actually run the earlier version of cysecuretools as when I try that, I get a stack of python errors about being unable to build the wheel for cryptography which use PEP 517 and cannot be installed directly. 

So I would like to get things working with all the current versions of ModusToolbox etc.    Please help, it seems to be a pretty pathetic way to be failing as I am just trying to get the demo code to work at this stage 😞

Here is the response to entrance-exam. 

"

I:\Foundry\Project\S1000072_AWS\FreeRTOS\vendors\cypress\MTB\psoc6\psoc64tfm\security>cysecuretools -t cy8ckit-064s0s2-4343w entrance-exam

2020-12-29 14:24:58,260 : C : INFO  : Target: cy8ckit-064s0s2-4343w

2020-12-29 14:24:58,292 : P : INFO  : Target type is cy8c64xa_cm4_full_flash

2020-12-29 14:24:58,306 : P : INFO  : DP IDR = 0x6ba02477 (v2 rev6)

2020-12-29 14:24:58,308 : P : INFO  : AHB-AP#0 IDR = 0x84770001 (AHB-AP var0 rev8)

2020-12-29 14:24:58,312 : P : INFO  : AHB-AP#2 IDR = 0x24770011 (AHB-AP var1 rev2)

2020-12-29 14:24:58,318 : P : INFO  : AHB-AP#0 Class 0x1 ROM table #0 @ 0xf1000000 (designer=034 part=102)

2020-12-29 14:24:58,322 : P : INFO  : AHB-AP#2 Class 0x1 ROM table #0 @ 0xe00ff000 (designer=034 part=102)

2020-12-29 14:24:58,329 : P : INFO  : [0]<e0080000:CTI class="9" designer=43b part=906 devtype=14 archid=0000 devid=40800:0:0>

2020-12-29 14:24:58,331 : P : INFO  : [3]<e008e000:TPIU-M3 class="9" designer=43b part=923 devtype=11 archid=0000 devid=ca1:0:0>

2020-12-29 14:24:58,341 : P : INFO  : [4]<e007f000:ROM class="1" designer=034 part=102>

2020-12-29 14:24:58,342 : P : INFO  :   AHB-AP#2 Class 0x1 ROM table #1 @ 0xe007f000 (designer=034 part=102)

2020-12-29 14:24:58,356 : P : INFO  :   [0]<e000e000:SCS-M4 class="14" designer=43b part=00c>

2020-12-29 14:24:58,358 : P : INFO  :   [1]<e0001000:DWT class="14" designer=43b part=002>

2020-12-29 14:24:58,369 : P : INFO  :   [2]<e0002000:FPB class="14" designer=43b part=003>

2020-12-29 14:24:58,371 : P : INFO  :   [3]<e0000000:ITM class="14" designer=43b part=001>

2020-12-29 14:24:58,380 : P : INFO  :   [4]<e0042000:CTI class="9" designer=43b part=906 devtype=14 archid=0000 devid=40800:0:0>

2020-12-29 14:24:58,382 : P : INFO  :   [5]<e0041000:ETM-M4 class="9" designer=43b part=925 devtype=13 archid=0000 devid=0:0:0>

2020-12-29 14:24:58,393 : P : INFO  : CPU core #1 is Cortex-M4 r0p1

2020-12-29 14:24:58,396 : P : INFO  : FPU present: FPv4-SP

2020-12-29 14:24:58,409 : P : INFO  : 4 hardware watchpoints

2020-12-29 14:24:58,410 : P : INFO  : 6 hardware breakpoints, 4 literal comparators

2020-12-29 14:24:58,423 : C : INFO  : Use system AP

2020-12-29 14:24:58,428 : P : INFO  : Clearing TEST_MODE bit...

2020-12-29 14:24:58,434 : C : INFO  : Probe ID: 19111301a419041100a4190400000000000000002e127069

2020-12-29 14:24:58,435 : C : INFO  : Secure Flash Boot version: 4.0.1.1089

2020-12-29 14:24:58,862 : C : INFO  : Device CyBootloader version: unknown

2020-12-29 14:24:58,863 : C : INFO  : Package CyBootloader version: 2.0.0.3345

2020-12-29 14:24:59,067 : C : INFO  : Chip protection state: Secure

2020-12-29 14:24:59,073 : C : ERROR : Early Production Units detected, please get earlier version of tools by running 'pip install --upgrade --force-reinstall cysecuretools==2.1.0'. Check the log for details

Error: Failed processing!

"

The response when attempting to provision is similar.

"

I:\Foundry\Project\S1000072_AWS\FreeRTOS\vendors\cypress\MTB\psoc6\psoc64tfm\security>cysecuretools --policy ./policy/policy_multi_CM0_CM4_tfm.json --target CY8CKIT-064S0S2-4343W provision-device

2020-12-29 14:22:50,975 : C : INFO  : ######################################################################

2020-12-29 14:22:50,975 : C : INFO  : Provisioning packet is created

2020-12-29 14:22:50,976 : C : INFO  : ######################################################################

..... "

The rest of the provisioning response is the same as for the entrance-exam.

Thanks in advance for any help.  Cheers!

Peter

hello,

i've succesfully tried and reproduced the example called "qspi_read_write_using_sfdp".

When i'm importing the rights function in my project, the init function fails (cy_serial_flash_qspi_init).

When i'm digging into the details, it fails when calling Cy_SMIF_MemInit which return CY_SMIF_SFDP_SS0_FAILED

i've compared everything, and i'm not able to find what i'm doing wrong.

is there anybody who experienced the same issue ? thanks

How do you delete watchpoints in PSoC Creator?  In debug mode they are not selectable and right click does nothing.  When not in debug mode the windows does not appear.

Hi

I am making a connection to 2 different phones at the same time and trying to setup 2 simultaneous SCO links using HFP. For this to work I need at least one of the connections to route through the APP, I can see that it can be done by using:

wiced_bt_dev_status_t voice_patch_status =  wiced_bt_sco_setup_voice_path(&hfp_client_voice_path_setup);

WICED_BT_TRACE("Voice path setup status: %d\n\r", voice_patch_status);

I have inserted it right after:

result = wiced_bt_hfp_hf_init(&config, hfp_client_event_callback);

In the init of hfp.

And the rest is:

void hfp_client_sco_data(uint32_t ltch_len, uint8_t *p_data)

{}

static wiced_bt_voice_path_setup_t hfp_client_voice_path_setup =

{

              .path = WICED_BT_SCO_OVER_APP_CB,

              .p_sco_data_cb = &hfp_client_sco_data

};

I get status 0 Success but when I make the connection, I get a BTM_SCO_DISCONNECTED_EVT after BTM_SCO_CONNECTION_REQUEST_EVT instead of a BTM_SCO_CONNECTED_EVT.

I have also tried it in the Audio_Headset_and_Speaker example, there uses the bt_hs_spk_lib component, so here I have done it by:

bt_hs_spk_set_audio_sink(AM_UART);

And then the component should do the rest but same result, a disconnect.

I have been looking around but can’t find what I am doing wrong, do I need to include or setup something more to get it to work?

Is there an example project that uses wiced_bt_sco_setup_voice_path to APP?

Is there an example project their setup multiple SCO connections?

I use:

• CYW920721B2EVK-02
• Eclipse with ModusToolBox v2.2.0
• Bluetooth SDK version 2.8.0
• A headset with microphone

/Jacob

I made a custom board consisting of a CYPD3125 controller.

The board shall be the preferred power supply to a tablet connected via USB type-c. In case the boards external supply is down the tablet shall power the board. So the board with the CYPD3125 must be either source or sink.

The firmware is based on the notebook project that has already all main functions.

Now the problem is that the producer FET is never turned on. I only measure ~150mV.

Does anyone have an idea?!

Please find the attached screenshot of the schematic.

Hi there,

I have a question regarding the code checksum on a PSoC5LP part (specifically CY8C5667AXI-LP040).

I have a request on a project to provide the checksum of code over a serial interface.  Is there a known good way during runtime to either read or calculate the checksum of the entire codespace of the PSoC?  Perhaps even an API function I'm not aware of?

Thanks for the help!

Hello everyone,

i need a clarification on a detail regarding VCCIO=1V8 of CY7C65213.

As seen on the datasheet, the VCCD pin is the OUTPUT of the internal regulator for 1V8 and it cannot drive external loads.

Additionaly, on the datasheet  it is mentioned that when VCCIO is less than 2V, VCCD must be connected to VCCIO.

In this scenario, can the device be damaged during startup considering that the default configuration stored in its Flash doesn't disable the internal regulator (as shown on Table 2 in the datasheet)?

Lastly, always from Table 2 of the datasheet, it is hinted that CTS and DSR signals have an internal pull up. What about DCD and RI Signals? Do they have some internal pull up or pull down as well?

Thanks in advance.

Hi All,

I am creating a new design variant of a working project targeted for the 222014-01 BLE module by copying a working project that was targeted for the 222005 module, changing its name and using Device Selector to choose the new module type.

After doing this, I get three errors during the fitting stage:

To make matters worse, I've seen this error before but I cannot remember how I fixed it.  I have tried updating the components (BLE was updated to 3.66 and cy_boot to 5.90), but this hasn't eliminated the errors.

The error message suggests how to fix the problem but I can't find where one sets the "User provided" option.

Thanks,

Scott

Hello,

I am trying to include the 'CyAPI.lib' from the x64 Cypress library folder and trying to build in C++ 10.4 Builder for the multi target platform. But, I am facing problem with a linker error like "[ilink64 Error] Error: Unresolved external 'CCyUSBDevice::CCyUSBDevice(void*, _GUID, int)..................'  while trying to build. Please find the attached snapshot for more details. 

Any guidance on the matter would be greatly appreciated !!  

@YatheeshD_36 

Thanks,

Aditya