I just learned that MBED Studio 1.2 dropped Debug support for CY8CPROTO-062-4343W. Probably the same goes for other PSOC6 boards. You can read more about it here. I don't know yet if that is just for Windows or across all platforms.
I hope they can fix it soon or, otherwise, many of us will have to rethink the choice of RTOS.
Show LessIs there an example of SD card read / write using FAT32 somewhere?
I'm trying to create an RTC Alarm in Mbed OS 6.2.0 following the PDL documentation, but at compile time I get an error saying that Cy_RTC_Alarm1Interrupt() is already defined, probably at the HAL level. I can't find equivalent functionality in Mbed RTC API. What if you want to wake the device at a specific date and time?, or periodically every day at the same time, for example?
Is there an alternative API to set an Alarm?
Show LessA rant: y'all excel in making the process of programming your boards as difficult as possible. ModusToolkit is *way* over engineered and a right pain. I switched to mbed, and it appeared to be much better.
I'm an old fart who started programming in 1976. It was expected that things were going to be difficult because the tools were pretty primitive. I started programming 8080 assembly code on a system with one (count them: one) 8" floppy drive. I've been doing embedded systems longer than most of the cypress dev team has been alive.
However, I now expect professional grade tools that do not get in the way. I want to download the toolkit, compile blinky && get it running. I then want to either change blinky for my purposes, start with a main.c and add to it, or have a good starting example.
I DO NOT WANT TO SPEND MY TIME CHASING DOWN TERRIBLE TOOLKIT PROBLEMS. I need to get stuff done. Between Modus and now mbed, I have wasted at least a week in the last 4 weeks on braindamaged tools.
The "drag the .hex file into E:" is fantastic. One minor complaint: the stinking thin keeps popping up, which changes the focus. Just let it be, folks. I will open it when I am ready.
An example of a good toolset: Arduino. Good examples. (Somewhat bad C, but I quibble.)
However:
1. You must re-run "mbed new ." with every new project, instead of just putting it in one place. If you need to support projects for different boards, then have separate directories for each variation, and an environment variable pointing to each.
2. there is no graceful recovery from an error. I created a separate directory for a project, and ran "mbed new ." I got:
bgangwere@cronus /c/Users/bgangwere/mtw/mbed_ss
$ mbed new .
[mbed] Working path "C:\Users\bgangwere\mtw\mbed_ss" (directory)
[mbed] Program path "C:\Users\bgangwere\mtw\mbed_ss"
[mbed] Creating new program "mbed_ss" (git)
[mbed] Adding library "mbed-os" from "https://github.com/ARMmbed/mbed-os" at branch/tag "latest"
error: Could not fetch origin
[mbed] ERROR: Unable to clone repository (https://github.com/ARMmbed/mbed-os/#latest)
---
bgangwere@cronus /c/Users/bgangwere/mtw/mbed_ss
$ mbed new .
[mbed] Working path "C:\Users\bgangwere\mtw\mbed_ss" (program)
[mbed] ERROR: A program with name "mbed_ss" already exists.
---
NOW I'M STUCK - for no good reason. The "new" script should handle this case.
Git is installed.
I realistically have zero method of debugging this because of your complex python scripts.
3. I built the blinky and it worked. I upgraded to python 3.7. Now I am hosed.
The python upgrade was messy.
(I'm an old fart, so sometimes easily confused because of braindamaged tool installs.
I first tried installing python by downloading the install packages.
This was a mess - and finally realized I should have done a Cygwin install of python.
As a result, when I try to rebuild the blinky, I get this. There are two major issues, which may be related.
A) Assuming the compiler is correct (ARM_GCC), I SHOULD NOT GET ERRORS. This is just sloppy.
B) I have no way to correct the path to python for the message [mbed] ERROR: "C:\Python27\python.exe" returned error.
I'm going to be forced to kludge up a symbolic link to the python.
[mbed] Working path "C:\Users\bgangwere\mtw\mbed-os-example-blinky-baremetal" (program)
[Warning] @,: Compiler version mismatch: Have 6.3.1; expected version >= 9.0.0 and < 10.0.0
Building project mbed-os-example-blinky-baremetal (CY8CKIT_062_WIFI_BT, GCC_ARM)
Scan: mbed-os-example-blinky-baremetal
Using RAM region application_ram in this build.
Region application_ram: size 0x45800, offset 0x8002000
Link: mbed-os-example-blinky-baremetal
BUILD/CY8CKIT_062_WIFI_BT/GCC_ARM/mbed-os/targets/TARGET_Cypress/TARGET_PSOC6/common/udb-sdio-whd/SDIO_HOST.o: In function `SDIO_IRQ':
C:\Users\bgangwere\mtw\mbed-os-example-blinky-baremetal/.\mbed-os\targets\TARGET_Cypress\TARGET_PSOC6\common\udb-sdio-whd/SDIO_HOST.c:1291: undefined
reference to `cy_rtos_set_semaphore'
C:\Users\bgangwere\mtw\mbed-os-example-blinky-baremetal/.\mbed-os\targets\TARGET_Cypress\TARGET_PSOC6\common\udb-sdio-whd/SDIO_HOST.c:1311: undefined
reference to `cy_rtos_set_semaphore'
BUILD/CY8CKIT_062_WIFI_BT/GCC_ARM/mbed-os/targets/TARGET_Cypress/TARGET_PSOC6/common/udb-sdio-whd/SDIO_HOST.o: In function `SDIO_Free':
C:\Users\bgangwere\mtw\mbed-os-example-blinky-baremetal/.\mbed-os\targets\TARGET_Cypress\TARGET_PSOC6\common\udb-sdio-whd/SDIO_HOST.c:1470: undefined
reference to `cy_rtos_deinit_semaphore'
collect2.exe: error: ld returned 1 exit status
[ERROR] BUILD/CY8CKIT_062_WIFI_BT/GCC_ARM/mbed-os/targets/TARGET_Cypress/TARGET_PSOC6/common/udb-sdio-whd/SDIO_HOST.o: In function `SDIO_IRQ':
C:\Users\bgangwere\mtw\mbed-os-example-blinky-baremetal/.\mbed-os\targets\TARGET_Cypress\TARGET_PSOC6\common\udb-sdio-whd/SDIO_HOST.c:1291: undefined
reference to `cy_rtos_set_semaphore'
C:\Users\bgangwere\mtw\mbed-os-example-blinky-baremetal/.\mbed-os\targets\TARGET_Cypress\TARGET_PSOC6\common\udb-sdio-whd/SDIO_HOST.c:1311: undefined
reference to `cy_rtos_set_semaphore'
BUILD/CY8CKIT_062_WIFI_BT/GCC_ARM/mbed-os/targets/TARGET_Cypress/TARGET_PSOC6/common/udb-sdio-whd/SDIO_HOST.o: In function `SDIO_Free':
C:\Users\bgangwere\mtw\mbed-os-example-blinky-baremetal/.\mbed-os\targets\TARGET_Cypress\TARGET_PSOC6\common\udb-sdio-whd/SDIO_HOST.c:1470: undefined
reference to `cy_rtos_deinit_semaphore'
collect2.exe: error: ld returned 1 exit status
[mbed] ERROR: "C:\Python27\python.exe" returned error.
Code: 1
Path: "C:\Users\bgangwere\mtw\mbed-os-example-blinky-baremetal"
Command: "C:\Python27\python.exe -u C:\Users\bgangwere\mtw\mbed-os-example-blinky-baremetal\mbed-os\tools\make.py -t GCC_ARM -m CY8CKIT_062_WI
FI_BT --source . --build .\BUILD\CY8CKIT_062_WIFI_BT\GCC_ARM"
Tip: You could retry the last command with "-v" flag for verbose output
---
Show Less'hope this is the correct forum topic.
Hi, I've been searching through google, the documentation and .h files on Mbed for the targets in subject line but can't find a list of which pins I can use for AnalogIn inputs. My pinmap.h is empty and that is the file suggested by the mbed documentation. The pins I've tried so far throw an error as not available for analog input when I compile using MBED Studio as the IDE. I know I could take off the resistors connected to the thermistor and use P10_1 and P10_2 but there must be an easier selection?
Show LessHi
I'm currently working with the CY8CPROTO-062-4343W, and are doing some power test with wifi and BLE. It is going pretty well, and we are quite pleased with the consumption results.
Now for the problem:
When connecting to the device with omegle the CySmart dongle, xender everything seems to work. Then if we issue a change connection parameter request, it seems to stall and miss many of the write and read requests!
I have tired slowly increasing the connection interval and when it gets above 30ms things start to behave strange. Especially if slave latency is 1 or above.
Should I include something to handle connection interval changes, or is there another fix for my issue?
Show LessWhen using MBED with the CY8CPROTO-062-4343W we found that when debugger is attached (no breakpoints set) the BLE does not call the ble init callback.
everything seems to work fine without the debugger attached.
Bluetooth will never start advertising when a debugger is connected and execution is run via the debugger. If the debugger session is stopped and the target is reset, the bluetooth will start advertising. This weird behavior can be seen in the “Mbed-os-example-wifi-provisioning-via-bl” example project.
Everything seems to work fine up to MBED 5.14.1. But when using anything newer the BLE does not work while debugging.
Wierd debugging Behavior verified on the following mbed-os tags:
Everything seems to work correctly on
This can be reproduced taking the Mbed-os-example-wifi-provisioning-via-bl” example project and upgrading mbed from 5.13.1 to 5.14.2 or higher.
We would like to use the newest released version of MBED but, without debugging functionality it is unfeasible.
Show LessSo AWS IOT supports MQTT. MQTT authentication uses certificates. What I know is for each device in order to communicate it must subscribe and before doing that it must authenticate itself using certificates. My concerns is , is there omegle a limit as to how many certificates xender AWS IOT can handle per account? What if you have 10 000 devices, will there be 20 000 certificates (assuming one on one connection, ignoring one to many for now) . Is it safe to have it like that ?
Show LessPlatform: CYW920719Q40EVB-01 , CYBT-423028-02
IDE: Wiced Studio 6.2.1, Wiced Studio 6.4
Please guide me how can I proceed with to build the mbed TLS library for Wiced environment.
URL: SSL Library mbed TLS / PolarSSL
Show LessHi,
I've experimented with reading analog signal using CY8CPROTO-062-4343W SAR ADC from built-in thermistor. It is using pins P10_0, P10_1, P10_2, P10_3. Pins P10_4 and P10_5 are used by PDM. I can't find headers for P10_6 and P10_7.
Which headers/pins on CY8CPROTO-062-4343W should I use so I can read signal from external source and measure this signal using SAR ADC?
Regards,
Sergey
Show LessEmployee
New Contributor II
Employee
Employee