• State Verified Answer
  • Replies 7 replies
  • Subscribers 74 subscribers
  • Views 4256 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 222785
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

PC-BLE-Driver (C/C++) Installation on Windows 10 : Building Problem of Connectivity HEX file with MSBuild & CMD.exe

kwonjoon

Hello, this is Kwonjoon Lee from Korea.
I would like to ask about building problem of connectivity HEX file of pc-ble-driver (C/C++).

Actually, installation of the pc-ble-driver (C/C++) on Windows have many issues !!! 
so that I cannot install smoothly according to the guide in the following Git Hub. Please help me.
(https://github.com/NordicSemiconductor/pc-ble-driver#Architecture) 

(Development Environments)

1) Windows 10 64 Bit with cmd.exe (administrator)
2) Visual Studio 2015
3) GCC-ARM-Embedded Version : 7.3.1

(Default installation version of the guide was 7.2.1, and it had cmake error during "Compiling Connectivity HEX Files on the Windows" 
in the above-mentioned Git Hub guide due to the version of the gcc-arm-embedded. So I changed it)

4) Python Version 3.7.2

(Detailed Problem)

During the 3. MSBuild stage, building is progressed and successful for a while, 
However, I got a error in the building of "compile_connectivity_1.0.0_usb_with_s132_3.1.0.vcproj" as following sentences.

CustomBuild:
Generating connectivity_1.0.0_usb_with_s132_3.1.0_cmd
Makefile:260: Cannot find source file: ../../../../../../components/serialization/connectivity/codecs/ble/serializers
/conn_ble_l2cap_sdu_pool_1.c
Assembling file: gcc_startup_nrf52840.S
Compiling file: nrf_log_backend_rtt.c
Compiling file: nrf_log_backend_serial.c

..........

Compiling file: ble_gatts_evt_conn.c
Compiling file: ble_gatts_struct_serialization.c
Compiling file: ble_l2cap_conn_1.c
../../../../../../components/serialization/connectivity/codecs/ble/serializers/ble_l2cap_conn_1.c:47:10: fatal error:
conn_ble_l2cap_sdu_pool_1.h: No such file or directory
#include "conn_ble_l2cap_sdu_pool_1.h" // #include "conn_ble_l2cap_sdu_pool.h"
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
make: *** [../../../../../../components/toolchain/gcc/Makefile.common:272: _build/nrf52840_xxaa/ble_l2cap_conn_1.c.o]
Error 1
C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.CppCommon.targets(171,5): error MSB6006: "cmd.exe"이(가)
종료되었습니다(코드: 2). [C:\pc-ble-driver-master\hex\build\compile_connectivity_1.0.0_usb_with_s132_3.1.0.vcxproj]

As shown in the above-mentioned error message, the Makefile could not find "conn_ble_l2cap_sdu_pool.c" & "conn_ble_l2cap_sdu_pool.h"
So, I opened the Makefile in the following path

(Makefile Path)

C:\Users\~~~~~\AppData\Local\Temp\pc-ble-driver\sdks\v15\nRF5_SDK_15.2.0_9412b96
\examples\connectivity\ble_connectivity\pca10056\ser_s132v3_usb_hci\armgcc

(Related Contents in the Makefile)

$(SDK_ROOT)/components/serialization/connectivity/codecs/ble/serializers/conn_ble_l2cap_sdu_pool_1.c \

And, I found "conn_ble_l2cap_sdu_pool.c" & "conn_ble_l2cap_sdu_pool.h" are located 
in the following path without any path error.

C:\Users\krbong\AppData\Local\Temp\pc-ble-driver\sdks\v15\nRF5_SDK_15.2.0_9412b96
\components\serialization\connectivity\codecs\ble\serializers

Also, I checked that above-mentioned path have full read & write authority, 
and I made above-mentioned folders as a exception folder for anti-virus program.

However, still build error is generated. I have no idea. 
If you need additional evidence & files, I can provide you.

If you give me any answer, it will be huge help for me.

