AFAIK all the 2.4.8’s have 2Mb of flash. Those boards came out after all the hoopla about the 1Mb version. But you should post the messages screen to see if it’s fmuv2 or fmuv3 loaded because by default these all seem to load the former. BTW-fmuv3 will run on these boards and it will make some features available that are not in fmuv2.
There is one way you can tell from Mission planner when you attempt to load firmware.See the “found board type” note? It indicates flash here for the board and now will not a load a version that doesn’t fit. This is a 1Mb board.
I upgraded the AR620 with the latest firmware but I’m trying to find the actual board version information. I cannot access it from the “Install Firmware” page in the Mission Planner as shown by Dave.
I’m including the look of my mission planner screen
What do the messages show when you boot the board? Messages tab under the HUD. Select it before connecting and post a screen shot before the needed info scrolls away. You should update Mission Planner to Latest Beta from the Help screen.
It’s the port labelled “data” on the AR620. You need to connect it to a free UART using the TX pin/+/gnd
And set SERIALn_OPTIONS=4 SERIALn_PROTOCOL=23 when n is the serial number.
I’ve updated the firmware with the one you supplied. I wired the AR620 as you indicated using the +, gnd and signal for the 1/data port and the other end on the Serial UART#4 on the board.
Shown in the picture as #9.
Here is the wiring I followed:
I used pin 1 for VCC, Pin2 for the data on the AR620 and pin 6 for GND
I changed the parameters with the following configuration:
Do you think it makes a difference which serial port I used since normally #4 is used for GPS? Should I used the Serial port #5 instead?
The device is power up but when connecting to the mission plan, I get no movement on the bar during the radio calibration.
These bugs were reported in the SRXL2 thread on rcgroups, I suspect the SRXL comment is a typo. So I have no reason to believe it does not support SRXL2. Someone else is reporting issues similar to you with an RX that definitely supports SRXL2, so it may be something else.