# segger embedded studio build error

Hi NordicSemiconductor Community,

I have a problem with the SEGGER Embedded Studio IDE, i want to build my project but i have the following error :

can't open 'C:/Users/Yacire/Desktop/NORDIC_SEMICONDUCTOR/nRF51_SDK_10.0.0_dc26b5e/examples/ble_peripheral/Self_Wake_UP_2.0_SEGGER_Embedded_Studio/pca10028/s110/arm5_no_packs/Output/experimental_ble_app_blinky_s110_pca10028 nrf51422_xxac_s110/Obj/hardware_initialization.asm' for writing: No such file or directory


I don't understand, i can build the project without issue in Keil uVision. I follow the Blog tutorial from Hang Bui.

Any help would be appreciated. Thanks.

edit retag close delete

Hi RK,

Thanks for your answer, but i have others files builded without issue. I changed the path but i have the same error...

( 2017-08-12 13:18:10 +0200 )editconvert to answer

@Yacire93: The blog post states that you need to use SDK v12.0.1 or newer, you are using SDK v10.0.0.

( 2017-08-14 11:18:12 +0200 )editconvert to answer

Yes, i use the SDK 10.0.0 but i have tested with another example from the SDK 10.0.0 and it worked. I have tested with the app_ble_beacon from the SDK 10.0.0. So i don't understand why with my file hardware_initialization.c it doesn't work ...

( 2017-08-14 12:11:41 +0200 )editconvert to answer

Could it be that you have not added the hardware_initialization.c file to the SES project or that the path is incorrect? Alos check if running SES as administrator fixes the issue.

( 2017-08-14 12:57:03 +0200 )editconvert to answer

Ok it was the name of my file, strangely i change the name of the file to hdw_init.c and now it works without issue.Maybe it was because the file name was too long ...

( 2017-08-14 17:39:57 +0200 )editconvert to answer
1

that's what I told you in my original answer. The entire path with the original filename was 260 characters long which is bigger than 256 which is where windows goes wrong. Had you just shortened some elements of the path as per the original suggestion so that all filenames with paths were shorter, it should have worked just fine.

( 2017-08-14 22:06:39 +0200 )editconvert to answer

Yes, you were right RK, thanks for the additional information about the number of character of the path name allowed by Windows.

( 2017-08-15 17:08:32 +0200 )editconvert to answer

Sort by » oldest newest most voted

I'd suggest a shorter path, there have been many reports of windows having issues with long paths before.

more

I would suggest to try "Long Path Tool" program.

more

[hide preview]

## Recent blog posts

• ### GPIO pin errors

Posted 2017-10-20 02:37:56 by micallef25
• ### How to build continuous integration and delivery process for embedded SW development

Posted 2017-10-03 11:01:29 by Yaniv Nis
• ### Multiple channels in RTT

Posted 2017-09-29 11:51:52 by Krzysztof Zaraska
• ### 6 Things to Know about Bluetooth Beacons

Posted 2017-09-22 08:27:00 by Rose Martin
• ### Creating a Keil project for a Bluetooth Mesh example (Updated for 0.10.0)

Posted 2017-09-19 12:08:11 by Kristian Skordal

## Recent questions

• ### DLE in S112

Posted 2017-10-20 07:02:25 by Stayhungry
• ### How can I create repeater with nrf52

Posted 2017-10-20 06:20:34 by MainOFF

Posted 2017-10-20 05:07:03 by MNIL
• ### Transfer large data 2 board nrf52840

Posted 2017-10-20 04:54:54 by MainOFF
• ### Nordic Glucose crashed after entering wrong passkey

Posted 2017-10-20 04:44:34 by Daniel