Skip to content

Conversation

@akarus3
Copy link

@akarus3 akarus3 commented Jun 14, 2025

tested with X4 quad , s1,s2,s3,s4, uart1, uart2, uart3, uart4, opflow+rangefinder works good
Up: acc, gyro, baro, analog osd works too

@sensei-hacker
Copy link
Member

Hi Akarus. Thanks for submitting this.
Are you a representative of the manufacturer?

@akarus3
Copy link
Author

akarus3 commented Jun 15, 2025

Hi Akarus. Thanks for submitting this. Are you a representative of the manufacturer?

Hi, I am a home diy. Bf can't provide opflow and rangefinder, and I build inav for my sologood f405 v1.1 with bf dump_all cli output. Now I have indor surface althold for 3.5" cinewhoop. Opflow+rangefinder is msp UpixelT1.

@sensei-hacker
Copy link
Member

sensei-hacker commented Jun 15, 2025

Thanks for that. I'll pull that in to my unofficial targets repository for now.
You may also want to email the manufacturer requesting that they take a look at this.

To maintain high quality for official targets, we put them through the following tests to ensure everything works correctly:

  • Flash firmware
  • Calibrate
  • Orientation matches
  • Gyro working
  • Accel working
  • Baro working
  • Voltage correct
  • Current correct
  • Analog RSSI
  • Mag I2C Bus
  • UART1
  • UART2
  • UART3
  • UART4
  • UART5
  • UART6
  • LEDs working
  • Buzzer working
  • Motor outputs
  • DShot support on m1-4
  • Blackbox
  • Analog Camera working
  • Video Out working
  • OSD working
  • PINIO1
  • PINIO2

The process is described in our New Hardware Policy:
https://github.com/iNavFlight/inav/blob/master/docs/policies/NEW_HARDWARE_POLICY.md

If the manufacturer sends a test board and we confirm everything works correctly, we can make it an official target.

@akarus3
Copy link
Author

akarus3 commented Jun 15, 2025

If the manufacturer sends a test board and we confirm everything works correctly, we can make it an official target.

Since we don't have a board

Am write a feedback to manufacturer, maybe it can help

@sensei-hacker sensei-hacker added the New target This PR adds a new target label Jun 18, 2025
@chimera15
Copy link

How do I download and flash it, it's not a hex file, so I have to compile it?

@akarus3
Copy link
Author

akarus3 commented Nov 17, 2025 via email

@chimera15
Copy link

chimera15 commented Nov 17, 2025

I need to use it for an altus vtol, you think it will work? Weighing doing this and swapping out one of my speedybee's from one of my quads. Do you think motor pads 5-8 will have timers assigned to them? need to use them for servos.

@akarus3
Copy link
Author

akarus3 commented Nov 17, 2025 via email

@chimera15
Copy link

ok thanks a lot, I put in a request to sologood to try to get it approved by them as well, hopefully will help get this board in the targets and fully functional eventually, looks like I'm in for a swap session then.

@akarus3
Copy link
Author

akarus3 commented Nov 17, 2025 via email

@chimera15
Copy link

chimera15 commented Nov 17, 2025

hmm it has a thing that says "all checks passed" and motor outputs were tested so does that mean if I build the target it will have timers assigned though? But you're saying just the 4 are tested I guess huh?

@akarus3
Copy link
Author

akarus3 commented Nov 17, 2025 via email

@chimera15
Copy link

chimera15 commented Nov 17, 2025

if I build it does it help test it I guess and get it approved even without sologood? I guess I can give it a try if it will help. I'm currently waiting for motors for my build so have a week or two before they get here to play around with it I guess.

@akarus3
Copy link
Author

akarus3 commented Nov 17, 2025 via email

@chimera15
Copy link

chimera15 commented Nov 17, 2025

@akarus3
Copy link
Author

akarus3 commented Nov 17, 2025 via email

@sensei-hacker
Copy link
Member

"all checks passed" means only that the code compiles.
GitHub doesn't have the hardware, so it can't tell if anything will actually work on the hardware.

In other words, one could copy any other target for a completely different board, rename it "sologood405” and GitHub wouldn't have any idea that it doesn't match the actual board.

Testing the actual board to see if the target is correct for THIS board is done when the manufacturer sends us a sample to test.

@chimera15
Copy link

chimera15 commented Nov 20, 2025

I compiled it on 8.0.1, apparently my version, which is board revision v1.1 apparently a new revision of the board uses a new gyro, ICM‑42688P, tried a bunch of stuff, will not recognize the gyro. The barometer is working. Obviously that's an issue though. everything else I see looks like it's working but haven't powered it yet or tested motor outputs or osd. Apparently there's support for that gyro in 8.1, but lots of issues trying to compile 8.1 vs 8.0.1. What gyro do you have akarus? is yours v1.1?

had to use stm32cubeprogrammer to flash it cause both betaflight and inav think the hex is too large, but its actually not. really strange.

yeah this is confirming it uses that gyro, I guess that's why they're not sending it to you guys to get it approved.

https://sologood.net/products/sologood-f405-55a-stack-icm42688p-f405-flight-controller-blheli_s-50a-4in1-esc-30-5x30-5mm-2-6s-for-fpv-freestyle-drones-parts

SoloGood F405 55A Stack ICM42688P F405 Flight Controller BLHELI_S 55A 4in1 ESC 30.5X30.5mm 2-6S
that's showing to be on the v1.0 board though? so maybe I'm doing something wrong?

even 8.1 doesn't seem to have a separate .c or .h under accgyro for that gyro, and its somehow imbedded into the build for specific targets or something weird? Apparently it's supposed to be compatible with another gyro? But nothing I do stops my gyro from being red or activates the calibration. I've tried all the gyros in the list.

Hmm, I think from the betaflight hex they all use that gyro, so I must be doing something wrong in my 8.0.1 build.

Ah I found the betaflight config.h, so it does seem they had two gyros cause it calls out two of them.

#define USE_GYRO
#define USE_GYRO_SPI_MPU6000
#define USE_GYRO_SPI_ICM42688P
#define USE_MAX7456

That would follow why he was able to build it with no issues then and I'm having all sorts of trouble. This just got too hard to fix I think, I'm going to do the speedybee swap.

edit got it working, you just treat it as a 42650 in the target defines, that was the mistake.

osd is working, everything seems to be working. need to still test the motors, but servo outputs are working 5, 6, and 8. Only sort of weird thing is that one of the timers is split into 3, like s3 s4, and s7, which makes it hard to do what I want to do. The led doesn't seem to work for servos. Need to see if I can alter that in the code maybe?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

New target This PR adds a new target

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants