Camera control does not work as it should on target ZEEZF7V2

[robustini]

Describe the bug

Hi, i've this issue only with ZEEF7V2 target, same fpv cam and other F7 boards and I have no problem.
PB15 is the default pin used in Betaflight, I enter the cam menus correctly, but the "drop value" command does not work, and others are reversed from how it should work.
With other targets, even custom, everything works perfectly, so there is something anomalous with this fc with this Foxeer Predator.
I use the camera control with many other F7 fc and I have no problem, with the default settings.
So please test it and post these values in the correct arrangement, because by default not all work and some are reversed.

To Reproduce

Just try with the default settings, even changing them the problem remains.

Expected behavior

Even changing them the problem remains.

Flight controller configuration

board_name ZEEZF7V2
manufacturer_id ZEEZ

# name: Edo

# resources
resource PINIO 1 B11

# feature
feature GPS
feature TELEMETRY

# beeper
beeper -ON_USB

# beacon
beacon RX_LOST
beacon RX_SET

# serial
serial 0 1024 115200 57600 0 115200
serial 1 2048 115200 57600 0 115200
serial 4 2 115200 57600 0 115200

# aux
aux 0 0 0 1800 2100 0 0
aux 1 1 3 1300 2100 0 0
aux 2 46 5 1750 2100 0 0
aux 3 13 2 1300 2100 0 0
aux 4 15 6 900 1600 0 0
aux 5 35 4 1300 2100 0 0
aux 6 36 1 1300 2100 0 0

# vtxtable
vtxtable bands 6
vtxtable channels 8
vtxtable band 1 BOSCAM_A A FACTORY 5865 5845 5825 5805 5785 5765 5745 5725
vtxtable band 2 BOSCAM_B B FACTORY 5733 5752 5771 5790 5809 5828 5847 5866
vtxtable band 3 BOSCAM_E E FACTORY 5705 5685 5665    0 5885 5905    0    0
vtxtable band 4 FATSHARK F FACTORY 5740 5760 5780 5800 5820 5840 5860 5880
vtxtable band 5 RACEBAND R FACTORY 5658 5695 5732 5769 5806 5843 5880 5917
vtxtable band 6 IMD6     I CUSTOM  5732 5765 5828 5840 5866 5740    0    0
vtxtable powerlevels 4
vtxtable powervalues 25 100 400 1000
vtxtable powerlabels 25 100 400 1W

# rxfail
rxfail 9 s 2000

# master
set acc_calibration = 75,-13,-12,1
set align_mag = CUSTOM
set mag_align_roll = 250
set mag_align_pitch = 1800
set mag_align_yaw = 900
set mag_calibration = -117,-34,-128
set motor_pwm_protocol = DSHOT600
set failsafe_procedure = GPS-RESCUE
set gps_provider = UBLOX
set gps_sbas_mode = AUTO
set gps_auto_baud = ON
set gps_ublox_use_galileo = ON
set gps_rescue_angle = 35
set gps_rescue_initial_alt = 25
set gps_rescue_descent_dist = 30
set gps_rescue_ground_speed = 800
set gps_rescue_throttle_max = 1300
set gps_rescue_throttle_hover = 1200
set gps_rescue_sanity_checks = RESCUE_SANITY_FS_ONLY
set gps_rescue_allow_arming_without_fix = ON
set gps_rescue_alt_mode = FIXED_ALT
set osd_link_quality_pos = 14370
set osd_flymode_pos = 14785
set osd_gps_speed_pos = 14792
set osd_gps_lon_pos = 14799
set osd_gps_lat_pos = 14768
set osd_gps_sats_pos = 14376
set osd_home_dir_pos = 14380
set osd_home_dist_pos = 14386
set osd_avg_cell_voltage_pos = 14392
set osd_disarmed_pos = 14635
set vtx_band = 2
set vtx_channel = 8
set vtx_power = 3
set vtx_low_power_disarm = ON
set vtx_freq = 5866
set pinio_box = 40,255,255,255
set name = Edo

profile 0

rateprofile 0

#resource show all

