PSoC 6 and ModusToolbox: FreeRTOS to AWS MQTT

RE: PSoC 6 and ModusToolbox: FreeRTOS to AWS MQTT

skruglewicz — Wed, 10 Nov 2021 02:36:44 GMT

Hi [mention:acaf6a9338de4eef8f6717d5561ed01d:e9ed411860ed4f2ba0265705b8793d05]

I hope this comment finds you well.

I 'm having some trouble connecting an Arduino Nano 33 IoT to my PSoC6 CY8CKIT and getting this project to work. I'm not getting any error, but the AWS output you described. Nothing is showing up on the nanodrone tAWS hing.

You did help me with Building the new version of the project stated in the above thread and I was hoping you could give me some insight into why it doesn't appear to be working with my 2 boards.

The Arduino was used for a Design Challenge "Design for a cause 2021" and the PSoC6 is being used for an existing challenge "Low Power IoT design challenge".

I realize I'm using 2 different boards than you are for this project and I'm wondering if I have the connections and software correct for these 2 boards?

I've Followed your steps above, in summary:

I experimented with and was able to get the Anycloud MQTT client example to run by:
- Creating a ''Thing" on AWS called "ledstatus"
- It connected ok and I was able to subscribe to ledstatus and see the button press events as described.
When using your project:
- I created another Thing called nanodrone
- I used the keys generated when creating the thing, in the "mqtt_client_config.h" file
- I was able to build the project
- On the the Arduino I created a sketch as you described above.
- I then connected 2 jumper wires between the 2 kits as you described above.
  - there is no pin 10.0 on my kit?
  - so I used the RX pin
  - Described on the wiring diagram in the Low Power IoT challenge blog.
- The code runs and displays status messages on the terminal that the WiFi is connected and the AWS MQTT broker is connected.
- When I press the reset button on the Arduino nothing happens as described?
.I was wondering a few things that I might have wrong:
- Do I have the proper jumper wire connections?
  - Is 10.0 the RX pin I'm using?
- Do I have the proper pins defined in uart_task.h ?
- Is your example code portable to the Arduino Nano 33 IoT? or do I need to do something different?
- You use the 10.0 pin on your PSoc6 CY8CPROTO kit. What is the equivalent pin on the PSoC6 CY8CKIT?

Thanks so much for an excellent project and all you continued help.

Steve K

RE: PSoC 6 and ModusToolbox: FreeRTOS to AWS MQTT

Jan Cumps — Sat, 23 Oct 2021 18:22:22 GMT

Success:

[View:/resized-image/__size/620x281/__key/commentfiles/f7d226abd59f475c9d224a79e3f0ec07-d27de103-bca8-4e6b-8586-2ef78cd96685/7824.contentimage_5F00_216690.png:620:281]

The linker complained that I had 2 global variables called message.

I fixed this by renaming the one in subscriber_task.c sub_message and the one in publisher_task.c pub_message.

It now compiles and links.

Not tested.

RE: PSoC 6 and ModusToolbox: FreeRTOS to AWS MQTT

Jan Cumps — Sat, 23 Oct 2021 18:03:07 GMT

Progress:

The configuration for TLS is in file Nanodrone-II_PSoC6/configs/mbedtls_user_config.h

I replaced the Nanodrone one with the contents of the new AnyCloud MQTT Client project (found at the same location in the imported example).

[View:/resized-image/__size/620x356/__key/commentfiles/f7d226abd59f475c9d224a79e3f0ec07-d27de103-bca8-4e6b-8586-2ef78cd96685/6266.contentimage_5F00_216689.png:620:356]

The mbedtls lib now compiles OK.

RE: PSoC 6 and ModusToolbox: FreeRTOS to AWS MQTT

Jan Cumps — Sat, 23 Oct 2021 17:54:52 GMT

It errors with the same issues as you have:

[View:/resized-image/__size/620x261/__key/commentfiles/f7d226abd59f475c9d224a79e3f0ec07-d27de103-bca8-4e6b-8586-2ef78cd96685/8321.contentimage_5F00_216688.png:620:261]

RE: PSoC 6 and ModusToolbox: FreeRTOS to AWS MQTT

Jan Cumps — Sat, 23 Oct 2021 17:51:24 GMT

After refreshing the QuicPanel:

[View:/resized-image/__size/470x459/__key/commentfiles/f7d226abd59f475c9d224a79e3f0ec07-d27de103-bca8-4e6b-8586-2ef78cd96685/contentimage_5F00_216687.png:470:459]

Now I should update some files with my certificates and Wifi settings, but I'm going to skip that.

I'm not going to run the example. Goal is to see if it builds...

RE: PSoC 6 and ModusToolbox: FreeRTOS to AWS MQTT

Jan Cumps — Sat, 23 Oct 2021 17:37:17 GMT

I installed ModusToolbox 2.4, and now can install and compile the AnyCloud MQTT Client example:

[View:/resized-image/__size/620x557/__key/commentfiles/f7d226abd59f475c9d224a79e3f0ec07-d27de103-bca8-4e6b-8586-2ef78cd96685/6354.contentimage_5F00_216685.png:620:557]

I also downloaded Enrico's repo, in a separate folder.

[View:/resized-image/__size/587x379/__key/commentfiles/f7d226abd59f475c9d224a79e3f0ec07-d27de103-bca8-4e6b-8586-2ef78cd96685/4201.contentimage_5F00_216686.png:587:379]

I imported the Nanodrone-II.

For some reason, ( the behaviour is different than in previous ModusToolbox version2.3 I'm not sure anuymore), it created a new shared folder while dong that. (edit: I think this is because my project folder is outside of the workspace folder tree).

RE: PSoC 6 and ModusToolbox: FreeRTOS to AWS MQTT

Jan Cumps — Fri, 22 Oct 2021 07:54:08 GMT

These were the instructions I wrote down. Before executing them, import the Anycloud MQTT example in the same workspace and check if it builds and works.

Then:

After cloning and importing the project into your workspace, perform these activities in the Quick Panel:

open the Library Manager and click Update. Close when finished.
click Refresh Quick Panel.
update mqtt_client.h with your Amazon certificates, and wifi_config.h with your WiFI settings, as you'd do for the AnyCloud MQTT Client example.
click Build Nanodrone-II_PSoC Application

We didn't make lib changes to the makefiles. These are the only modifications: https://github.com/alicemirror/Nanodrone-II_PSoC6/commit/c188050f788979f10cb1cc1b133634a1848d97eb#diff-76ed074a9305c04054cdebb9e9aad2d818052b07091de1f20cad0bbac34ffb52

RE: PSoC 6 and ModusToolbox: FreeRTOS to AWS MQTT

skruglewicz — Fri, 22 Oct 2021 02:56:40 GMT

Hi Again [mention:acaf6a9338de4eef8f6717d5561ed01d:e9ed411860ed4f2ba0265705b8793d05]

Here is the Library manager dialog for yet another try to build the project

What does this mean?

I do not see any library for MBEDTLS?

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

Checking if remote manifest is accessible...
Getting manifests from remote server...
#################################################################################################### 100%
Processing super-manifest https://github.com/cypresssemiconductorco/mtb-super-manifest/raw/v2.X/mtb-super-manifest-fv2.xml...
Successfully acquired the information.

Reading project (C:/PSoC6/Nanodrone-II_PSoC6-main) information...

Successfully acquired project information.

INFO - Warning: Multiple versions of "core-make" requested. Keeping version "latest-v1.X" and discarding version "release-v1.9.0".
INFO - Warning: Multiple versions of "freertos" requested. Keeping version "release-v10.3.1" and discarding version "latest-v10.X".
INFO - Warning: Multiple versions of "whd-bsp-integration" requested. Keeping version "release-v1.1.2" and discarding version "latest-v2.X".
INFO - You have specified to use "freertos release-v10.3.1". There is a new minor or patch version available.
INFO - You have specified to use "whd-bsp-integration release-v1.1.2". There is a new minor or patch version available.

Very weird?

Thanks in Advance

Steve K

RE: PSoC 6 and ModusToolbox: FreeRTOS to AWS MQTT

skruglewicz — Thu, 21 Oct 2021 23:16:03 GMT

Hello [mention:acaf6a9338de4eef8f6717d5561ed01d:e9ed411860ed4f2ba0265705b8793d05]

I hope this comment finds you well.

I've been reviewing your code on the PSoC6 kit for the NanoDrone_II project, which this blog is a part of.

I'm still trying to get the AnyCloud example to work but in the meantime I cloned

"The firmware is available on GitHub: https://github.com/alicemirror/Nanodrone-II_PSoC6 "

I'm using a different kit, the CY8CKIT-062S2-43012 given to me for an element14 design challenge.

In theory (and you state in your GitHub repo) that this should be compatible.

I getting build error?

I have imported the project into ModusToolbox with the "Open Project from File System".

I changed the target= in the makefile and changed the

Library Manager to my kit which is CY8CKIT-062S2-43012

it was CY8CPROTO-062-4343W

I try to build and I get 6 Errors as follows:

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

Description Resource Path Location Type

#error "MBEDTLS_PSA_ITS_FILE_C defined, but not all prerequisites" check_config.h /mtb_shared_2/mbedtls/mbedtls-2.22.0/include/mbedtls line 580 C/C++ Problem

make: *** [../mtb_shared/core-make/release-v1.9.0/make/core/main.mk:434: secondstage_build] Error 2 Nanodrone_II C/C++ Problem

make[1]: *** [../mtb_shared/core-make/release-v1.9.0/make/core/build.mk:387: C:/PSoC6/Nanodrone-II_PSoC6-main/build/CY8CKIT-062S2-43012/Custom/ext/mtb_shared/mbedtls/mbedtls-2.22.0/library/aes.o] Error 1 Nanodrone_II C/C++ Problem

make[1]: *** Waiting for unfinished jobs.... Nanodrone_II C/C++ Problem

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

not sure what the errors mean?

Is "MBEDTLS_PSA_ITS_FILE_C needed?

can I change the makefile in some way to support the CY8CKIT-062S2-43012 kit.

the challenge page on element14 is -----

Thanks in advance

Steve K

PS.. you can send a message directly to me if you would like to communicate in this way.

RE: PSoC 6 and ModusToolbox: FreeRTOS to AWS MQTT

Jan Cumps — Sat, 03 Apr 2021 09:16:46 GMT

The PSoC 6 prototype board that I'm using is modular.

There is a central PCB that holds all logic. And there are 5 break-off boards, a debugger and peripherals.

When they are attached to the central board, they are connected. Small traces run through the mouse bites.

[View:/resized-image/__size/631x431/__key/commentfiles/f7d226abd59f475c9d224a79e3f0ec07-d27de103-bca8-4e6b-8586-2ef78cd96685/1185.contentimage_5F00_207584.png:631:431]

image source: PSoC 6 Wi-Fi BT Prototyping Kit Guide

For some designs it's useful to remove the side PCBs.

Once you separate them, you can still use them by plugging them into the headers of the main board.

But for some boards, it's a bit tricky to count where they have to be placed.

I made it easier to find the correct positions by marking the locations on the main PCB with a permanent silver ink pen.

[View:/resized-image/__size/620x65/__key/commentfiles/f7d226abd59f475c9d224a79e3f0ec07-d27de103-bca8-4e6b-8586-2ef78cd96685/5383.contentimage_5F00_207585.png:620:65]

image source: https://www.penstore.nl/markers/permanent-markers/sakura-pen-touch-permanent-markers/sakura-pen-touch-permanent-marker-e…

The ink is not conductive.

[View:/resized-image/__size/620x436/__key/commentfiles/f7d226abd59f475c9d224a79e3f0ec07-d27de103-bca8-4e6b-8586-2ef78cd96685/2744.contentimage_5F00_207586.png:620:436]

image source: me

When you remove the boards, take care to clean up the cuts. There's always a risk of shortcuts in the ripped traces.

I smoothen the break-off area by scraping the side of the PCB with a cutter.