ModusToolbox™ General

Hi! I am new to Modus and psoc6. 
I have a few questions about Release vs Debug builds. 
1)

The Makefile CONFIG variable seems to be the way to build the project in Release or Debug mode. 
The IDE build configuration does not seem to affect the actual code build. 

IDE Debug build config -> builds with the CONFIG setting hard coded in Makefile

IDE Release build config -> builds with the CONFIG setting hard coded in Makefile.

In the Makefile, if I set CONFIG=Release, I see -DNDEBUG in my GCC build.
In the Makefile, if I set CONFIG=Debug, I see -DDEBUG in my GCC build. 
This is the result I expect for a Debug vs Release build.

Changing the IDE build config does not give me the DEBUG/NDEBUG I expect.
Can anyone confirm this? What's the best way to accomplish this? 

2) 
Launch configurations are not behaving reliably either with specifying the hexfile path in project settings. 

a) ${config_name:MyProject} -> always renders to Debug, despite IDE Build Configuration 
b) Hard code ALL launches to load the Release hex file (the IDE generated all launches to load the Debug hex file)
    With everything set to Release, Makefile and IDE, and my launch config, it still Error's out when it tries to program
    Error: couldn't open /Users/mike/work/xxxx/yyyy/MyProject/build/CY8CPROTO-062-4343W/Debug/MyProject.hex

What is the proper way to manage which build configuration / hexfile that the launch will use? 
Does IDE Build Configuration actually do anything?

I've also learned that IDE 'exclude files from build' does nothing, and I had to include/e
Thanks!

After linking, I get this output, but not all of my projects have PROGBITS lines. 

They are really not useful and keep me from seeing what I want to see. How can I turn off PROGBITS?

Calculating memory consumption: CYBLE-416045-02 GCC_ARM -Og

----------------------------------------------------
| Section Name | Address | Size |
----------------------------------------------------
| .cy_m0p_image | 0x10000000 | 6428 |
| .text | 0x10002000 | 106568 |
| PROGBITS | 0x1001c048 | 72 |
| PROGBITS | 0x1001c090 | 132 |
| PROGBITS | 0x1001c114 | 20 |
| PROGBITS | 0x1001c128 | 24 |
| PROGBITS | 0x1001c140 | 36 |
| PROGBITS | 0x1001c164 | 28 |

.. and hundreds of PROGBITS entries. 

Dear Sirs and Madams,

I asked the following questions in the past:

https://community.infineon.com/t5/ModusToolbox-General/Modus-Tool-Box-BSP-of-quot-KIT-XMC-2GO-XMC1100-V1-quot/td-p/324617

I am trying to change it according to the procedure below, but I cannot successfully generate a custom BSP.

https://community.infineon.com/t5/Knowledge-Base-Articles/ModusToolbox-2-2-and-later-Make-a-Custom-BSP-KBA231373/ta-p/251107

First, I found that the part number used in the command below was incorrect.

$ make bsp TARGET_GEN=MyBSP DEVICE_GEN=XMC1100_Q024x0064

The command will pass correctly if you change the part number.

$ make bsp TARGET_GEN=MyBSP DEVICE_GEN=XMC1100-Q024x0064

However, when I change the makefile to "TARGET = MyBSP", save it, and execute the "make config" command, the following error occurs.

Therefore, we cannot use the KITXMC2GO evaluation board with ModusToolbox.

Do we have no choice but to wait for the XMC1100 BSP to be released?

Is it possible to successfully generate a custom BSP for the XMC1100?

My development environment is as follows.

ModusToolbox 2.4

modus-shell 1.3.0

Empty XMC App of XMC-GENERIC BSP

For reference, either method (a) modus-shell 1.3.0 applicaion  or (b) Terminal of ModusToolbox will result in an error.

Regards,

Hello Infineon Support,

I'm trying to setup a I2C Master device which will run on the CM0P core of the CY8CPROTO-062-4343W proto board.  It isn't working correctly for me and I'm wondering if I setup my interrupts correctly for the CM0P core, since it's different than the setup for CM4 which is in the docs.

Here is my setup:

void I2C_Isr(void) {
    Cy_SCB_I2C_MasterInterrupt(mI2C_HW, &i2cContext);
}

