Compiling ZAppSI error

Go To Last Post
7 posts / 0 new
Author
Message
#1
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Hello guys!
Im trying to run the "Runner" application that comes with Bitcloud Profile Suite 1.10. This application shows the usage of the ZigBee Serial Interface library (ZAppSI)running on a PC and on a embedded system (RF231USBRD wireless board). Im working with Smart Energy Profile

My problem is that I can not compile the project to PC using "make" command like is said in BitCloud Profile Suite Quick Start Guide.
Im using GNU make.

After configuring properly "configuration.h" and running make clean sucssefully, trying to run "make all" the windows command prompt shows me this:

C:\BITCLOUD\BitCloud_PS_SAM3S_EK_1_10_0\BitCloud_PS_SAM3S_EK_1_10_0\Applications\ZAppSi\Demo\SEDevice>make all
make -C makefiles/PC -f Makefile_PC_Gcc all APP_NAME=DemoSE
make[1]: Entering directory 'C:/BITCLOUD/BitCloud_PS_SAM3S_EK_1_10_0/BitCloud_PS_SAM3S_EK_1_10_0/Applications/ZAppSi/Demo/SEDevice/makefiles/PC'
A sintaxe do comando está incorrecta.
make[1]: *** [directories] Error 1
make[1]: Leaving directory 'C:/BITCLOUD/BitCloud_PS_SAM3S_EK_1_10_0/BitCloud_PS_SAM3S_EK_1_10_0/Applications/ZAppSi/Demo/SEDevice/makefiles/PC'
make: *** [all] Error 2

the below line means "The syntax of the command is incorrect"

A sintaxe do comando está incorrecta.

Anyone who had compiled it successfully?

PS: Im ataching the 2 makefiles used in this example in a .zip file.

Attachment(s): 

Last Edited: Fri. Oct 16, 2015 - 02:16 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

What versions of all the tools involved in this you are using?

NOTE: I no longer actively read this forum. Please ask your question on www.eevblog.com/forum if you want my answer.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Im using BitCloud Profile Suite for SAM3S4 version 1.10, GNU make 3.81, and I have a PC with Windows 7 32 bits and a Intel x86 processor. To programm my board (RF231USBRD) I use Atmel Studio 6.

I also tried MinGW make (mingw32-make) and the result is the same.
The first makefile has 2 targets: "all" and "clean". "clean" works fine with both make.

I made a mistake in my first post: the command that I used is "make all" instead of only "make".

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Check that tools like "mkdir" and your compiler are in the PATH variable. I've just compiled it and it worked fine, so it is something on your system.

On the other hand, are you sure that ZAppSi is the best choice for you? What is your goal?

NOTE: I no longer actively read this forum. Please ask your question on www.eevblog.com/forum if you want my answer.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I have both the bin folder from AVRGCC and the compiler. It keeps giving me the error in the "directories" target. I also think the problem is with mkdir but I will check it out.

Im working in the Smart Grid area and Im trying to interface my SE coordinator to a remote server through PC. ZAppSI seems to be a good option and seems to be also "fast" for programming, but if you have a better option please tell me.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

duduspot wrote:
I have both the bin folder from AVRGCC and the compiler. It keeps giving me the error in the "directories" target. I also think the problem is with mkdir but I will check it out.
Try replacing mkdir with gmkdir.

duduspot wrote:
Im working in the Smart Grid area and Im trying to interface my SE coordinator to a remote server through PC. ZAppSI seems to be a good option and seems to be also "fast" for programming, but if you have a better option please tell me.
If both sides are BitCloud, then you are probably fine, but then do you really need SE? If you want to interoperate with other vendors, then it is better to use plain embedded application and write your own serial API only for the functions you need. SE stuff is not mature enough, so it is likely that you'll have to make modifications to the embedded side anyway.

NOTE: I no longer actively read this forum. Please ask your question on www.eevblog.com/forum if you want my answer.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

It's working!! I just had to change some details on the PATH to where I really have "mkdir".

Thanks a lot for your help.