• Support
  • VSC : sample external_rtc - PCF85063A not found

jft7 something like this?

warning: attempt to assign the value 'y' to the undefined symbol PCF85063A
  • jft7 replied to this.

    jaredwolff
    Yes, this is the error :
    C:/Users/jfthi/ZephyrProjects/app/samples/external_rtc/prj.conf:15: warning: attempt to assign the value ‘y’ to the undefined symbol PCF85063A

    I’ve been running into this using the VSCode extension more. It has to do with how Zephyr caches directory information. If you’re using the repo in the same location on your machine the main application folder probably got renamed from nfed to app. I did this a while back and have the same error as you right now.

    I haven’t stumbled on the exact surgical fix so I’ll get back to you.

    Ahh. Found it.

    In your west.yml in the self: option change path: nfed to path: app. I’ll be pushing a fix shortly and also addressing this in the VSCode plugin

    Thanks for your help
    I modified west.yml but I still have the problem.
    The Nordic extension was also installed previously, maybe this could be a problem ?
    It seems that the “Zephyr Tools: build” uses the path of the NCS toolchain as initially installed which is “Users/xxx/ncs/v1.7.1”, but the Zephyr extension repo is “Users/xxx/ZephyrProjects”
    I have west.yml files in both locations, and I tried to change both files without success.

    As I can build the application without the “Zephyr tools” , I am not stuck at the moment, but I’ll investigate further and maybe try a fresh install ?

    For information, this is the build log:

    – Application: C:/Users/jfthi/ZephyrProjects/app/samples/external_rtc
    – Using NCS Toolchain 1.7.1 for building. (C:/Users/jfthi/ncs/v1.7.1/toolchain/cmake)
    – Zephyr version: 2.6.99 (C:/Users/jfthi/ZephyrProjects/zephyr), build: v2.6.99-ncs1
    – Found west (found suitable version “0.11.1”, minimum required is “0.7.1”)
    – Board: circuitdojo_feather_nrf9160_ns
    – Cache files will be written to: C:/Users/jfthi/ZephyrProjects/zephyr/.cache
    – Found dtc: C:/Users/jfthi/ncs/v1.7.1/toolchain/opt/bin/dtc.exe (found suitable version “1.4.7”, minimum required is “1.4.6”)
    – Found toolchain: gnuarmemb (C:/Users/jfthi/ncs/v1.7.1/toolchain/opt)
    – Found BOARD.dts: C:/Users/jfthi/ZephyrProjects/zephyr/boards/arm/circuitdojo_feather_nrf9160/circuitdojo_feather_nrf9160_ns.dts
    – Generated zephyr.dts: C:/Users/jfthi/ZephyrProjects/app/samples/external_rtc/build/zephyr/zephyr.dts
    – Generated devicetree_unfixed.h: C:/Users/jfthi/ZephyrProjects/app/samples/external_rtc/build/zephyr/include/generated/devicetree_unfixed.h
    – Generated device_extern.h: C:/Users/jfthi/ZephyrProjects/app/samples/external_rtc/build/zephyr/include/generated/device_extern.h
    – Including generated dts.cmake file: C:/Users/jfthi/ZephyrProjects/app/samples/external_rtc/build/zephyr/dts.cmake

    C:/Users/jfthi/ZephyrProjects/app/samples/external_rtc/prj.conf:15: warning: attempt to assign the value ‘y’ to the undefined symbol PCF85063A
    Parsing C:/Users/jfthi/ZephyrProjects/zephyr/Kconfig
    Loaded configuration ‘C:/Users/jfthi/ZephyrProjects/zephyr/boards/arm/circuitdojo_feather_nrf9160/circuitdojo_feather_nrf9160_ns_defconfig’
    Merged configuration ‘C:/Users/jfthi/ZephyrProjects/app/samples/external_rtc/prj.conf’

    error: Aborting due to Kconfig warnings

      jft7 it’s best to re-init the project especially if it’s been relocated. I’ve also fixed the issue with the application folder name in the latest version of the extension. So you no longer have to edit the west.yml file.

      To re-init remove your .west folder and then run Zephyr Tools: Init Repo

      I run the following steps as described in documentation (https://docs.jaredwolff.com/nrf9160-sdk-setup-windows.html)
      1- create an empty directory “c:\ZephyrRepo”
      2- run “Zephyr Tools: setup”
      3- run “Zephyr Tools: Init Repo” with the empty directory created at step #1 and the URL “https://github.com/circuitdojo/nrf9160-feather-examples-and-drivers.git

      But there is a PermissionError during “Init Repo” (see bellow). I tried different location, same result.

      === Initializing in C:\ZephyrRepo
      — Cloning manifest repository from https://github.com/circuitdojo/nrf9160-feather-examples-and-drivers.git
      Cloning into ‘C:\ZephyrRepo.west\manifest-tmp’…
      remote: Enumerating objects: 889, done.
      remote: Counting objects: 100% (889/889), done.
      remote: Compressing objects: 100% (512/512), done.
      remote: Total 889 (delta 465), reused 746 (delta 326), pack-reused 0
      Receiving objects: 100% (889/889), 5.95 MiB | 1.81 MiB/s, done.
      Resolving deltas: 100% (465/465), done.
      Traceback (most recent call last):
      File “C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.9_3.9.2544.0_x64__qbz5n2kfra8p0\lib\shutil.py”, line 815, in move
      os.rename(src, real_dst)
      PermissionError: [WinError 5] Accès refusé: ‘C:\ZephyrRepo\.west\manifest-tmp’ -> ‘C:\ZephyrRepo\nfed’

      The error is complaining that you already have a .west file in C:\ZephyrRepo. Files with a . prefix are typically hidden. You may need to enable viewing of hidden files/folders to delete it first. Then retry the init process.

      I’ll retry it here with the latest to make sure I didn’t break anything.

      Hmm fix one thing and break another! Let me see what’s up with this. Getting the same error.

      You may need to enable viewing of hidden files/folders to delete it first. Then retry the init process.

      I always enable viewing of hidden files, and the directory was freshly created …
      To be sure, I’ve just tried again, with the same error.
      I am sorry to importune you with that, but I don’t find where is my mistake …

        It doesn’t look like something you’re doing. It appears to be a permissions issue. For some reason when I run the same command manually (west init) it works but when I do it through the extension, it fails. Looking into it. I’m sorry about this!

        Looks like you’ll need to roll back to 0.1.15 for now.

        I’m still trying to figure out a solution. For some reason cmd.exe is executing west with different privileges which causes it to bork. You will need to edit your west.yml once everything is initialize to pull in the RTC drivers.

        @jft7 do you have something like chocolatey or Cygwin installed? You may have to remove it from your path. I was able to get things working once I did on my end.

        C:\Zephyr>"C:\Users\Jared Wolff\.zephyrtools\env\Scripts\west.exe" init -m https://github.com/circuitdojo/nrf9160-feather-examples-and-drivers.git
        === Initializing in C:\Zephyr
        --- Cloning manifest repository from https://github.com/circuitdojo/nrf9160-feather-examples-and-drivers.git
        Cloning into 'C:\Zephyr\.west\manifest-tmp'...
        remote: Enumerating objects: 899, done.
        remote: Counting objects: 100% (899/899), done.
        remote: Compressing objects: 100% (521/521), done.
        remote: Total 899 (delta 472), reused 750 (delta 327), pack-reused 0
        Receiving objects: 100% (899/899), 6.71 MiB | 12.46 MiB/s, done.
        Resolving deltas: 100% (472/472), done.
        --- setting manifest.path to nfed
        === Initialized. Now run "west update" inside C:\Zephyr.

        Still working on this to confirm what it exactly is though. Stay tuned..

        Ok, with the latest version of the extension adding a .vscode/settings.json and disabling the built in Git client will fix the problem. That took a LOT longer than expected.

        {
            "git.enabled": false,
            "git.path": null,
            "git.autofetch": false
        }

        I’ll release a new version of the extension that will do this.

        I just pushed version 0.1.17 which addresses this. I hope you’re able to get going. Let me know if you need anything else jft7

        Thanks a lot !
        Everything seems to be OK : I’ve reinstalled and successfully compiled and run a few samples.
        I apologize for the delay to answer due to the time difference (we are UTC+1)

        Terms and Conditions | Privacy Policy