void i2c_init(void)
{
    // Reference: https://infineon.github.io/mtb-pdl-cat1/pdl_api_reference_manual/html/group__group__scb__i2c.html

    cy_en_scb_i2c_status_t initStatus;
    cy_en_sysint_status_t sysStatus;

    // Initialize I2C
    initStatus = Cy_SCB_I2C_Init(mI2C_HW, &mI2C_config, &i2cContext);
    if (initStatus != CY_SCB_I2C_SUCCESS) {
	    CY_ASSERT(0);
    }

    // Initialize the interupt
    #if (CY_CPU_CORTEX_M0P)
        const cy_stc_sysint_t i2cIntrConfig =
        {
            .intrsrc=NvicMux6_IRQn,
            .cm0psrc=mI2C_IRQ,
            .intrPriority = 3,
        };
    #else
        const cy_stc_sysint_t i2cIntrConfig =
        {
            .intrsrc=mI2C_IRQ,
            .intrPriority = 7,
        };
    #endif

    /* Hook interrupt service routine and enable interrupt */
    sysStatus = Cy_SysInt_Init(&i2cIntrConfig, &I2C_Isr);
    if (sysStatus != CY_SYSINT_SUCCESS) {
	    CY_ASSERT(0);
    }

    NVIC_EnableIRQ((IRQn_Type) i2cIntrConfig.intrSrc);

    /* Enable I2C to operate */
    Cy_SCB_I2C_Enable(mI2C_HW);

    /* Enable global interrupts */
    __enable_irq();
}

  What's happening is the first time I call Cy_SCB_I2C_MasterWrite(), Cy_SCB_I2C_MasterGetStatus() starts to return CY_SCB_I2C_MASTER_BUSY and never returns anything else.  It seems like this normally happens if the interrupt isn't setup correctly.  I've also confirmed that the I2C bus is not busy before the call:

void i2c_wait(void) {
    /* Wait for transaction completion */
    while (0UL != (CY_SCB_I2C_MASTER_BUSY & Cy_SCB_I2C_MasterGetStatus(mI2C_HW, &i2cContext))) {}
}  
    ....
    i2c_wait(); // This one returns instantly

    /* Initiate write transaction.
    *  The Start condition is generated to begin this transaction.
    */
    result = Cy_SCB_I2C_MasterWrite(mI2C_HW, &transfer, &i2cContext);

    i2c_wait(); // This one never returns

I've also probed the SCL and SDA lines and confirmed that the transaction never starts on the hardware.  They are always at 3.3 V, so not even the start command is sent.

Lastly, here's my configuration for the SCB block in the device configurator:

Please let me know if there's anything I've configured wrong.

Best regards,

Cory

Hello Infineon Support,

I'm trying to setup ModusToolbox on a Raspberry Pi build server my team has for running builds with CI/CD.  I was able to install ModusToolbox on the Pi without any issues.

However, when I try to run make getlibs inside my project folder, I get the following output and error:

$ make getlibs
Tools Directory: /build/tools/ModusToolbox/tools_2.4/
make -C ../app_cm0p/ getlibs
make[1]: Entering directory '/var/lib/gitlab-runner/builds/<build-dir>/app_cm0p'
Tools Directory: /build/tools/ModusToolbox/tools_2.4/
==============================================================================
= Importing libraries =
==============================================================================
/build/tools/ModusToolbox/tools_2.4/proxy-helper/proxy-helper: 4: exec: /build/tools/ModusToolbox/tools_2.4/proxy-helper/bin/proxy-helper: Exec format error
make[1]: *** [/build/tools/ModusToolbox/tools_2.4//make/getlibs.mk:121: getlibs] Error 2
make[1]: Leaving directory '/var/lib/gitlab-runner/builds/<build-dir>/app_cm0p'
make: *** [Makefile:210: getlibs_cm0p] Error 2

We have been trying to debug an issue where project creator is not generating the application .git directory when a new application is created.  This is breaking our build process with our custom applications.

 We have isolated the issue to modus 2.4 and can readily reproduce even with stock Infineon BSPs and  Infineon sample apps. 2.3 always works, 2.4 never works.

To reproduce:

In Modus_2.4 open project creator (1.4) , select BSP  CY8CPROTO-063-BLE and create a new 'Hello World' application. The project successfully completes, and the log sure looks like git is happy, but no .git folder is created in the project directory. (see 2.4_no_gitFolder.gif)

Summary: 

BSP: CY8CPROTO-063-BLE
Template Application(s): Hello World
Application(s) Root Path: D:/Data/ModusEclipse/mtw

Press "Create" to create the selected application(s).
Collecting application data...


Info: The following entered on the command line will create the exact same project as that created with the GUI tool:
C:/Infineon/Tools/ModusToolbox/tools_2.4/project-creator/project-creator-cli.exe --board-id CY8CPROTO-063-BLE --board-uri https://github.com/cypresssemiconductorco/TARGET_CY8CPROTO-063-BLE --board-commit latest-v3.X --app-id mtb-example-psoc6-hello-world --app-uri https://github.com/cypresssemiconductorco/mtb-example-psoc6-hello-world --app-commit latest-v3.X --cypress-tools C:/Infineon/Tools/ModusToolbox/tools_2.4 --target-dir D:/Data/ModusEclipse/mtw --user-app-name Hello_World --output-for-machine --use-modus-shell


==============================================================================
= Cloning 'mtb-example-psoc6-hello-world' =
==============================================================================
Cloning https://github.com/cypresssemiconductorco/mtb-example-psoc6-hello-world into D:/Data/ModusEclipse/mtw directory...
env git clone --progress --origin cypress https://github.com/cypresssemiconductorco/mtb-example-psoc6-hello-world Hello_World
Cloning into 'Hello_World'...
remote: Enumerating objects: 56, done.        
remote: Total 56 (delta 0), reused 0 (delta 0), pack-reused 56        
Receiving objects: 100% (56/56), 204.53 KiB | 10.76 MiB/s, done.
Resolving deltas: 100% (21/21), done.

Checking out latest-v3.X...
env git checkout --progress latest-v3.X
Note: switching to 'latest-v3.X'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by switching back to a branch.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -c with the switch command. Example:

  git switch -c <new-branch-name>

Or undo this operation with:

  git switch -

Turn off this advice by setting config variable advice.detachedHead to false

HEAD is now at a1d784d Upload mtb-example-psoc6-hello-world 3.0.0.905

==============================================================================
= Creating "TARGET_CY8CPROTO-063-BLE.mtb" file(s) =
==============================================================================

Perform the same operation in Modus 2.3 (Project Creator 1.3). looks similar but a (populated) .git folder is created in the project directory. This works. (see 2.3_gitFolder.gif)

Summary: 

BSP: CY8CPROTO-063-BLE
Template Application(s): Hello World
Application(s) Root Path: D:/Data/ModusEclipse/mtw

Press "Create" to create the selected application(s).

Collecting application data...


Info: The following entered on the command line will create the exact same project as that created with the GUI tool:
C:/Infineon/Tools/ModusToolbox/tools_2.3/project-creator/project-creator-cli.exe --board-id CY8CPROTO-063-BLE --board-uri https://github.com/cypresssemiconductorco/TARGET_CY8CPROTO-063-BLE --board-commit latest-v2.X --app-id mtb-example-psoc6-hello-world --app-uri https://github.com/cypresssemiconductorco/mtb-example-psoc6-hello-world --app-commit latest-v2.X --cypress-tools C:/Infineon/Tools/ModusToolbox/tools_2.3 --target-dir D:/Data/ModusEclipse/mtw --user-app-name Hello_World_1 --output-for-machine --use-modus-shell


==============================================================================
= Cloning 'mtb-example-psoc6-hello-world' =
==============================================================================
Cloning https://github.com/cypresssemiconductorco/mtb-example-psoc6-hello-world into D:/Data/ModusEclipse/mtw directory...
env git clone --progress --origin cypress https://github.com/cypresssemiconductorco/mtb-example-psoc6-hello-world Hello_World_1
Cloning into 'Hello_World_1'...
remote: Enumerating objects: 56, done.        
remote: Total 56 (delta 0), reused 0 (delta 0), pack-reused 56        

Checking out latest-v2.X...
env git checkout --progress latest-v2.X
Note: checking out 'latest-v2.X'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b <new-branch-name>

HEAD is now at 2d0432b Upload mtb-example-psoc6-hello-world 2.2.0.857

==============================================================================
= Creating "TARGET_CY8CPROTO-063-BLE.mtb" file(s) =
==============================================================================