# Error following BSP upgrade

**URL:** <https://forums.digi.com/t/error-following-bsp-upgrade/4268>\
**Category:** NET+OS\
**Tags:** bsp-update\
**Created:** [October 21, 2010, 2:45pm UTC](https://forums.digi.com/t/error-following-bsp-upgrade/4268 "2010-10-21T14:45:41Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![eos\_pengwern](https://avatars.discourse-cdn.com/v4/letter/e/ac91a4/32.png) [@eos\_pengwern](https://forums.digi.com/u/eos_pengwern)\
**Post date:** [October 21, 2010, 2:45pm UTC](https://forums.digi.com/t/error-following-bsp-upgrade/4268/1 "2010-10-21T14:45:41Z")

</div>

I’ve just downloaded the latest BSP upgrades and, following the hints given by the operating system, have tried to create a new application Workspace into which I will subsequently re-import my custom routines.

However, the newly-created application won’t compile. During compilation, I get the error messages:

…/…/Makefile.tools:35: …/…/src/bsp/platforms/connectme9210\_esp/Makefile.bsp: Permission denied  
…/…/Makefile.tools:57: \*\*\* You have entered an invalid platform, the valid platforms are: ns9750\_a, ns9360\_a, ns7520\_a, ns9210\_a, connectme9210, connectwiem9210, connectcore9p9215\_a connectcorewi9p9215\_a connectme, connectem, connectsp, connectwisp, connectwime, connectwiem, connectcore9c\_a, connectcorewi9c\_a, connectcore7u\_a, connectcore9p9360\_a. Stop.

This is from a pristine automatically-generated application which so far has had no input from me at all, other than pressing the “Build” button. So what can be happening here?

Thanks,  
Stephen.

---

<div class="post-metadata">

**Author:** ![eos\_pengwern](https://avatars.discourse-cdn.com/v4/letter/e/ac91a4/32.png) [@eos\_pengwern](https://forums.digi.com/u/eos_pengwern)\
**Post date:** [October 25, 2010, 9:00am UTC](https://forums.digi.com/t/error-following-bsp-upgrade/4268/2 "2010-10-25T09:00:02Z")

</div>

Update: the problem seems to go away if I run Digi ESP as an Administrator (for example by ticking the appropriate box in the shortcut’s “Properties/Advanced” menu). This didn’t seem to be necessary before, but at least I’ve got it working now.
