Trying to get a RP 2040 going.

[chipfryer27]

Hi

Although using v10 I followed the v9 guide just to see what happened and I expected a bit of rooting around to find the documented files. I did and it worked fine for me.

Yesterday on a different machine I attempted to install using the latest versions just to see what happened. I admit my attention wasn't totally focussed during such as I'm still clearing my feet of another matter.

Not good. Initially it looked like a CMake issue so I replaced that with old. Next it looked like an gcc issue so that was replaced by old. Still no luck so VS was replaced with no joy. I'm guessing that I'll probably need to do a registry clean before anything else. Good job I created a restore point before any of this

I was loosely following the guide, but grabbing the latest versions and I'm not saying they don't work as my attention during the instal was a bit lacking at times. I might get around to another play later in the week, but I'm in no hurry as it works on my other machine and I've no immediate need to use the chip, but it's handy to have.

Regards

[chipfryer27]

Hi

This afternoon I went back in time courtesy of System Restore, then ran Registry cleaner etc. Restarted, ran cleaner again and then followed the v10 install guide above exactly as documented (I had Python already installed).

All good and I could send a test program to the Pico, flashing the on-board LED every second.

Regards

Edit...
Updated my other machine to latest GIT. These have a few additional pop-up windows to that in the guide, but accepting the default for those extra pop up's updated and allowed me to continue compiling to the Pico.

[Chadb]

Hi guys,

Ok I followed the guide again. I already had git and python installed for playing with LLM's and that is working fine.

I have installed:

arm gcc 10-2020-q4-major -- add path to environment checked

CMake 3.20.5 -- add path checked

Build tools VS 2022 ,c++ , optionals checked

I already have python installed and working.

I already have git installed and working.

I deleted my c:/pico-sdk and re-cloned it. -- sucess

I setup FC to my c:/pico-sdk location under pico.

*******************
For shits and giggles, I tried it in the free version of FC 10, and it built and programmed. I still get errors in my FC 9...
Great...

I really don't feel like dumping hundreds of dollars to get fc 10 up to my fc9 level.

Sigh..

Here is what fc 9 gives me.

Chad
//////////////////////////////////////////

Code: Select all

Target folder: E:\New project folder\Cable 2
Source name:   E:\New project folder\Cable 2\rp pico test1.fcfx
Title:         Pico test1
Description:   
Device:        PICO.PICO.Raspberry_Pi_RP2040
Generated by:  Flowcode v9.3.1.36
Date:          Tuesday, July 18, 2023 05:38:59
Users:         1
Registered to: chadb 
Licence key: 
https://www.flowcode.co.uk
Using FCD settings for compiler
Launching the compiler...
C:\ProgramData\MatrixTSL\FlowcodeV9\FCD\PICO\Batch\pico_build.bat  "C:\pico-sdk\" "rp pico test1" "E:\New project folder\Cable 2\"  

E:\New project folder\Cable 2>REM CRC: 11E85D0BF540A03612B9D5AB8A950728A3654FDC084B783F85B503651504FC6E8DA967745A187CF8FECF9115B25085A2774D1D3D69D8A99EE7320EAE740A5DB6B7BD508EEBDD47B75FAC7989837F066407A873416006272C711B8143522C2B691E456854D22958005824CF181DE22D23B9DE25CDF0E36405D9066202E94705CBBDB038842E43FA4AAC72934211FD4B5DCC661788BEC7C91A063848616D51551DB978AC1A4BAF29AD4517DCDD22FC70DE135D32748FB3D1732C3050DA273BE4EEE43F007DD05FDB033C02C2501DA160983770621C568611AD61112B2378F6127E5D3A7ED706D09BBA 

E:\New project folder\Cable 2>REM REVISION: 3.0 

E:\New project folder\Cable 2>REM GUID: 9EF5601F-D979-495F-89EB-F1C4F35D9212 

E:\New project folder\Cable 2>REM DATE: 17\07\2023 

E:\New project folder\Cable 2>REM DIR: FCD\PICO\batch\pico_build.bat 
. . .

