PSoC™ 6 SDK

I see that the project creation wizard still does not support the CY8CKIT-064S0S2-4343W board in choosing to create a new project based on BSP selection. You have to go through AWS to get a default project and then modify that in situ.

Can we expect BSP support any time soon? We are nearly at the end of 2021.

For example, the Hello-World blink example:

https://github.com/Infineon/mtb-example-psoc6-hello-world

Only supports the B0S2 version and not the S0S2. 

Why?

Hello,

I have created a static library project (libhello-demo) to illustrate the issues I've encountered.  I wanted the project to generate libhello.a, which I can then linked with, in another project.  I'm using ModusToolbox 2.4 in Ubuntu 18.04.5 LTS (64 bit).

The static library has 1 public function:

bool test_me(void) {

    return true;

}

As the implementation does not use any BSP or SDK library, I would like the resultant .a to be usable across all PSoC 6 boards (e.g. PSoc6 Prototyping Kit and Pioneer Kit).

I have attached the steps to reproduce the issues (steps.zip).  Also, I have attached the project code (libhello-demo.zip), although you can also find it on Github (https://github.com/mtb04313/libhello-demo)

The project Makefile has defined LIBNAME=libhello.  Initially, I set TARGET=CY8CPROTO-062-4343W, so that I can perform make getlibs successfully in Step 1

Then make build in Step 2 fails. 

To workaround the failure, I temporarily comment out LIBNAME line, and added APPNAME=apphello instead (shown in Step 3).  Now, make getlibs downloaded a bunch of dependencies into mtb_shared (capsense, core-lib, core-make, mtb-hal-cat1, mtb-pdl-cat1, psoc6cm0p, recipe-make-cat1a).

Then in Step 4, I reverted to LIBNAME=libhello (commenting out APPNAME line).  This time, make build succeeded and produced libhello.a.

My questions are:

1. Why don't "make getlibs" and "make build" work with LIBNAME=libhello?  Why do I have to fake an APPNAME?

2. How can I avoid defining a TARGET, so that my static library does not require a bunch of unnecessary Capsense and BSP files during compilation, and so have the static library work with any PSoC 6 boards?

3. Can I make the resultant library usable for both M4 and M0 cores?

Thanks!

Best Regards,

SK

   请问一下，ModusToolbox如何根据芯片具体型号创建项目，如：使用芯片CY8C6316BZI-BLF03、CY8C614ABZI-S2F44等等。（像Creator 一样可以选择芯片型号）

     ModusToolbox如何选择芯片进行创建项目，而不是通过选择开发板型号创建项目。通过开发板型号创建，不清楚如何更改芯片型号。

      如过法使用芯片型号创建项目，在使用某款芯片时不知道如何选择芯片。例如：要使用CY8C6316BZI-BLF03或者CY8C614ABZI-S2F44时，无法通过选择芯片型号创建项目，在引脚和各种资源配置上，就不清楚如何使用ModusToolbox来开发。

     有过有教程手册，麻烦给一下地址。

Attempting to run example from PSoC6 CapSense UART Tuner Sample Project in ModusToolBox using ModusToolbox 2.4.

I'm currently stuck at an error when attempting to Build the project that shows up in the Console:

Error: Program "${cy_tools_path:CY_TOOL_modus-shell_BASE}\bin\make" not found in PATH

Are there path requirements that aren't automatically created with ModusToolbox 2.4?

Attached is the process followed when attempting to run the Sample Project. My first two attempts failed due to a space in the path I used to locate the unzipped example. The third try, I wasn't sure how to run "make getlibs" so I tried another approach, which brought me to the Error in Path issue.

Greg

Hello to all,

I have build a project but there are some warnings .

I want to revise the following warnings：

1,ignoring #pragma arm section [-Wunknown-pragmas]:

How to use  "__attribute__((section("name")))" instead of "#pragma arm section" ?

2,always_inline function might not be inlinable [-Wattributes]:

How to solve this warning?

Can you please help me to get rid of the warnings?

Best Wishes，

JCD

I work in a virtual computer environment and can therefore use the variables CY_TOOLS_PATHS: = C: /Infineon/Tools/ModusToolbox/tools_2.3 and CY_GETLIBS_CACHE_PATH: = C: /Users/user/.modustoolbox/cache do not set in windows.

I have set the PATH variable in the Makefile and in the IDE.

Now comes this error

Log file (s) for this session are stored at: C: \ Users \ user \ AppData \ Local \ Temp \ Logs5065691172615597458 Modus Toolbox is not installed in the default location and the CY_TOOLS_PATHS variable is not set. Unable to get app info: 0 [main] make (9700) C: \ Infineon \ Tools \ ModusToolbox \ tools_2.3 \ modus-shell \ bin \ make.exe: *** fatal error - add_item ("\ ?? \ C: \ Infineon \ Tools \ ModusToolbox \ tools_2.3 \ modus-shell "," / ", ...) failed, errno 1

Stack trace: Frame Function Args

000FFFFAC30 0018006074E (0018026E89A, 0018024A1B9, 00600010000, 000FFFF8B40) 000FFFFAC30 00180049239 (000FFFF9BC0, 000FFFFAC30, 00000000000, 00000000000) 000FFFFAC30 00180049272 (000FFFF9BC0, 00000000001, 00600010000, 495C3A435C3F3F5C) 000FFFFAC30 001800D7D0C (00000000000, 00040000024, 00000000000, 00000000000) 1D7CB23A5658D70 001801265B5 (001800C0C5C, 00000000000, 00000000000, 00000000000) 000FFFFCCD0 00180049863 (00000000000, 00000000000, 00000000000, 00000000000) 00000000000 00180048353 (00000000000, 00000000000, 00000000000, 00000000000) 000FFFFFFF0 00180048404 (00000000000, 00000000000, 00000000000, 00000000000)

End of stack trace not on the local computer.

I don't know what to do