One thing I should have mentioned in the original post is that
I set my work space to
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.
cylogger.log.zip 2.3 K
Reading the release note, I noticed that the KitProg2 has to be updated to KitProg3,
so I ran fw-loader as below
Then I rebooted my PC and tried to create the project again and got similar error.
Attached is the log file of this trial.
cylogger.log.zip 2.0 K
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!
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...
3 of 3 people found this helpful
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.
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.
Finally, I'm ready to start exploring the new territory.
Scotty, beam me up!
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"
1 of 1 people found this helpful
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
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)!
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.
(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.
(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"
(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.
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)
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.)
(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
-> I needed to select "BlinkyLED_mainapp" in the Project Explorer then menu seemed similar, I miss the "set as active" menu.
Note: I build with Quick Panel "Build BlinkyLED Application"
The last message of program "shutdown command invoked" sounds
somewhat intimidating. Showing the image of display may mitigate it.
(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
And when I pushed the pause icon
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.
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
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.
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.
> 2. Can you give me the result of a fw-loader.exe command?
> 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
(3.2) Build selected and built
(3.3) BlinkyLED Program (KitProg3) selsected
(3.4) Program finished
Note: At this point not LED blinking and even with RST switch pushed no blinking
(3.5) I also tried "BlinkyLED Debug (KitProg3)
(3.6) Debugger started (?)
> 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
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-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 firstname.lastname@example.org please?
Sorry for these issues.