Please help me!

Hello everybody!

I have a problem by using Hmote2430 and Keil compiler for my sensor network project. When I use Keil compiler to compile my NesC code, I have some error as follow:

vu_anh_dung@anhdung /opt/tinyos-2.x/apps/Battery3
$ ./AUTOMAKE.sh

C:\cygwin\opt\tinyos-2.x\apps\Battery3\build\hmote2430>echo off

A51 MACRO ASSEMBLER V8.01 - SN: K1MMC-0LE18C
COPYRIGHT KEIL ELEKTRONIK GmbH 1987 - 2007

ASSEMBLY COMPLETE. 0 WARNING(S), 0 ERROR(S)

C:\cygwin\opt\tinyos-2.x\apps\Battery3\build\hmote2430>echo off

C51 COMPILER V8.12 - SN: K1MMC-0LE18C
COPYRIGHT KEIL ELEKTRONIK GmbH 1987 - 2008
*** WARNING C219 IN LINE 1527 OF APP.C: long constant truncated
*** ERROR C136 IN LINE 1596 OF APP.C: invalid dimension size: [0]

C51 COMPILATION COMPLETE. 1 WARNING(S), 1 ERROR(S)

LX51 LINKER/LOCATER V4.25 - SN: K1MMC-0LE18C
COPYRIGHT KEIL ELEKTRONIK GmbH 1995 - 2007
startup.obj, app.obj TO app CLASSES( XDATA(X:0xE000-X:0xFF00), IDATA(I:0-I:0xFF)) REGFILE(app.reg)ma
*** ERROR L210: I/O ERROR ON INPUT FILE: EXCEPTION 0021H: PATH OR FILE NOT FOUND FILE: APP.OBJ

Extended 8051/251 Object to Hex File Converter V1.36b
COPYRIGHT KEIL ELEKTRONIK GmbH 2000 - 2006

*** ERROR: CAN'T OPEN FILE 'app'
**********************************************************
***** app.hex is created.. upload IMAGE to CC2430 !! *****
**** You can use SmartRF04 Flash Programmer (chipcon) ****
**********************************************************
ls: app.hex: No such file or directory

- To implement on Hmote2430 device, I used app.hex file to implement on it. but Keil compiler can not generate hex file by this error.
- If I copy the APP file generate from another program, Keil compiler can generate hex file but the result same to that another program.
- I need some help, please!

Parents
  • Was "Please help me!" a descriptive summary?

    Have you taken a closer look at:

    *** WARNING C219 IN LINE 1527 OF APP.C: long constant truncated
    *** ERROR C136 IN LINE 1596 OF APP.C: invalid dimension size: [0]
    

    We can't do it for you. We do not know the contents of line 1527 and line 1596 of your APP.C file.

    Always take care of problems in the order they arrive, instead of trying to cheat the last step by copying an other hex file or similar.

    When the C code is correct and compileable, then there will be an APP.OBJ file, and then the linker will have the required files to try to create a HEX file.

    Another thing: The AUTOMAKE.sh file seems a bit stupid, since it prints "app.hex is created" when no such file is actually created.

Reply
  • Was "Please help me!" a descriptive summary?

    Have you taken a closer look at:

    *** WARNING C219 IN LINE 1527 OF APP.C: long constant truncated
    *** ERROR C136 IN LINE 1596 OF APP.C: invalid dimension size: [0]
    

    We can't do it for you. We do not know the contents of line 1527 and line 1596 of your APP.C file.

    Always take care of problems in the order they arrive, instead of trying to cheat the last step by copying an other hex file or similar.

    When the C code is correct and compileable, then there will be an APP.OBJ file, and then the linker will have the required files to try to create a HEX file.

    Another thing: The AUTOMAKE.sh file seems a bit stupid, since it prints "app.hex is created" when no such file is actually created.

Children
More questions in this forum