Best regards,
Kwonjoon Lee

Parents
  • +1

    Hi,

    I'm not able to reproduce this error. I would recommend that you try removing all files/directories in the build directory and try running cmake/msbuild again. If this does not work, make sure you follow every step in the instructions carefully from the start.

    Another thing to mention is that you should swap out the Python version you have installed and use Python 2.7.x instead. This is required by nrfutil, and you need to make sure you install nrfutil through pip for Python 2.7 to be able to build the USB connectivity firmwares.

    Best regards,
    Jørgen

  • +1 in reply to Jørgen Holmefjord
    • Win 10 x64
    • Python 2.7.15 on win32
    • pip 19.0.2 from c:\Python27\lib\site-packages\pip (python 2.7)
    • nrfutil version 5.0.0
  • 0 in reply to Jørgen Holmefjord

     Dear Jorgen Holmefjord,

    1) The above-mentioned my issue is solved by following steps including your kind advice.
    So, I would like to share my procedure with you. 

    2) Even though I got a quite good build results (Warning 0, Error 0),
    I want to get check and confirm about some phenomenon during the building of connectivity hex files,
    and also, I want to know whether that kinds of phenomenon is normal or abnormal.
    This is my final question.

    Firstly, about 1),

    I changed "SDK_ROOT" path (originally, /../../../../../../) and
    "PROJ_DIR" path (originally, /../../../) in the makefile which is located in the following path.

    C:\Users\~~~\AppData\Local\Temp\pc-ble-driver\sdks\
    v15\nRF5_SDK_15.2.0_9412b96\examples\connectivity\
    ble_connectivity\pca10056\ser_s132v3_usb_hci\armgcc

    The above figure is about my makefile revision, and I faced another issue
    which is related to the creating process for the generation of DFU_PKG.zip.

    So, I applied Jorgen Holmefjord's kind methods, and
    I got good build results (Warning 0, Error 0)

    Secondly, about 2),

    However, in the building process of connectivity hex files,
    Some projects creating DFU_PKG.zip file generate     "WARNING"s like the following figure.
    So, I want to get check and confirm about the "WARNING", and also,
    I want to know whether it is normal or abnormal.

    I really appreciate Jorgen Holmefjord's kind guides.
    If you provide some comments about 2), It will be huge help for me.

    Best regards,
    Kwonjoon Lee

Reply
  • 0 in reply to Jørgen Holmefjord

     Dear Jorgen Holmefjord,

    1) The above-mentioned my issue is solved by following steps including your kind advice.
    So, I would like to share my procedure with you. 

    2) Even though I got a quite good build results (Warning 0, Error 0),
    I want to get check and confirm about some phenomenon during the building of connectivity hex files,
    and also, I want to know whether that kinds of phenomenon is normal or abnormal.
    This is my final question.

    Firstly, about 1),

    I changed "SDK_ROOT" path (originally, /../../../../../../) and
    "PROJ_DIR" path (originally, /../../../) in the makefile which is located in the following path.

    C:\Users\~~~\AppData\Local\Temp\pc-ble-driver\sdks\
    v15\nRF5_SDK_15.2.0_9412b96\examples\connectivity\
    ble_connectivity\pca10056\ser_s132v3_usb_hci\armgcc

    The above figure is about my makefile revision, and I faced another issue
    which is related to the creating process for the generation of DFU_PKG.zip.

    So, I applied Jorgen Holmefjord's kind methods, and
    I got good build results (Warning 0, Error 0)

    Secondly, about 2),

    However, in the building process of connectivity hex files,
    Some projects creating DFU_PKG.zip file generate     "WARNING"s like the following figure.
    So, I want to get check and confirm about the "WARNING", and also,
    I want to know whether it is normal or abnormal.

    I really appreciate Jorgen Holmefjord's kind guides.
    If you provide some comments about 2), It will be huge help for me.

    Best regards,
    Kwonjoon Lee

Children
No Data
Related
Terms of service