LeafLabs Garden

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

1. 

   samtal
   Member

   Hi,
   I have several r5 all run ok.
   One of them runs fine, I can upload programs and run them, but I am unable to set it in the perpetual bootloader mode.
   Unlike the other boards where I can easily enter the boot mode by the Reset-BUT, on that one pressing the BUT does not seem to have any affect.
   While on 'normal' board, when pressing the reset, holding the BUT and releasing the reset, it enters the boot mode, no blinking until loading. In this one, when releasing the BUT it completes the reset, and does not enter boot mode.
   Here is the bootloader error mesage:

   E:\Documents and Settings\python27\python.exe E:\Maple\bootload
   er\stm32loader.py -p COM4 -evw E:\Maple\bootloader\maple_boot-rev3-9c5f8e.bin
   Reading data from E:\Maple\bootloader\maple_boot-rev3-9c5f8e.bin
   Can't init. Ensure that BOOT0 is enabled and reset device
   Traceback (most recent call last):
   File "E:\Maple\bootloader\stm32loader.py", line 461, in <module>
   bootversion = cmd.cmdGet()
   File "E:\Maple\bootloader\stm32loader.py", line 121, in cmdGet
   if self.cmdGeneric(0x00):
   File "E:\Maple\bootloader\stm32loader.py", line 118, in cmdGeneric
   return self._wait_for_ask(hex(cmd))
   File "E:\Maple\bootloader\stm32loader.py", line 69, in _wait_for_ask
   raise CmdException("No response to %s" % info)
   __main__.CmdException: No response to 0x0

   Posted 2 years ago #
2. 

   gbulmer
   Moderator

   samtal - IIRC there was a period where several people reported (on this forum) having a problem with buttons. IIRC it was diagnosed and fixed, but it really was the button itself. I thought that was before r5, but I might be mis-remembering.

   Could you try touching a wire across the two sides of the switch to short it? That might provide evidence that it is the button, in which case your supplier should fix it or replace the board.

   It wouldn't upload code without the bootloader, so it is unlikely to be that. Though you could write a tiny program to read the bootloader, and print it as hex on SerialUSB, copy and paste from the serial monitor into a file, and compare two boards.

   (Full disclosure: I am not a member of LeafLabs staff.)

   Posted 2 years ago #
3. 

   samtal
   Member

   Thanks gbulmer,
   Unfortunately it is not a hardware issue.
   I tested the BUT pin on the CPU (pin 40) and found out that the correct 3V signal is present when the BUT is pressed.

   Unless someone comes with a smart idea, I am afraid there is damage to the system (internal hardware or software) that inhibit the bootloader program loading.
   As the unit works fine, this will not present a problem until there will be the need to reload the bootloader, which may never occur.

   Posted 2 years ago #
4. 

   tormod
   Member

   samtal, you are not possibly mixing up "perpetual boot loader" and the "built-in serial bootloader"?
   - http://leaflabs.com/docs/bootloader.html
   - http://leaflabs.com/docs/troubleshooting.html#troubleshooting-perpetual-bootloader

   Posted 2 years ago #
5. 

   samtal
   Member

   Thanks tormod

   The Maple "boot loader" and the IDE are supposed together to load the built-in ST ARM USB driver AND its Windows Serial implementation driver, using two drivers: The Serial and the DFU (for win).
   (Both are located in the Maple Drivers library).
   The problem I am facing is that while the USB driver and port load nicely, it is not implemented as a serial port.
   Uninstalling and re-install the port makes no change to that.
   I have learned (and experienced) that kind of problem with Win7, but I am running WinXP whioch runs OK for other Maples.
   I have tried the same board, another computer, fresh Maple download (all, incl. drivers) for no avail.
   It still shows the Maple003 as pure USB port, no serial.
   Can anyone help?

   Posted 2 years ago #
6. 

   tormod
   Member

   Still not 100% clear to me. For the record, the stm32loader.py you are using in the original post is for the built-in serial bootloader, which you most likely are not interested in.

   When you say pure "USB port" do you mean you are stuck in the perpetual boot loader? This one shows up as a DFU USB device with USB ID of 1eaf:0003. Is that what you see in Device Manager or equivalent tools?

   When user code (a sketch) is running, the serial interface appears through a USB device of ID 1eaf:0004. Is this the one you see in Device Manager?

   Posted 2 years ago #

RSS feed for this topic

Reply

You must log in to post.