I own one of these GF30F405-ICM and i was looking through the firmware for a possible match, i do see JHEM_JHEF405 and JHEMCU-GSF405A, however i’m not sure if the first one refers to this specific F405 model, and the second one is not a match but could have the same characteristics, how would i verify this?
Review the Hwdef
Hwdef
I don’t think either of those firmwares suit.
Although the Betaflight target that board uses,JHEF405pro, is referenced in the hwdef for the JHEMCU GSF405A board.
I’ve looked over the hwdefs a little, and while i’m not very experienced, i can’t find any obvious differences. The GSF is an AIO, i’m really not sure it would be closer to the GF30 than the GF16. I’m comparing the definitions from Inav with the AP def JHEMF405, which is for the GF16, and my only uncertainty was the gyro (Inav seems to use an older name, however it’s verified working fine), both seem to use the ICM42688-P. I have flashed that one onto a naked board with just a Mavlink-ELRS receiver and noticed the gyro orientation was off, i had to set AHRS_ORIENTATION to 6 (yaw270).
So far, i mean, everything looks alright? I’m not an AP expert so if there’s something terribly wrong i’m missing, please enlighten me.
I did a port and it’s working fine for a first run, but I have strange situation if I create a new directory in hwdef - it doesn’t work. If I use existing directory JHEM_JHEF405, set all proper definitions and even set a new APJ_BOARD_ID it works fine.
I created a thread about that New board JHEMCU GF30F405 - strange behavior
@xznhj8129 rotation IMO should be ROTATION_PITCH_180_YAW_270 27
IMU on the board is upside down a board itself is rotated 90.
That’s very possible, i didn’t look further than the horizon going the right way when bench-testing. I tried flashing to another but had problems like you mentionned, i couldn’t seem to find what file i used last time, i think i used beta at first, which worked as above, but 4.6 failed, it wouldn’t boot as you mentionned. Requires someone with more experience looking into it. But it would be nice for an inexpensive, minimally acceptable quality AP FC.