hi,

since a couple of days back we're having issues with make getlibs (which should download a lot of git repositories from github), with errors such as:
ERROR:there was an error retreiving the asset 'https://github.com/cypresssemiconductorco/mtb-hal-cat1' commit 'release-v2.2.0' - fatal: unable to access 'https://github.com/cypresssemiconductorco/mtb-hal-cat1/': Failed to connect to github.com port 443 after 131002 ms: Connection timed out.

we don't have any firewalls or connection issues with github when run outside of your build system.

unfortunately mtbgetlibs is a binary file so i can't figure out exactly how it works.

this is with modus toolbox 3.0.

anyone else seen this?

Howdy, all

Unfortunately I'm curious about Mbed operating system. In this way, I simply want to find out whether Mbed SDK utilizes PSoC62/4343W backings for WPA3 individual security. Might you at any point tell me?

Much obliged to you!

I'm currently working on a project involving the CY8C4245-AXI microcontroller for a CapSense application, and I've run into a bit of a challenge. Specifically, I'm having trouble with UART the convenience of accessing credit card information https://mycardstatement.wiki    communication. It seems to be stuck, and I'm not sure why.Has anyone else worked with this microcontroller and experienced similar UART communication issues? If so, I would greatly appreciate any insights or solutions you might have. Your assistance would be invaluable to me.

Thank you for your help!

What is the GATT_DISCOVER_MAX in the bluetooth stack wiced_bt_gatt_discovery_type_e used for? And what parameter should I pass in wiced_bt_gatt_client_send_discover() if I wanted to used it?

Hello,

I am using the PMG1-S3 evaluation board (CY7113) to run the sample project "USBPD_DRP_EPR" provided on gitHub.

When I write and run FW from Modus Toolbox with [USBPD_DRP_EPR Program (KitProg3_MiniProg4)], it works fine, but when I run it with [USBPD_DRP_EPR Debug (KitProg3_MiniProg4)], the following error message appears.

（Error: Failed to read memory at xxx）

--------------------------------------------------------------------------------------