A00: SERIAL_TX 4
A01: SERIAL_RX 4
A02: SERIAL_TX 2
A03: FREE
A04: GYRO_CS 1
A05: SPI_SCK 1
A06: SPI_MISO 1
A07: SPI_MOSI 1
A08: I2C_SCL 3
A09: FREE
A10: FREE
A11: USB
A12: USB
A13: SWD
A14: SWD
A15: OSD_CS
B00: LED_STRIP
B01: FREE
B02: BEEPER
B03: MOTOR 4
B04: MOTOR 3
B05: SPI_MOSI 3
B06: MOTOR 2
B07: MOTOR 1
B08: I2C_SCL 1
B09: I2C_SDA 1
B10: FREE
B11: PINIO 1
B12: FLASH_CS
B13: SPI_SCK 2
B14: FREE
B15: CAMERA_CONTROL
C00: ADC_BATT
C01: ADC_CURR
C02: SPI_MISO 2
C03: SPI_MOSI 2
C04: GYRO_EXTI
C05: FREE
C06: FREE
C07: FREE
C08: FREE
C09: I2C_SDA 3
C10: SPI_SCK 3
C11: SPI_MISO 3
C12: SERIAL_TX 5
C13: FREE
C14: LED 1
C15: LED 2
D00: FREE
D01: FREE
D02: SERIAL_RX 5
D03: FREE
D04: FREE
D05: FREE
D06: FREE
D07: FREE
D08: FREE
D09: FREE
D10: FREE
D11: FREE
D12: FREE
D13: FREE
D14: FREE
D15: FREE
E00: FREE
E01: FREE
E02: FREE
E03: FREE
E04: FREE
E05: FREE
E06: FREE
E07: FREE
E08: FREE
E09: FREE
E10: FREE
E11: FREE
E12: FREE
E13: FREE
E14: FREE
E15: FREE
F00: FREE
F01: FREE
F02: FREE
F03: FREE
F04: FREE
F05: FREE
F06: FREE
F07: FREE
F08: FREE
F09: FREE
F10: FREE
F11: FREE
F12: FREE
F13: FREE
F14: FREE
F15: FREE

Currently active Timers:
-----------------------
TIM1:
    CH2: LED_STRIP
TIM2:
    CH2: MOTOR 4
TIM3:
    CH1: MOTOR 3
TIM4:
    CH1: MOTOR 2
    CH2: MOTOR 1
TIM5: FREE
TIM6: FREE
TIM7: FREE
TIM8: FREE
TIM9: FREE
TIM10: FREE
TIM11: FREE
TIM12:
    CH2: CAMERA_CONTROL
TIM13: FREE
TIM14: FREE

Currently active DMA:
--------------------
DMA1 Stream 0: MOTOR 2
DMA1 Stream 1: FREE
DMA1 Stream 2: FREE
DMA1 Stream 3: MOTOR 1
DMA1 Stream 4: MOTOR 3
DMA1 Stream 5: FREE
DMA1 Stream 6: MOTOR 4
DMA1 Stream 7: FREE
DMA2 Stream 0: ADC
DMA2 Stream 1: FREE
DMA2 Stream 2: FREE
DMA2 Stream 3: FREE
DMA2 Stream 4: FREE
DMA2 Stream 5: FREE
DMA2 Stream 6: LED_STRIP
DMA2 Stream 7: FREE

Setup / Versions

• Flight controller: ZEEZF7V2

• Other components: rx Crossfire, VTX 600 mW, ESCs 40A

• How are the different components wired up: standard wiring, the camera OSD is connected to the PB15 of the FC via a 220 ohm resistor.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs within a week.

[robustini]

Bump...

[haslinghuis]

Please remove resource output and provide the diff and resource show all as requested while opening the issue and edit in the opening message. I've now edited to show how to use the backticks
Do you have the 20x20 or 30x30 board?

After that maybe @Guidus93 could have a look at it.

[robustini]

Please remove resource output and provide the diff and resource show all as requested while opening the issue and edit in the opening message. I've now edited to show how to use the backticks
Do you have the 20x20 or 30x30 board?

After that maybe @Guidus93 could have a look at it.

I had already chatted with Guido and he told me that with RunCam he didn't encounter this problem.
Yet this unfortunately happens here with a Foxeer Predator.

[robustini]

@haslinghuis I edit the first post with the requested information, sorry for the layout but it is not easy to understand how your layout designer thinks.

[haslinghuis]

@robustini It's default github markup, we didn't anything about layout. Updated your post. Perhaps Foxeer doesn't need a resister (or another value to be used) like the Runcam camera does but this is just speculation.

[robustini]

@robustini It's default github markup, we didn't anything about layout. Updated your post. Perhaps Foxeer doesn't need a resister (or another value to be used) like the Runcam camera does but this is just speculation.

Tested both with and without resistor, the result does not change.
Installed another F7, so with the same target (STM32F7X2) and zero problems, same parameters.

[haslinghuis]

Should camera control not have a dma pin assignment in the config file @Guidus93?

dma pin B15 0

[robustini]

One thing I have not tried, remap the resource of the leds and use that, only as a comparison.
I would not like the pin dedicated to the camera control of this board to have circuit problems.
But the problem is not that it doesn't work, it works but the selection with the sticks is wrong, as I wrote above, as if the five resistance values that can be changed are not correct for this board.
We tried to change them and we managed to get four controls to work, but the fifth one remains not working.
From the joystick supplied with the cam we measured the five resistance values by pressing a button at a time, and they are the usual ones that we know well, in fact with its joystick the camera control is fine, it is the board that sends out incorrect resistance values.

[haslinghuis]

[Should be] fixed in betaflight/unified-targets#946