LeafLabs Garden

A place to share, learn, and grow...

1. 

   poslathian
   LeafLabs

   hmm, its possible the stm32loader script in the boot loader repo is out of date. Not sure whats happening there.

   I wonder why the Arduino-as-serial-passthrough was not working. At the end of the day, the rx/tx lines on an arduino are just hard wired to the onboard FTDI chip. Serial1 on Maple is 5V compatible so no problem there. Its possible that while the rx line on maple is 5v compatible, the ftdi chip on the Arduino running at 5V is not sensitive to Maple's 3.3V output on tx.

   Also, as mike pointed out, Vin is a pre-regulator input. Since there is a drop from the regulator, you need to give it something more than 3.3. The official range is 5V-12V, but in practice 4.2V should get you there.

   Sometimes, and this is a little dangerous, you might want to have multiple systems running on exactly the same power source. In this case you can provide 3.3V directly onto Maple's Vcc pins. This is handy when comm busses are very sensitive to differences in voltages. However, if you put too much voltage on Vcc directly you can fry the MCU. Its quite sensitive, and will usually smokes around 4.2.

   Posted 4 years ago #
2. 

   rosendo
   Member

   Something that I just noticed after flashing the file maple_mini_boot.bin is that those 4 blinks fast blinks followed by slow blinks are gone!

   I thought that maybe the problem could be in both stm32loader.py files, so I tried the method suggested by siy (using stm32flash on linux terminal) and even though I could flash properly (very nice by the way, siy! Python and pyserial are not needed at all), the blinks that I would have are not there.

   Was there any bootloader change from the Rev1 to Rev2, or something like this? Did other people experience this same problem, or is it just me?

   Posted 4 years ago #
3. 

   siy
   Member

   I've noticed this issue with Maple Mini like board and appropriate bootloader. I've used binary downloaded from the page dedicated to the bootloader. Perhaps this is the cause. When I'll have some spare time I'll try to prepare binary from sources and check if this will solve the issue. In fact missing blinks, beside some inconveniences, don't prevent uploading sketches, at least for my board.

   Posted 4 years ago #
4. 

   mikep
   Member

   If everything else works fine and you can flash properly, then it might be that the LED_PIN is wrong in the bootloader source for the board you are using. I had the same issue when I flashed the Maple bootloader on another board which was using a different LED_PIN. Not sure why the official Maple Mini bootloader would have the wrong LED_PIN for the Maple Mini, but I would check that first, just to make sure.

   Posted 4 years ago #
5. 

   Leonardo
   Member

   Hi guys.
   I'm having a big problem with my maple mini. I probably erased the bootloader from it. I'm trying to flash it back. I'm using the FTDI CI of my arduino duemilanove. When I run the "python.exe stm32loader.py -p COM3 -evw maple_mini_boot.bin" command it return this:

   Microsoft Windows [versão 6.1.7600]
   Copyright (c) 2009 Microsoft Corporation. Todos os direitos reservados.

   C:\Users\Leonardo>cd c:\python33

   c:\Python33>python.exe stm32loader.py -p COM3 -evw maple_mini_boot.bin
   Reading data from maple_mini_boot.bin
   Traceback (most recent call last):
   File "stm32loader.py", line 479, in <module>
   data = read(args[0])
   File "stm32loader.py", line 383, in read
   if bytes.startswith('\x7FELF'):
   TypeError: startswith first arg must be bytes or a tuple of bytes, not str

   Why he is saying that I'm trying to use a srt? What is that mean? I read in the datasheet of FTDI FT232RT that it have a buffer to the RX and Tx data. This buffer can be a problem? It can be the origem of my problem?

   Posted 3 years ago #
6. 

   feurig
   Member

   Thats a python error.

   That looks a lot like a "python 3 makes significant changes so no one is adapting or testing against it yet" error.

   Can you try it with python2.7?

   I have only run the stmloader with python 2.5-2.7.3 and it seems to work well on linux and osx on those versions.
   I have only done pyserial and wxpython stuff using python for windows (also version 2.7)

   I am surprised no one has made a py2exe bundle for it.

   Posted 3 years ago #
7. 

   Leonardo
   Member

   Hi feurig.

   I tried what you said but the result was:

   Microsoft Windows [versão 6.1.7600]
   Copyright (c) 2009 Microsoft Corporation. Todos os direitos reservados.

   C:\Users\Leonardo>cd c:\python27

   c:\Python27>python.exe stm32loader.py -p COM3 -evw maple_mini_boot.bin
   Reading data from maple_mini_boot.bin
   Can't init. Ensure BOOT0=1, BOOT1=0, and reset device
   Traceback (most recent call last):
   File "stm32loader.py", line 486, in <module>
   bootversion = cmd.cmdGet()
   File "stm32loader.py", line 139, in cmdGet
   if self.cmdGeneric(0x00):
   File "stm32loader.py", line 136, in cmdGeneric
   return self._wait_for_ack(hex(cmd))
   File "stm32loader.py", line 87, in _wait_for_ack
   raise CmdException("No response to %s" % info)
   __main__.CmdException: No response to 0x0

   My "boot1" pin has already set to the ground. I run the "built-in serial bootloader" exactly as step 3:

   Step 3: Run the built-in hardware serial bootloader[2]. Accomplish this using the following steps:

   Press and hold the reset and BUT buttons.
   Release the reset button without releasing BUT.
   Release BUT.

   Need I set the "but" pin (pin 32) to Vcc as i put the "boot1" pin to the ground (phisically, with a wire)?

   Posted 3 years ago #
8. 

   feurig
   Member

   Thats better. Now the issues are related to the chip not talking to you. Yes you do need to wire boot1 to gnd and pull boot0 high (which is what holding the button does) during the reset. It couldn't hurt to just hardwire boot0 high until you get the bootloader talking. At some point one of us should probably tweak on the python so it handles the exception a bit more gracefully.

   Posted 3 years ago #

RSS feed for this topic

Reply

You must log in to post.