Go Down

Topic: Elegoo Tumbller: basic questions (Read 1 time) previous topic - next topic

suokia

Hi all,

I just assembled the tumbller and everything works great.
Now I wanted to try program it and possibly expand it in the future.
Since I'm going to learn this platform with my kid, who's the actual owner and assmbler of the robot, I want to go through mblock.
Here is the board specs: https://win.adrirobot.it/robot_tumbller/robot_tumbller_elegoo.html#Scheda_controllo_Nano_V4

Now the first questions.
  • The bot came with preflashed instructions allowing the bot to be controlled both via button and Bluetooth.  If I start playing with mblock to run commands on the bot, will I loose the preflashed instructions or I can run commands without flashing?
  • If I want to expand it for voice control it and add a camera, what do I need and what do I have to check?




suokia

I just got a tumbller with a preloaded firmware offering various functions.
It can be controller with a physical button which has 4 operating modes and can be also controlled with elegoo remote app which has a preprogrammed remote pad and a customizable one where you can set your own commands to move the bot or let leds switch on/off.

Now I wanted to dig it.
AFAIK if I want to try my code I'll loose the preloaded functions.
But today I found the bluetooth arduino controller:  if it's connecting successfully and starts working, will I lose the preloaded firmware when launching my commands?
And what about mblock ide: it can also connect via BT

suokia

I connected to the bot with  ./G4DUDE configured like this:
- config.ini : put the correct port detected by arduino IDE
- programmer type : arduino
- chip type : ATMega328p

Quote
/usr/bin/avrdude -pm328p -carduino -P/dev/ttyACM0 -t

avrdude: AVR device initialized and ready to accept instructions

Reading | ################################################## | 100% 0.00s

avrdude: Device signature = 0x1e950f (probably m328p)
avrdude> part
>>> part

AVR Part                      : ATmega328P
Chip Erase delay              : 9000 us
PAGEL                         : PD7
BS2                           : PC2
RESET disposition             : dedicated
RETRY pulse                   : SCK
serial program mode           : yes
parallel program mode         : yes
Timeout                       : 200
StabDelay                     : 100
CmdexeDelay                   : 25
SyncLoops                     : 32
ByteDelay                     : 0
PollIndex                     : 3
PollValue                     : 0x53
Memory Detail                 :

                        Block Poll               Page                       Polled
 Memory Type Mode Delay Size  Indx Paged  Size   Size #Pages MinW  MaxW   ReadBack
 ----------- ---- ----- ----- ---- ------ ------ ---- ------ ----- ----- ---------
 eeprom        65    20     4    0 no       1024    4      0  3600  3600 0xff 0xff
 flash         65     6   128    0 yes     32768  128    256  4500  4500 0xff 0xff
 lfuse          0     0     0    0 no          1    0      0  4500  4500 0x00 0x00
 hfuse          0     0     0    0 no          1    0      0  4500  4500 0x00 0x00
 efuse          0     0     0    0 no          1    0      0  4500  4500 0x00 0x00
 lock           0     0     0    0 no          1    0      0  4500  4500 0x00 0x00
 calibration    0     0     0    0 no          1    0      0     0     0 0x00 0x00
 signature      0     0     0    0 no          3    0      0     0     0 0x00 0x00

avrdude> sig
>>> sig

Reading | ################################################## | 100% 0.00s

Device signature = 0x1e950f

avrdude> d lfuse
>>> d lfuse
0000  00                                                |.               |

avrdude> d hfuse
>>> d hfuse
0000  00                                                |.               |

avrdude> d efuse
>>> d efuse
0000  00                                                |.               |

avrdude> quit
>>> quit

avrdude done.  Thank you.
I can then read the chip and backup the code

Go Up