I am trying to program some LED lights but my PC is only able to recognize the device and not connect to it. If I connect the device with my phone and use the app that it came with however, the lights are able to work, and my PC connects to what I believe is an alternate version of this device paired with my phone, but which code (using JAVA Bluetooth API) does not recognize. After some research, I have come to believe that the lights are BLE, which would make sense since the name of the Bluetooth connection as seen on my phone and pc are "ELK-BLEDOM", but I am not sure where to go from here if this is the case. I read that BLE devices require third party applications to work, but I wonder why this is the case, and how people can create BLE applications in the first place if they need to test them on a PC which can't connect to BLE devices (I think). I do wonder if I can work around this process by creating an android application but only using it on my pc. However, I'd rather avoid building apps since I don't know how to, and I simply want to connect to this device and send data to turn on and off the lights. I may be understanding BLE wrong so I need help in doing so and to point me in the right direction.gb whatsapp

Hi, all

Sorry but I am not familiar with Mbed OS. So, I just want to know if Mbed SDK uses PSoC62/4343W supports for WPA3 personal security. Could you let me know?

Thanks, Bhavik

I recently discovered that MBED Studio 1.2 has removed debugging support for CY8CPROTO-062-4343W. The equivalent probably applies to other PSOC6 sheets. You can read more ometv about him here. I don't have a vague idea yet, I assume it's only for Windows or across all stages.

I believe that this will be rectified soon, or that a large number of us should reconsider the RTOS decision.

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.

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?

A 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

---