paparazzi-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Paparazzi-devel] Lisa/L test program


From: Felix Ruess
Subject: Re: [Paparazzi-devel] Lisa/L test program
Date: Fri, 4 May 2012 12:14:14 +0200

Hi Xavier,

I would guess you are using master, as these test progs are already fixed in dev.

To show your branches (and the corresponding upstream branch):
git branch -vv
(the one marked with the star is the currently used branch)

Cheers, Felix

On Mon, Apr 23, 2012 at 9:10 AM, Xavier RIVIERE <address@hidden> wrote:
Hi,

Well, I don't know what "github branch" I'm using... I get the last version using "git pull" before to post :)

Here is the error for test_telemetry

/home/aero/paparazzi/var/
LezGaui/test_telemetry/test/test_telemetry.o: In function `main_periodic':
/home/aero/paparazzi/sw/airborne/test/test_telemetry.c:53: undefined reference to `uart_check_free_space'
/home/aero/paparazzi/sw/airborne/test/test_telemetry.c:53: undefined reference to `uart2'
/home/aero/paparazzi/var/LezGaui/test_telemetry/arch/stm32/mcu_periph/uart_arch.o: In function `uart2_init':
/home/aero/paparazzi/sw/airborne/arch/stm32/mcu_periph/uart_arch.c:151: undefined reference to `uart_periph_init'
/home/aero/paparazzi/sw/airborne/arch/stm32/mcu_periph/uart_arch.c:175: undefined reference to `uart2'
/home/aero/paparazzi/var/LezGaui/test_telemetry/arch/stm32/mcu_periph/uart_arch.o: In function `usart_irq_handler':
/home/aero/paparazzi/sw/airborne/arch/stm32/mcu_periph/uart_arch.c:98: undefined reference to `uart2'
collect2: ld returned 1 exit status




Here is the error for test_actuators_mkk

CC /home/aero/paparazzi/var/
LezGaui/test_actuators_mkk/mcu_periph/i2c.o
CC /home/aero/paparazzi/var/LezGaui/test_actuators_mkk/arch/stm32/mcu_periph/i2c_arch.o
arch/stm32/mcu_periph/i2c_arch.c: In function 'i2c1_ev_irq_handler':
arch/stm32/mcu_periph/i2c_arch.c:507:3: warning: implicit declaration of function 'i2c_event' [-Wimplicit-function-declaration]
arch/stm32/mcu_periph/i2c_arch.c:507:3: warning: nested extern declaration of 'i2c_event' [-Wnested-externs]
arch/stm32/mcu_periph/i2c_arch.c: In function 'i2c1_er_irq_handler':
arch/stm32/mcu_periph/i2c_arch.c:513:3: warning: implicit declaration of function 'i2c_error' [-Wimplicit-function-declaration]
arch/stm32/mcu_periph/i2c_arch.c:513:3: warning: nested extern declaration of 'i2c_error' [-Wnested-externs]
arch/stm32/mcu_periph/i2c_arch.c: At top level:
arch/stm32/mcu_periph/i2c_arch.c:11:20: warning: 'i2c_hard_reset' used but never defined [enabled by default]
arch/stm32/mcu_periph/i2c_arch.c:12:20: warning: 'i2c_reset_init' used but never defined [enabled by default]
LD /home/aero/paparazzi/var/LezGaui/test_actuators_mkk/test_actuators_mkk.elf
/home/aero/paparazzi/var/LezGaui/test_actuators_mkk/arch/stm32/mcu_periph/i2c_arch.o: In function `i2c1_hw_init':
/home/aero/paparazzi/sw/airborne/arch/stm32/mcu_periph/i2c_arch.c:499: undefined reference to `i2c_reset_init'
/home/aero/paparazzi/var/LezGaui/test_actuators_mkk/arch/stm32/mcu_periph/i2c_arch.o: In function `i2c1_ev_irq_handler':
/home/aero/paparazzi/sw/airborne/arch/stm32/mcu_periph/i2c_arch.c:507: undefined reference to `i2c_event'
/home/aero/paparazzi/var/LezGaui/test_actuators_mkk/arch/stm32/mcu_periph/i2c_arch.o: In function `i2c1_er_irq_handler':
/home/aero/paparazzi/sw/airborne/arch/stm32/mcu_periph/i2c_arch.c:513: undefined reference to `i2c_error'
collect2: ld returned 1 exit status



