cancel
Showing results for 
Search instead for 
Did you mean: 

ModusToolbox™ General

MotooTanaka
Esteemed Contributor

Hi!

This morning I downloaded and installed the ModusToolbox_1.0.0.2953-windows-install.exe.

Then I watched the four tutorial videos.

They were very nice and clear to be understood.

And I misunderstood myself ready to go.

I Started ~\ModusToolbox_1.0\eclipse\ModusToolbox.exe

I selected the menu File > New > ModusToolbox IDE Applicaiton

I selected Dev/Eval Kit

And selected CY8CKIT-062-BLE, as it's the only PSoC 6 evb I have right now.

For the Starter Application, although I wanted try some FreeRTOS,

I decided not to take chance, so I selected BlinkyLED.

When I selected "Finish" button, I got following dialog saying "Problem Occurred."

000-Problem-Occurred.JPG

Although I'm sure that I'm good at encountering problem(s),

I'm a little bit bewildered about what to do next.

moto

1 Solution
MotooTanaka
Esteemed Contributor

Well, I'm afraid that I found the reason.

So I gave up the sample project and tried to create an empty project for CY8C6347BZI-BLD53.

Then I got following error dialog!

003-Problem_Occurred.JPG

And now I understand the reason (or at least one reason),

that is in our company/office the security does not allow us run "bash"

So unless I can manage to convince the management/security

that I need to use bash and let them allow me to run one,

it will be very difficult to create a project...

moto

View solution in original post

0 Likes
31 Replies
MotooTanaka
Esteemed Contributor

One thing I should have mentioned in the original post is that

I set my work space to

C:\Cypress\PSoC\PSoC6\MTW100

moto

0 Likes
MotooTanaka
Esteemed Contributor

I tried a few more times with different options, but all came back with similar errors.

Then I noticed that in the console pane it says

Log file(s) for this session are stored at: C:\Users\700650\AppData\Local\Temp\Logs2352646260215400188

So I went to dig that folder, attached is the log file I found there.

moto

0 Likes
MotooTanaka
Esteemed Contributor

Reading the release note, I noticed that the KitProg2 has to be updated to KitProg3,

so I ran fw-loader as below

002-KigProg3-update.JPG

Then I rebooted my PC and tried to create the project again and got similar error.

Attached is the log file of this trial.

moto

0 Likes
MotooTanaka
Esteemed Contributor

Well, I'm afraid that I found the reason.

So I gave up the sample project and tried to create an empty project for CY8C6347BZI-BLD53.

Then I got following error dialog!

003-Problem_Occurred.JPG

And now I understand the reason (or at least one reason),

that is in our company/office the security does not allow us run "bash"

So unless I can manage to convince the management/security

that I need to use bash and let them allow me to run one,

it will be very difficult to create a project...

moto

View solution in original post

0 Likes
mattl_01
Employee

Hey Motoo,

I am so sorry you ran into all these problems.  We do use bash as a shell to run commands like make.  Your IT group probably does not want users running bash as a generic shell because it had security issues back in 2014 (See shellshock).  The way we use bash would not be susceptible to that, and we use an old version that was prior to it having those vulnerabilities anyway.  That Wikipedia page I reference even shows commands you can run to show it's not vulnerable.  I think it is only a problem with Linux/Unix/Mac systems.

My belief is that if you removed /bin/bash (since your security team won't let you run it anyway), then it would find the bash in $CYSDK/tools. Check with your IT/security team to make sure it's OK by them.

Here is more about shellshock from Symantec.

Unfortunately, ModusToolbox (nor almost any tool) cannot run without a shell to execute commands, and the shell we use is bash.

Let us know how it goes.

Regards,

--Matt

MotooTanaka
Esteemed Contributor

Dear Matt-san,

Thank you very much for your information!

I was not quite aware of that bash bug.

Anyway, I asked my manager to submit bash usage permission application to the security.

Although I could not use bash whole day yesterday, this morning when I tried to start my cygwin, which has been dead quite a while now, the shell prompt came up just like the yesteryear.

Then I started ModusToolbox and tried to create an empty Modus IDE project for CY8C6347BZI-BLD53.

Yes, it worked fine this time.

000-MTW100.JPG

Finally, I'm ready to start exploring the new territory.

Scotty, beam me up!

moto

P.S. A couple of additional notes

(1) I'm using "Windows7" not linux nor MacOSX

(2) Since the "Error Occurred" dialog does not have scroll bar

  nor it saves the message (at least I know of),

  unless I tried with an empty project,

  I could not have found that the root cause was "bash"

0 Likes
mattl_01
Employee

Great, Tanaka-san! I am so happy you got past that. 

With regards to the error message.  You've uncovered something we had not anticipated. I'll talk to the developers about coming up with a better error message (or at least why it didn't get written to the log file).

Have you had a chance to look at any of the links/videos the Welcome page. I'd like to get some feedback on them and on our Quick Start Guide.

One thing i'd also like to point out is the Documentation. It's one of my favorite things.  You get to it by going to Help->General Documentation like this

pastedImage_2.png

Best Regards,

--Matt

MotooTanaka
Esteemed Contributor

Dear Matt-san,

Thank you very much for your response and information!

> Have you had a chance to look at any of the links/videos the Welcome page.

> I'd like to get some feedback on them and on our Quick Start Guide.

I have watched the first 4 Video Tutorials, which made me feel like I'd like to try by myself.

Well, I'll check the "Quick Start Guide"

> One thing i'd also like to point out is the Documentation. It's one of my favorite things. 

> You get to it by going to Help->General Documentation like this

I'll check that menu, too.

Again, thank you very much for your help(s)!

Best Regards,

19-Dec-2018

Motoo Tanaka

0 Likes
MotooTanaka
Esteemed Contributor

Dear Matt-san,

Following is my first trial and personal review of the Quick Start Guide

(1) Initial Screen shows Welcome page.

    May be mentioning it could avoid some surprise(s)

    After dismissing the "Welcome" we arrive at the workbench.

000-Initial-screen.JPG

(2) Page 3 (Step 2)

As I don't have CY8CKIT-062-WIFI-BLE, I selected CY8CKIT-062-BLE

(3) Step 5

after "focus on the <app-name>_mainapp project.

Specifying the real name, for example

In this example, "BlinkyLED_mainapp"

would be easier to understand.

(4) May be showing the upper-left half (1/4) of the workbench

could be easier to locate/notice the project name.

001-Projects.JPG

(5) Add/Modify Application Code

The appearance of main.c when started first is totally different.

May be suggesting "scroll down the window up to where we see the code"

or something will be helpful for the "hardcore beginners"

003-main_c.JPG

(6) The Save/Save As commands will also available to select.

(May be I'm too picky but) I wonder if we should mention that

they are in the File Menu and/or in the menu icon bar.

BTW, Isn't "Save As" command always available?

(7) Configure Device Resource

The screen shot shows different project name "CapSenseSlider_config"

I would suggest to stick with the same project.

(8) Expand the <app-name>_config project

and double click the design.modus file.

It would be nicer to specify that you need to look into Quick Panel.

So I would say something like

Expand BlinkyLED_mainapp in the Quick Panel

then double click Configure Device

(9) When I double clicked the Configure Device,

Device Configurator Dialog showed up

and I received an Error Dialog.

002-Device-Configurator-with-error.JPG

Since I'm not sure if I should proceed, I'm stopped here.

(If I hack through, I won't be able to review the rest of the document)

moto

0 Likes
MotooTanaka
Esteemed Contributor

Well I noticed that if I only single click the "Configure Device" I could start Device Configurator without problem.

(It would be nice if Quick Panel detects "double click" and gracefully ignores the second click.)

moto

0 Likes
MotooTanaka
Esteemed Contributor

(10) Build the Application

"You can also select select Build ModusToolBox Application from the Project menu."

(10.1) there are two "select"s

(10.2) The Project Menu seems different

004-Project-Build.JPG

-> I needed to select "BlinkyLED_mainapp" in the Project Explorer then menu seemed similar, I miss the "set as active" menu.

004-Project-Menu.JPG

Note: I build with Quick Panel "Build BlinkyLED Application"

(11) Program

The last message of program "shutdown command invoked" sounds

somewhat intimidating. Showing the image of display may mitigate it.

005-program-finished.JPG

(12) After program flashed, my "CY8CKIT-062-BLE" did not blink any LEDs.

Note: May be there is/are problem with CY8CKIT-062-BLE sample...

(13) Debug the Program

I selected "BlinkyLED Debug (KitProg3)

And got following screen

006-Blinky_Debug.JPG

And when I pushed the pause icon

007-Blinky_debug_paused.JPG

So I suppose that if I did not have problem in the BlinkyLED project

I should have been able to build the project and invoke the debugger.

I will try to see if I can fix the project but anyway, it's not the topic of this thread.

moto

0 Likes
mattl_01
Employee

Tanaka-san,

Thank you for the detailed review and suggestions for our quick start.  If you ever get tired of embedded design you should be a technical editor!

Now, let's talk about the BlinkyLED project issues.  I have that same board, and it's working OK for me.  I'm going to put aside the error messages for the debugger for the time being.  Here are four things I would like you to do.

1. Do you see SW5 in the middle of that board?  It's that white 3-position switch.  Put it in the middle position so it will be configured like my board.

2. Can you give me the result of a fw-loader.exe command?  Here's how to do that

i. Go to $CYSDK.tools\fw-loader-1.0\bin in Windows Explorer

ii. In the right pane, do a Shift-Right Click of your mouse and select "Open command window here"

iii. type fw-loader-1.0 --device-list

It should look something like

pastedImage_3.png

If it says "HID" instead of "BULK" that's OK.

3. In the Quick Panel, do a "Clean BlinkyLED Application" then Make, then just a plain Program (should be the bottom entry in the Launches section of the Quick Panel"

4. Look on the back of your board, bottom left-hand side, and tell me your revision number (for example Rev 11 or Rev 13)

We'll go from there.

Thanks,

--Matt

0 Likes
MotooTanaka
Esteemed Contributor

Dear Matt-san,

Following the observations

> 1. Do you see SW5 in the middle of that board?  It's that white 3-position switch.

> Put it in the middle position so it will be configured like my board.

SW5 of my board was also in the middle position.

IMG_3166.JPG

> 2. Can you give me the result of a fw-loader.exe command?

000-fw-loader-TeraTerm_log.JPG

> 3. In the Quick Panel, do a "Clean BlinkyLED Application" then Make,

> then just a plain Program (should be the bottom entry in the Launches section of the Quick Panel"

(3.1) Clean selected and finished cleaning

001-Clean-BlinkyLED_Application.JPG

(3.2) Build selected and built

002-Build.JPG

(3.3)  BlinkyLED Program (KitProg3) selsected

003-BlinkyLED-Program_KitProg3.JPG

(3.4) Program finished

004-Program-finished.JPG

Note: At this point not LED blinking and even with RST switch pushed no blinking

(3.5) I also tried "BlinkyLED Debug (KitProg3)

005-BlinkyLED_Debug__KitProg3.JPG

(3.6) Debugger started (?)

006-Debug-screen.JPG

> 4. Look on the back of your board, bottom left-hand side,

> and tell me your revision number (for example Rev 11 or Rev 13)

==============

121-60367-01 Rev 11

1744SO00652

==============

IMG_3167.JPG

FYI, With PSoC Creator 4.2, attached project can be built, programmed, and debugged fine.

RED LED blinks ok. So I think that at least "some" part of the board is alive.

moto

0 Likes
mattl_01
Employee

moto-san, you need a new board.  I know it may not seem like it since it

works with Creator, but I am pretty sure that is the issue.

Can you email me at mdl@cypress.com please?

Sorry for these issues.

--Matt

0 Likes
MotooTanaka
Esteemed Contributor

Dear Matt-san,

I have sent you a short mail.

Best Regards,

20-Dec-2018

Motoo Tanaka

0 Likes
jomoc_3144201
New Contributor II

I'm seeing the same issue with a Rev. 8 Board.  I can program this board without issue with PSoC Creator but the BlinkyLED example from ModusToolbox does not work as the OP has shown. Does this mean I need a new board as well?

0 Likes
mattl_01
Employee

Jon, I am 90% sure yes.
I think it will still work fine with your current version of Creator/Programmer, but not ModusToolbox.

Who did you get the kit from? Can you ask them to send you a new one and Cc me (mdl@cypress.com)

on the communication?

We need a smooth way of doing this, but I don't think we'll be able to get anything set up before

the new year.

--Matt

jomoc_3144201
New Contributor II

I got the board from element14 but it is working fine with PSoC Creator so I am okay with that for now.

However, I am curious to know what version of PDL that ModusToolbox is using.  I noticed when I tried to use PDL 3.1 with the CY8CKIT-062-BLE I had seen similar behavior where the code would compile and load without issue but would not run on the kit. I had to down rev to PDL 3.0.4 or earlier to get it to work so It would be interesting to know if there is a similar issue with ModusToolbox.

0 Likes
mattl_01
Employee

Hey Jon,

90% sure it's 3.1 in ModusToolbox.

--Matt

0 Likes
jomoc_3144201
New Contributor II

Then I am 99.99999% sure there in lies the issue.

If there is an option in ModusToolbox to down rev the PDL to say 3.0.4 then I would suspect it would work with the older BLE Pioneer kit.

Jon

mattl_01
Employee

Unfortunately, I don't think there is a way.  I believe when you update an SDK in ModusToolbox,

you get the whole $CYSDK/libraries/psoc6sw-[version] directory.  There is no separate PDL unit.

I could be wrong about that. There are folks working on this.  Maybe there will be a solution that

doesn't involve replacing the kit.

--Matt

0 Likes
jomoc_3144201
New Contributor II

There is a PDL folder under:

ModusToolbox_1.0\libraries\psoc6sw-1.0\components\psoc6pdl

Jon

0 Likes
MotooTanaka
Esteemed Contributor

Hi,

Last night (in Japan) in the following thread

CY8CKIT-062-BLE Setup Only requires PDL 3.0.1

msur-san uploaded attached startup file.

When I backed up and replaced startup_psoc6_01_cm0plus.S at

C:\Users\<MyUserName>\ModusToolbox_1.0\libraries\psoc6sw-1.0\components\psoc6pdl\devices\psoc6\startup\gcc

I could finally build and debug BlinkyLED with my CY8CKIT-062-BLE (Rev 11) via ModusToolbox!

Thanks msur-san!

moto

000-Blinky-Debug.JPG

0 Likes
jomoc_3144201
New Contributor II

Moto,

Yep, and no need to have the board replaced.   I'm still recovering my environment and plan to confirm this as well as soon as I have Modus up and running again.  The adjusted startup script does work with PSoC Creator 4.2 and PDL 3.1.0 and though.

Cheers,

Jon

MotooTanaka
Esteemed Contributor

Dear Jon-san,

> The adjusted startup script does work with PSoC Creator 4.2 and PDL 3.1.0 and though.

Thanks!

So we are now OK with cm0p side of startup.

I wonder if similar issue(s) may arise with the cm4 side,

we will find it along the way we explore more about ModusToolbox.

And meantime, I wonder if the startup with Cy_SaveIRQ and Cy_RestoreIRQ bothers the newer boards (Rev 13~).

Best Regards,

27-Dec-2018

Motoo Tanaka

0 Likes
MotooTanaka
Esteemed Contributor

I have just run diff on

PDL3.0.4 startup_psoc63_cm4.S

and

PDL3.1.0 startup_psoc6_01_cm4.S

and there surely was the same difference

=====================

269,289d276

<     /* Saves and disables the interrupts */

<     .global Cy_SaveIRQ

<     .func   Cy_SaveIRQ, Cy_SaveIRQ

<     .type   Cy_SaveIRQ, %function

< Cy_SaveIRQ:

<     mrs r0, PRIMASK

<     cpsid i

<     bx lr

<     .size   Cy_SaveIRQ, . - Cy_SaveIRQ

<     .endfunc

<

<     /* Restores the interrupts */

<     .global Cy_RestoreIRQ

<     .func   Cy_RestoreIRQ, Cy_RestoreIRQ

<     .type   Cy_RestoreIRQ, %function

< Cy_RestoreIRQ:

<     msr PRIMASK, r0

<     bx lr

<     .size   Cy_RestoreIRQ, . - Cy_RestoreIRQ

<     .endfunc

=====================

So we may be able to hack the startup for cm4, too

or may be we'd better wait for Cypress's "official" fixed version.

moto

0 Likes
MotooTanaka
Esteemed Contributor

I have just confirmed that with the startup file,

I also could program and debug BlinkyLED on my colleague's

CY8CKIT-063-BLE (Rev 😎

moto

0 Likes
MeenakshiR_71
Employee

Moto/Jon,

It is not required to update the M4's startup file. The functions are used by boot code, which executes in M0+. So no need to update/change M4 startup files.

Regards,

Meenakshi Sundaram R

jomoc_3144201
New Contributor II

Meenakshi and Moto-san,

I can confirm that I was able to load and run the BlinkyLED ModusToolbox Example with my rev. 8 PSoC 6 BLE Pioneer Kit using the changes to the M0+ startup file. 

Since there appears to be multiple versions of the PSoC 6 BLE Pioneer Kit, perhaps it would be best to put some sort of check in the startup file to accommodate the differences between boards; that is if it is possible.

Is there a ModusToolbox and/or PDL GitHub repository that this will be pushed to once it is signed off?  

MeenakshiR_71
Employee

Jon,

It will be a ModusToolbox SDK release, if we decide to add those functions. It should be noted that the "Cy_SaveIRQ" and "Cy_RestoreIRQ" APIs are replaced with Enter/ExitCriticalSection APIs in the newer version (which makes sense). Somehow the *A flash boot seem to use fixed Address for the Save/RestoreIRQ calls. Anyway our SW team is out on holiday and will get back with proper answer when they get back on the defect ticket I raised.

Regards,

Meenakshi Sundaram R

0 Likes
MeenakshiR_71
Employee

And yeah to add to my previous response - the modified startup should work for newer version kits as well (I have tested ). In fact, the startup does not impact any functionality for the newer version. It possibly may have unused code (Cy_SaveIRQ and Cy_RestoreIRQ) if not optimized out by compiler.