south hinge
Hello,
I have a problem with the recognition of MEGA cards.
The board is new, Elegoo Mega2560R3 (but same with china mega 2560).
It is well recognized by windows and works perfectly in the Arduino IDE.
When I run MF (beta 9.7.1.2) it asks me to load the firmware. This one is installed and then the card is not recognized by MF and I go around in circles having to reload the firmware.
thanks
Log
errant panther
Can you share a log for a run of MobiFlight after you have flashed a board but where it fails to detect?
I see in the log you provided the flash did succeed. I'd like to see a second log where you ran and it says the board needs to be flashed again
south hinge
Here is the second log after restart MF always asking to flash the board
south hinge
New manipulation, reset of the card using MF then flashing, the card is recognized but if I upload a config, there is an error.
When MF restarts, it asks for flashing again
errant panther
I'm really not sure what's going on. This looks similar to the Nano issue in the other thread. it's flashing fine but then not responding as a mobiflight board on future runs
do you know how to use the Arduino IDE serial monitor?
south hinge
Yes I know
errant panther
Ok cool
Shut down mobiflight
Run the Arduino IDE and connect to your mega with the serial monitor (make sure to use the correct baud rate for your board)
Type 9; in the serial monitor and hit enter
See if you get anything back from the board
make sure you have the baud rate set to 115200
also post a photo of your mega so I can clearly see all the chips on the board
south hinge
errant panther
Fascinating.
one moment
So that should report back the board info. Since it isn't it's like the firmware isn't actually on that board 😦
This is happening with both your megas?
south hinge
Yes, on 3 differents one, two china and the elegoo
errant panther
Hopefully someone else can chime in, I'm out of ideas 😦 It's clearly completing the flash based on your logs, but if you aren't getting anything back when you connect directly to it with the arduino IDE then the firmware doesn't seem to actually be there
If it was just one board I'd say it's defective, but three? I'm really confused
south hinge
Thank you for your help anyway, I'm going in circles!
I bought the elegoo card thinking that the Chinese cards were in question.
At the first start(this Friday), the card worked perfectly. Today it is no longer recognized!
I have a Chinese card which is recognized and works normally.
The difference with a china board that works in the log :
Debug 08/26/2023 18:07:21 MobiFlightCache.RegisterModule(): Registering module Default:COM5.
Info 08/26/2023 18:07:22 MobiFlightModule.Connect(): MobiflightModule.connect: Connected to Default at COM5 of type MobiFlight Mega (DTR=>True).
Debug 08/26/2023 18:07:23 MobiFlightModule.GetInfo(): Retrieved board: MobiFlight Mega, MobiFlight Test, 2.4.1, SN-594-89b.
errant panther
yes, see how it's able to get the board info? that last line
that's the response to a 9; command
south hinge
yes this card work, so I dont touch it !
errant panther
random idea that seems unlikely to fix anything, but... have you tried rebooting the PC?
can you post a photo of the top of the chinese card that's working too, so I can see the chips on it?
south hinge
yes, rebooting, reinstall W11, change USB cable, differents USB port
errant panther
reinstalling w11 is way overkill 😬
share a photo of the top of the chinese board that's working fine
south hinge
south hinge
reinstalling w11 is way overkill 😬
It's fast !
errant panther
Well that's the difference between your boards. It's a little hard to see with your hand and wires, but that board looks like it uses the CH340 chip for USB. The other one you posted is using an amtel chip for USB
Can you get a better photo of this part of the board that's working?
south hinge
errant panther
yup, that's the difference between the boards. I'm not sure why the other ones aren't working, but the USB chip is definitely different between them
and that board has a genuine CH340 on it so it won't have the issues we've seen with the counterfeit ones
all the other three megas have a square chip there instead of a rectangular one?
south hinge
I find something ! The elegoo seems to work when nothing is connected
so maybe my wiring can cause a problem with the firmware or how the board start ?
I will try to reconnect step by step to find if it comes from there
south hinge
no, I never use D0/D1
south hinge
many thanks for your help !
junior bear
I thought the same there is probably something connected to those pins D0 and D1.
sick mica
Hi,
I am using 4 exemplars of these R3 Elegoo 2560 cards, like yours. For a few weeks, i had an errratic behaviour from only one after connecting a new panel. Finaly, i've understood that i had an electric defect in my setup and then pressing a tempo button, it caused a reset for the card. Only when i pressed this button, so as i was focused on other ones, i did'nt use it at the beginning, had a lot of functions that reacted well. But slater I encountered had a lot of erratic hard and soft behaviour (it is only my second pannel, and the firts with inputs). So i recommand to isolate your card from your panels before you test the basic functionnalities.
south hinge
This morning when restarting the PC, again the same message.
I realize that a card without connection does not pose a problem but as soon as I plug the devices on it, it crashes.
I have two I2C LCDs on the arduino and I put a switch cutting off the + terminal of these screens when I'm not using them.
If I don't feed these screens, the bug occurs, if I feed them, no bug.
junior bear
May I ask where did you get the idea to put a switch on the power supply to your i2c adapter?
a quick search reveals that if you power off the i2c adapter, the adapter initialization is lost. At best, you end up with a non-functioning screen. Apparently, the arduino also doesn't like the i2c not responding and crashes.
Alternatively, you can turn off the leds in the screen to have the screen look like it is off.
there is a jumper in the i2c adapter marked "led". It provides power to the screen leds from the i2c adapter. You can take off the jumper and replace the connection with a PWM signal coming from your arduino pin and you can now control the brightness of the screen.
Beware though, I have had i2c adapters where the jumper did not cut the power to the leds because the adapter fed the leds directly through a separate trace in parallel to the jumper.
