ModusToolbox™ General Forum Discussions

Dear Sirs and Madams,

We are using the LIN sample project on Github as a reference.

mtb-example-psoc4-lin-slave project URL

https://github.com/Infineon/mtb-example-psoc4-lin-slave

Using the "make getlibs" command and "make eclipse" command, We successfully built and confirmed the operation.

However, there is an unknown point in this project.

When We confirm for "Device configurator", it is not checked under "Peripherals" and "Pins".

[Peripherals]

[Pins]

If it is written in the "resource_ map.h" as shown below, is it possible not to check the corresponding "Peripherals" and "Pins" checkboxes in the device configurator?

[Resource_map.h]

For example, if you check the check boxes for pins P3[0], P3[1], P3[4], P3[6] and P2[6], it will not work properly.

Also, when We would like to use LIN communication in Modus Toolbox , is it possible to use it only if it is described by such a "resource_map.h"?

Please tell us about the relationship between "Device Configurator" and "resource_map.h" in the this "mtb-example-psoc4-lin-slave project".

Regards,

以前的项目一直用V2.2开发，以后的项目准备用V2.4开发。

现在同一台PC里安装了这2个版本的MODUS，但是用V2.2的MODUS打开以前的项目build时发现MODUS用的是

V2.4的GCC编译，请问怎么解决两个版本共存的问题？

Previous projects have been developed with V2.2, and future projects are ready to be developed with V2.4.

Now these two versions of modus are installed on the same PC, but when opening the previous project build with Modus V2.2,it is found that Modus is compiled with V2.4 GCC. How can we solve the problem of the coexistence of the two versions?

Dear Sirs and Madams,

We have a question about the checksum of the HEX file generated by Modus Toolbox.

Does "03B1" in the HEX file below correspond to the checksum?

Also, is this checksum little endian like ARM Cortex in general?

We confirmed for help menu of ModusToolbox and user guide (002-29893) but did not hit "checksum".

Please let us know if you have any documents that explain the checksum.

Regards,

Hi,

KitProg3 User Guide, chapter 2.2.5.2 GPIO Bridge Feature, says...

You can also use fw-loader GPIO dedicated command line options to set mode and state of GPIO pin:
fw-loader --set-kp3-gpio-pin <pin_number> <pin_mode> <state>

Use this command to read the current state of a pin:
fw-loader --read-kp3-gpio-pin <pin_number>

For example, to set 3[5] (port 3, pin 5) GPIO pin to High state in ResUp operational mode, use
fw -loader --set-kp3-gpio-pin 35 ResUp 1

To read current state of 3[6] (port 3, pin 6) GPIO pin, use:
fw -loader --read-kp3-gpio-pin 36

I'm using the latest fw-loader version which Infineon provides via github - which is version 3.3.0. But whenever I try to execute one of the recommendended commands, I get an error saying that I'm using an uncrecognized command:

fw-loader --read-kp3-gpio-pin 36
Cypress Firmware Updater, Version: 3.3.0.1370
(C) Copyright 2018-2021 by Cypress Semiconductor Corporation (an Infineon company)
All Rights Reserved

Error: Unrecognized command '--read-kp3-gpio-pin'. Run the app without arguments to see all supported command line options

If I'm executing fw-loader without arguments the command read/set-kp3-gpio-pin is missing... which is a bit confusing. Has anyone any idea what could be going wrong here?

Dear Sirs and Madams,

Please tell us about "make getlibs" and "make eclipse" commands of Modus-shell in the answers to the questions asked in the community below.

https://community.infineon.com/t5/PSoC-4/PSoC4S-MAX-LIN-sample-project-in-ModusToolbox-2-4/td-p/358849

Is there any documentation that details these commands?

We don't understand which folder in the sample code to use the "make getlibs" command and which folder to use the "make eclipse" command.

Regards,

Hello,

when I add svd file to see the peripheral register,every port (port0 to port14) has the same address.

※modus version is 2.2

But in another version（2.3）,GPIO shows a correct address .

Was it a bug in version 2.2 Or   I did a wrong config?.

I would really like to migrate my PSoC Creator 4.4 projects to ModusToolbox, but it still does not support the PSoC 4200 family because of the PSoC 4's UDB blocks, as far as I can tell.  PSoC Creator is really showing its age and has not been updated since October of 2020.

Is full PSoC 4200 support planned for ModusToolbox, and if so, when can we expect it?

Hi,

"CapSense Configulator" and "CapSense tuner" have been released for debugging touch sensitivity.
On the other hand, what are the monitoring and tuning tools in ModusToolbox for general-purpose ?

Best regards,
Kazunari Hayashi

Hi ~ Receiver,

In the past, we used PSoC Creator to design MCU peripheral. By using PSoC Creator GUI, we can easily initial MCU peripherals.

Now, if we are forced to use MTB to develop PSoC 6 we will meet many difficulties.

For example, in the attached file we can see a TopDesign picture.

It has a I2S block, filp-flop, DMA and inverter blocks, etc.

If I want to use MTB to achieve this TopDesign,,, 

How should I start ?! Please kindly guide me.

Thank you so so much.