[Bitcloud] HAL make doesn't compile "WdtInitatmega256rfr2_Gcc.o"

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

Hi Team!

 

I have been rearranging my project files in order to be able to reference all the bitcloud components within the application itself. However, after some rearranging, I have found that for some reason when I compilied my application, the "WdtInitatmega256rfr2_Gcc.o" file went missing. Go to my bitcloud/lib and the file no longer exists. In the past I simply copied the file from the original library, but it has been starting to bother me that I can't simply 'compile it'.

 

My HAL make log:

C:\BitCloud_MEGARF_3_2_0_modified\BitCloud\Components\HAL>make all clean
make all -C ./../HAL/avr
make[1]: Entering directory `C:/BitCloud_MEGARF_3_2_0_modified/BitCloud/Componen
ts/HAL/avr'

----------------------------------------------------
HAL library creation.
----------------------------------------------------
avr-gcc ../avr/atmega128rfa1/common/src/halWdtInit.c
avr-gcc ../avr/atmega128rfa1/common/src/halPwm.c
avr-gcc ../avr/atmega128rfa1/common/src/halSleepTimerClock.c
avr-gcc ../avr/atmega128rfa1/common/src/halSecurityModule.c
avr-gcc ../avr/atmega128rfa1/common/src/halDelay.c
avr-gcc ../avr/atmega128rfa1/common/src/halAppClock.c
avr-gcc ../avr/atmega128rfa1/common/src/halClkCtrl.c
avr-gcc ../avr/atmega128rfa1/common/src/halUsart.c
avr-gcc ../avr/atmega128rfa1/common/src/halIrq.c
avr-gcc ../avr/atmega128rfa1/common/src/halTwi.c
avr-gcc ../avr/atmega128rfa1/common/src/halEeprom.c
avr-gcc ../avr/atmega128rfa1/common/src/wdt.c
avr-gcc ../avr/atmega128rfa1/common/src/halSleep.c
avr-gcc ../avr/atmega128rfa1/common/src/halAdc.c
avr-gcc ../avr/atmega128rfa1/common/src/halSpi.c
avr-gcc ../avr/atmega128rfa1/common/src/calibration.c
avr-gcc ../avr/atmega128rfa1/common/src/halInit.c
avr-gcc ../avr/atmega128rfa1/common/src/halFlash.c
avr-gcc ../avr/atmega128rfa1/common/src/halRfCtrl.c
avr-gcc ../avr/atmega128rfa1/common/src/halMacIsr.c
avr-as ../avr/atmega128rfa1/common/src/halW1.s
avr-as ../avr/atmega128rfa1/common/src/halCalibration.s
avr-as ../avr/atmega128rfa1/common/src/halSpDriver.s
avr-gcc ../avr/atmega128rfa1/../common/src/pwm.c
avr-gcc ../avr/atmega128rfa1/../common/src/sleepTimer.c
avr-gcc ../avr/atmega128rfa1/../common/src/appTimer.c
avr-gcc ../avr/atmega128rfa1/../common/src/halTaskManager.c
avr-gcc ../avr/atmega128rfa1/../common/src/usart.c
avr-gcc ../avr/atmega128rfa1/../common/src/w1.c
avr-gcc ../avr/atmega128rfa1/../common/src/irq.c
avr-gcc ../avr/atmega128rfa1/../common/src/resetReason.c
avr-gcc ../avr/atmega128rfa1/../common/src/i2cPacket.c
avr-gcc ../avr/atmega128rfa1/../common/src/eeprom.c
avr-gcc ../avr/atmega128rfa1/../common/src/timer.c
avr-gcc ../avr/atmega128rfa1/../common/src/adc.c
avr-gcc ../avr/atmega128rfa1/../common/src/spi.c
avr-gcc ../avr/atmega128rfa1/../common/src/sleep.c
avr-gcc ../avr/atmega128rfa1/../common/src/flash.c
avr-ar ../../../lib/libHAL_MegaRf_Atmega256rfr2_8Mhz_Gcc.a
-td ../../../lib/WdtInitatmega256rfr2_Gcc.o
-td ../../../lib/libHAL_MegaRf_Atmega256rfr2_8Mhz_Gcc.a
make[1]: Leaving directory `C:/BitCloud_MEGARF_3_2_0_modified/BitCloud/Component
s/HAL/avr'
make clean -C ./../HAL/avr
make[1]: Entering directory `C:/BitCloud_MEGARF_3_2_0_modified/BitCloud/Componen
ts/HAL/avr'

----------------------------------------------------
HAL component cleaning.
HAL cleaning done!
----------------------------------------------------
make[1]: Leaving directory `C:/BitCloud_MEGARF_3_2_0_modified/BitCloud/Component
s/HAL/avr'

C:\BitCloud_MEGARF_3_2_0_modified\BitCloud\Components\HAL>pause
Press any key to continue . . .

I am unsure what the -td line does that is supposed to create the WdtInitatmega256rfr2_Gcc.o file. Is it that I am doing something wrong for this file not to be created or...?

Last Edited: Thu. Oct 15, 2015 - 09:54 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 1

"-td" is a leftover from a call to "avr-size" utility, which is not found (not defined) for some reason. This alone can not be the reason for a missing library, but might be an indication of where to start looking.

 

There is nothing else wrong with the log.

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