Building rp pico test1 ...
**********************************************************************
** Visual Studio 2022 Developer Command Prompt v17.6.5
** Copyright (c) 2022 Microsoft Corporation
**********************************************************************
PICO_SDK_PATH is C:/pico-sdk
PICO platform is rp2040.
-- The C compiler identification is unknown
-- The CXX compiler identification is unknown
-- The ASM compiler identification is unknown
-- Found assembler: C:/Program Files (x86)/Arm GNU Toolchain arm-none-eabi/12.2 mpacbti-rel1/bin/arm-none-eabi-gcc.exe
CMake Error at C:/pico-sdk/CMakeLists.txt:10 (project):
  The CMAKE_C_COMPILER:
    C:/Program Files (x86)/Arm GNU Toolchain arm-none-eabi/12.2 mpacbti-rel1/bin/arm-none-eabi-gcc.exe
  is not a full path to an existing compiler tool.
  To use the NMake generator with Visual C++, cmake must be run from a shell
  that can use the compiler cl from the command line.  This environment is
  unable to invoke the cl compiler.  To fix this problem, run cmake from the
  Visual Studio Command Prompt (vcvarsall.bat).
  Tell CMake where to find the compiler by setting either the environment
  variable "CC" or the CMake cache entry CMAKE_C_COMPILER to the full path to
  the compiler, or to the compiler name if it is in the PATH.
CMake Error at C:/pico-sdk/CMakeLists.txt:10 (project):
  The CMAKE_CXX_COMPILER:
    C:/Program Files (x86)/Arm GNU Toolchain arm-none-eabi/12.2 mpacbti-rel1/bin/arm-none-eabi-g++.exe
  is not a full path to an existing compiler tool.
  To use the NMake generator with Visual C++, cmake must be run from a shell
  that can use the compiler cl from the command line.  This environment is
  unable to invoke the cl compiler.  To fix this problem, run cmake from the
  Visual Studio Command Prompt (vcvarsall.bat).
  Tell CMake where to find the compiler by setting either the environment
  variable "CXX" or the CMake cache entry CMAKE_CXX_COMPILER to the full path
  to the compiler, or to the compiler name if it is in the PATH.
CMake Error at C:/pico-sdk/CMakeLists.txt:10 (project):
  The CMAKE_ASM_COMPILER:
    C:/Program Files (x86)/Arm GNU Toolchain arm-none-eabi/12.2 mpacbti-rel1/bin/arm-none-eabi-gcc.exe
  is not a full path to an existing compiler tool.
  Tell CMake where to find the compiler by setting either the environment
  variable "ASM" or the CMake cache entry CMAKE_ASM_COMPILER to the full path
  to the compiler, or to the compiler name if it is in the PATH.
-- Warning: Did not find file Compiler/-ASM
-- Configuring incomplete, errors occurred!
See also "E:/New_project_folder/Cable_2/rp_pico_test1/CMakeFiles/CMakeOutput.log".
See also "E:/New_project_folder/Cable_2/rp_pico_test1/CMakeFiles/CMakeError.log".

Microsoft (R) Program Maintenance Utility Version 14.36.32537.0
Copyright (C) Microsoft Corporation.  All rights reserved.

NMAKE : fatal error U1064: MAKEFILE not found and no target specified
Stop.

Build Failed

C:\ProgramData\MatrixTSL\FlowcodeV9\FCD\PICO\Batch\pico_build.bat reported error code 0x1

Autoclose turned off


FINISHED

[Chadb]

Oh, and chip.. Thank you for trying all of that for us (me). It is appreciated.

Chad

[medelec35]

Hi Chad.
As it works with FC10 I don't see why it won't work with FC9.
The updated batch file was pushed onto the update system yesterday.
You will need to change the component update options from Files in-use to Full
After updating, you will need to reload any project for the update to be active.
What I would do first is start a new simple project (eg, 1sec flasher) with a new title, since if you use the same title it could cause issues unless the folder that was created had been deleted first.
The folder automatically created by the Pico toolchain will have the same name as the project folder, but spaces will be replaced by underscores.
The project name generated will also have underscores instead of spaces.

[Chadb]

You'd think...

I went in and deleted the file that you sent me as it was giving me a “not genuine” error, oddly enough, even after resetting the components and re downloading them. I did that and did a full component dl and restarted. I will try a new blink file. That is all my last one was.

*So I made a new file that is exactly the same blink and it programmed. Hallelujah !1!.

Thank you. And everyone else.

Chad

[medelec35]

Hi what updates are posted on the forums, they will give a not genuine as they have been modified for forum members to try.
By deleting it, it would have prevented your pico from working again.
At least now you are up and running, that's great news.
It sounds like the new folder that pico created, just need to be deleted.
You don't need to do that normally, just when different installer files are used or batch files get modified etc.
By renaming that is the same as deleting as the installation starts from fresh,

[Chadb]

Thanks again, Now I can try to get my little project working.

Chad

[chipfryer27]

Hi

Glad you have it working. I've been having a litlle play with the Pico and so far I quite like it.

Regards

[medelec35]

You're welcome.
I'm glad you have it working.