Started by GNU MCU Eclipse
Open On-Chip Debugger 0.12.0+dev-5.0.0.2401 (2023-05-16-04:28)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
Info : auto-selecting first available session transport "swd". To override use 'transport select <transport>'.
adapter speed: 2000 kHz
** Auto-acquire enabled, use "set PSOC4_USE_ACQUIRE 0" to disable
cortex_m reset_config sysresetreq
Info : Using CMSIS-DAPv2 interface with VID:PID=0x04b4:0xf155, serial=051E07C203011400
Info : CMSIS-DAP: SWD supported
Info : CMSIS-DAP: Atomic commands supported
Info : CMSIS-DAP: FW Version = 2.0.0
Info : CMSIS-DAP: Interface Initialised (SWD)
Info : SWCLK/TCK = 1 SWDIO/TMS = 1 TDI = 0 TDO = 0 nTRST = 0 nRESET = 1
Info : CMSIS-DAP: Interface ready
Info : KitProg3: FW version: 2.50.1383
Info : KitProg3: Pipelined transfers enabled
Info : KitProg3: Asynchronous USB transfers enabled
Info : VTarget = 3.276 V
Info : kitprog3: acquiring the device (mode: reset)...
Info : clock speed 2000 kHz
Info : SWD DPIDR 0x0bc11477
Info : [psoc4.cpu] Cortex-M0+ r0p1 processor detected
Info : [psoc4.cpu] target has 4 breakpoints, 2 watchpoints
*****************************************
** Silicon: 0x3501, Family: 0xC5, Rev.: 0x12 (A1)
** Detected Family: PMG1-S3
** Detected Device: CYPM1311-48LQXI
** Detected Main Flash size, kb: 256
** Chip Protection: OPEN
*****************************************
Info : gdb port disabled
Info : starting gdb server for psoc4.cpu on 3333
Info : Listening on port 3333 for gdb connections
Info : SWD DPIDR 0x0bc11477
Info : kitprog3: acquiring the device (mode: reset)...
[psoc4.cpu] halted due to debug-request, current mode: Thread
xPSR: 0xa1000000 pc: 0x10000040 msp: 0x20007fe8
** Device acquired successfully
Started by GNU MCU Eclipse
Info : Listening on port 6666 for tcl connections
Info : Listening on port 4444 for telnet connections
Info : Power dropout detected, running power_dropout proc.
Sensed power dropout.
Sensed power restore, running reset init and halting GDB.
Info : SWD DPIDR 0x0bc11477
Info : SWD DPIDR 0x0bc11477
Info : SWD DPIDR 0x0bc11477
Info : kitprog3: acquiring the device (mode: reset)...
[psoc4.cpu] halted due to debug-request, current mode: Thread
xPSR: 0xa1000000 pc: 0x10000040 msp: 0x20007fe8
** Device acquired successfully
Info : accepting 'gdb' connection on tcp/3333
Info : New GDB Connection: 1, Target psoc4.cpu, state: halted
Warn : Prefer GDB command "target extended-remote :3333" instead of "target remote :3333"
Info : SWD DPIDR 0x0bc11477
Error: Failed to read memory at 0x10000040
semihosting is enabled
Warn : No RTOS could be auto-detected!
Warn : No RTOS could be auto-detected!
Verifying region (0x00000000, 64356)... Match
Info : All data matches, Flash programming skipped
Info : SWD DPIDR 0x0bc11477
Info : kitprog3: acquiring the device (mode: reset)...
[psoc4.cpu] halted due to debug-request, current mode: Thread
xPSR: 0xa1000000 pc: 0x10000040 msp: 0x20007fe8, semihosting
** Device acquired successfully
Info : psoc4.cpu: bkpt @0x00000405, issuing SYSRESETREQ
[psoc4.cpu] halted due to debug-request, current mode: Thread
xPSR: 0x61000000 pc: 0x00000404 msp: 0x20008000, semihosting
===== arm v7m registers
(0) r0 (/32): 0x40100004
(1) r1 (/32): 0x00000405
(2) r2 (/32): 0x00000000
(3) r3 (/32): 0x00000000
(4) r4 (/32): 0x20008000
(5) r5 (/32): 0x08000000
(6) r6 (/32): 0x0ffff0e0
(7) r7 (/32): 0x00000000
(8) r8 (/32): 0x00020149
(9) r9 (/32): 0x802a4010
(10) r10 (/32): 0x1fff8000
(11) r11 (/32): 0x00000000
(12) r12 (/32): 0x016e3600
(13) sp (/32): 0x20008000
(14) lr (/32): 0x1000012b
(15) pc (/32): 0x00000404
(16) xpsr (/32): 0x61000000
(17) msp (/32): 0x20008000
(18) psp (/32): 0x30082884
(20) primask (/1): 0x00
(21) basepri (/8): 0x00
(22) faultmask (/1): 0x00
(23) control (/3): 0x00
===== Cortex-M DWT registers
Info : Power dropout detected, running power_dropout proc.
Sensed power dropout.
Sensed power restore, running reset init and halting GDB.
Info : SWD DPIDR 0x0bc11477
Info : SWD DPIDR 0x0bc11477
Info : kitprog3: acquiring the device (mode: reset)...
** Device acquired successfully
Info : SWD DPIDR 0x0bc11477
Error: Failed to read memory at 0x10000040
Info : SWD DPIDR 0x0bc11477
Error: Failed to read memory at 0x10000040
Info : SWD DPIDR 0x0bc11477
Error: Failed to read memory at 0x10000102
Info : SWD DPIDR 0x0bc11477
Error: Failed to read memory at 0x10000102

--------------------------------------------------------------------------------------

What is the cause of the error?

Similar errors have also occurred in other samples.

Regards.

Hi, 

I am trying to include mbedtls library for an example project called "Cryptography_AES_Demonstration" (Available in MTB Examples). 

But when I try to build the project 

make[1]: *** Waiting for unfinished jobs....
bsps/TARGET_APP_CYSBSYSKIT-DEV-01/config/GeneratedSource/cycfg_system.c:117:28: error: initializer element is not constant
117 | .enableOutputDiv = true,
| ^~~~
bsps/TARGET_APP_CYSBSYSKIT-DEV-01/config/GeneratedSource/cycfg_system.c:117:28: note: (near initialization for 'srss_0_clock_0_fll_0_fllConfig.enableOutputDiv')
bsps/TARGET_APP_CYSBSYSKIT-DEV-01/config/GeneratedSource/cycfg_system.c:170:19: error: initializer element is not constant

I know it works with the other mtb examples where mbedtls is already added into its project. 

Expectation: Steps to include the mbedtls library to the project and build without an error.. 

Your prompt response will be greatly appreciated.. 

wiced_btsdk\dev-kit\libraries\btsdk-audio\release-v4.3.0\COMPONENT_hfp_audio_gateway\hfp_ag_command.c

Error format: