ModusToolbox General

Hello,

I started using modustoolbox, I decided to start  with the pwm demo, because I want to control 30 pwm independently. From what I understood from the HAL interface, this interface makes it easier to use hardware modules.

I would like to know if it is possible to have a summary of the use of hardware modules by the hal library and the rest.

Best regards,

Maxime

Hello,

I have installed Modus Toolbox , and uninstall and install again in different location, after installation, I try to import an object by file->new->Modus toolbox App, it come following info:

Log file(s) for this session are stored at: C:\Users\xlu\AppData\Local\Temp\Logs7924986194417700111
Unable to find ModusToolbox executables:
Unable to execute project creator command.

For the first installation, we can run this  function smoothly. but after uninstall and install again it cannot run. we also try to reinstall again in the same location as the first installation, but failed. Could you please help me out

I add 2 Mesh Demo projects to Modus Toolbox IDE.Both projects use shared libraries and tools.

If i select one of the projects or an integrated file the Quick Panel is updated with information. That takes a lot of time (up to ~1 min) and blocking the IDE. Everytime i switch the project the Quick Panel is updated and blocking the whole IDE.

Is it possible to prevent an update of the quick panel? And if so, how can i prevent this?

I want to familiarize myself with the software and have to switch between the shared library header and / or the projects.

Thanks for your help

Hi,

What should I install exactly?

See the screenshot

Is there a list of required make files or instructions on how to set CY_TOOLS_PATH?

Following Linux installation of ModusToolbox 2.2 and the 2.2.1 patch on a Ubuntu 20.10 system. Everything appears to work. The Post-Install Script run from a terminal returns "make not found".

When I open ModusToolbox IDE, all looks good until I click "New Application", which puts the following text into the Console of ModusToolbox IDE, "Unable to find tools information: Cannot run program "<my_path>/ModusToolbox/tools_2.2/modus-shell/bin/make" Is the CY_TOOLS_PATH set correctly?"

Then when attempting to create a new application, a specific make file can't be found:

Project creation command to be executed:

/home/<user_name>/ModusToolbox/tools_2.2/project-creator/bin/project-creator-cli --board-id CY8CKIT-062-WIFI-BT --board-uri https://github.com/cypresssemiconductorco/TARGET_CY8CKIT-062-WIFI-BT --board-commit latest-v2.X --app-id mtb-example-psoc6-capsense-buttons-slider-freertos --app-uri https://github.com/cypresssemiconductorco/mtb-example-psoc6-capsense-buttons-slider-freertos --app-commit latest-v2.X --user-app-name CapSense_Buttons_and_Slider_FreeRTOS --target-dir /home/<user_name>/Documents/PSoC64_A/MTBa --output-for-machine --use-modus-shell

"make -f get_tool_info.mk get_tool_info" failed: execvp: No such file or directory

Getting manifest...

Hi

How to set optimization level in ModusToolbox?

I'm also looking for other settings, see the screenshot

In learning the differences between the MTB and LIB flows in Modus Toolbox, I have been wondering if there is an existing hybrid approach. For example, if I have a number of projects in my workspace that use FreeRTOS, I understand the appeal of MTB flow in that I don't need to have multiple copies of FreeRTOS for each project. However, I would potentially want to have unique copies "FreeRTOSConfig.h" for each project (if they take advantage of different RTOS features and have different heap requirements for instance). It is also my understanding that updating FreeRTOS with the library manager in MTB flow would essentially eliminate all my custom settings in "FreeRTOSConfig.h" (as it would be replaced by a copy of the file from the new downloaded version). For these reasons, I would want a way to leave "FreeRTOS" in the mtb_shared directory to avoid redundancy, but during the build process I would want to combine the library with a local project copy of "FreeRTOSConfig.h" to customize the build.