Here is my airframe firmware declaration

<firmware name="rotorcraft">
    <target name="ap" board="lisa_l_1.1"/>
    <define name="USE_ADAPT_HOVER" />
    <define name="GUIDANCE_H_USE_REF" />
    <subsystem name="radio_control" type="ppm"/>
    <subsystem name="actuators"     type="mkk"/>
    <subsystem name="telemetry"     type="transparent"/>
    <subsystem name="imu"           type="aspirin_v1.5"/>
    <subsystem name="gps"           type="ublox"/>
    <subsystem name="ahrs"          type="int_cmpl_euler">
        <define name="AHRS_MAG_UPDATE_YAW_
ONLY"/>
    </subsystem>
    <subsystem name="ins"           type="hff"/>
    <subsystem name="stabilization" type="euler"/>

    <configure name="CPU_LED"         value="3"/>
    <configure name="RADIO_CONTROL_LED"     value="5"/>
    <configure name="GPS_LED"         value="7"/>
</firmware>

  <firmware name="lisa_l_test_progs">
    <target name="tunnel"           board="lisa_l_1.1"/>
    <target name="test_led"         board="lisa_l_1.1"/>
    <target name="test_uart"        board="lisa_l_1.1"/>
    <target name="test_servos"      board="lisa_l_1.1"/>
    <target name="test_telemetry"   board="lisa_l_1.1"/>
    <target name="test_baro"        board="lisa_l_1.1"/>
    <target name="test_imu_b2"      board="lisa_l_1.1"/>
    <target name="test_imu_b2_2"    board="lisa_l_1.1"/>
    <target name="test_imu_aspirin" board="lisa_l_1.1"/>
    <target name="test_rc_spektrum" board="lisa_l_1.1"/>
    <target name="test_rc_ppm"      board="lisa_l_1.1"/>
    <target name="test_adc"         board="lisa_l_1.1"/>
    <target name="test_hmc5843"     board="lisa_l_1.1"/>
    <target name="test_itg3200"     board="lisa_l_1.1"/>
    <target name="test_adxl345"             board="lisa_l_1.1"/>
    <target name="test_esc_mkk_simple"      board="lisa_l_1.1"/>
    <target name="test_esc_asctecv1_simple" board="lisa_l_1.1"/>
    <target name="test_actuators_mkk"       board="lisa_l_1.1"/>
    <target name="test_actuators_asctecv1"  board="lisa_l_1.1"/>
  </firmware>




Le 19/04/2012 18:44, Stephen Dwyer a écrit :
Hello,

Knowing what compilation errors you are getting, as well as airframe
file configuration and what code (i.e. github branch and last commit)
you are using would be particularly helpful in identifying the problem
:).

Thanks,
-Stephen Dwyer

On Thu, Apr 19, 2012 at 10:41 AM, Xavier RIVIERE
<address@hidden> wrote:
Hi,


I'm working on a homemade soldering Lisa/L, and I'm testing each fonction.
FTDI and USB part is working well, and I can program the STM32. So I did.

I run lisa/l some test programs for lisa :
- test_LED
- test_UART
- test_baro

But for "test_telemetry" and "test_actuators_mkk", I have compilation
errors...


My problem is that when I try to compile the complete software, I don't have
any communication between the ARM and the Xbee. GCS remain blank, and when I
check with an oscilloscope, there is no signal passing on the line.

Any idea ??

To be complete, I have to say that I don't have any IMU connect yet. Maybe
the problem come from that ?

Thanks

Xavier

_______________________________________________
Paparazzi-devel mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/paparazzi-devel

_______________________________________________
Paparazzi-devel mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/paparazzi-devel


_______________________________________________
Paparazzi-devel mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/paparazzi-devel



reply via email to

[Prev in Thread] Current Thread [Next in Thread]