http://forums.leaflabs.com/topic.php?id=113 A place to share, learn, and grow... en-US Fri, 22 Jan 2016 00:14:43 +0000 http://bbpress.org/?v=1.0.2 q http://forums.leaflabs.com/search.php http://forums.leaflabs.com/topic.php?id=113&page=2#post-752 Tue, 17 Aug 2010 14:14:56 +0000 poslathian 752@http://forums.leaflabs.com/ <p>excellent! very nice hunting and good find. This will get generalized (adding wTransferSize to DFUUploader etc) in a later version of the IDE as we are expanding to support more stm32 chiptypes as well and likely parameterized in the bootloader as well. </p> <p>For the record, the stm32f103rbt6 on maple is a medium density device. The ret6 is a high density chip. </p> http://forums.leaflabs.com/topic.php?id=113&page=2#post-733 Thu, 12 Aug 2010 20:09:06 +0000 x893 733@http://forums.leaflabs.com/ <p>4P.S.<br /> Simple resolve this issue - change<br /> #define wTransferSize 0x0800<br /> in usb.h and rebuild(!) project<br /> All work correctly. </p> http://forums.leaflabs.com/topic.php?id=113&page=2#post-723 Thu, 12 Aug 2010 05:17:26 +0000 x893 723@http://forums.leaflabs.com/ <p>P.P.P.S<br /> It's a very helpfull if you add<br /> transfer-size parameter to DFUUploader.java and to boards.txt<br /> (may be all parameters for dfu-util program ?) </p> http://forums.leaflabs.com/topic.php?id=113&page=2#post-722 Thu, 12 Aug 2010 05:06:19 +0000 x893 722@http://forums.leaflabs.com/ <p>P.P.S<br /> How to set transfer-size parameter in maple-ide settings ? </p> http://forums.leaflabs.com/topic.php?id=113&page=2#post-721 Thu, 12 Aug 2010 04:57:23 +0000 x893 721@http://forums.leaflabs.com/ <p>P.S. After change<br /> #define wTransferSize 0x0800<br /> in usb.h<br /> i can correct download program to flash with dfu-util -t 2048 </p> http://forums.leaflabs.com/topic.php?id=113#post-720 Thu, 12 Aug 2010 04:42:02 +0000 x893 720@http://forums.leaflabs.com/ <p>Hi again,<br /> after some investigation i understand problem.<br /> Low density STM32 has 0x400 page size (1024 byte) but medium (for ex. RET6) has 2048 bytes page size. You use 1024 packet size and erase page on each packet (by write address). After transmit first block (at address 8005000) use corrently erase page and flash 1024 bytes. After trasmit second block you erase page (but for 2048 block you erase first block also) and write second block correctly (but first block erased). It means that each even block erased and odd block correct.</p> <p>I try use -t 2048 parameter in dfu-util but bootloader crash with this block size.<br /> Because your bootloader code very professional i can't suggest way to resolve this issue.</p> <p>Best regards<br /> Mitek </p> http://forums.leaflabs.com/topic.php?id=113#post-709 Tue, 10 Aug 2010 12:52:43 +0000 poslathian 709@http://forums.leaflabs.com/ <p>I wouldnt expect things to work stock with a higher density chip. You will definitely need to adjust the linker files in github-repo/libmaple/support/ld </p> http://forums.leaflabs.com/topic.php?id=113#post-705 Tue, 10 Aug 2010 09:29:18 +0000 manelcig 705@http://forums.leaflabs.com/ <p>Hi,</p> <p>I'm facing exactly the same problem. I'm working with another board with an STM32F103RET.</p> <p>I tried using your bootloader, remade the makefile to work on windows and flashed it with jtag.<br /> Using the maple-ide I can upload the blinky example and all seems to go fine.<br /> However dumping the mem contents with OpenOCD it appears that instead of the code going to right places it goes to the locations referred on this thread's first post.<br /> I can only see 2 possibilities. Changes made to the makefile broke something, or linker file problem due to it being a high density device. </p> http://forums.leaflabs.com/topic.php?id=113#post-695 Sun, 08 Aug 2010 11:30:37 +0000 bnewbold 695@http://forums.leaflabs.com/ <p>Our "factory" versions of the bootloader are available as .bin files at <a href="http://static.leaflabs.com/pub/leaflabs/maple-bootloader/" rel="nofollow">http://static.leaflabs.com/pub/leaflabs/maple-bootloader/</a></p> <p>The rev3 version we currently ship with is maple_boot-rev3-9c5f8e.bin </p> http://forums.leaflabs.com/topic.php?id=113#post-691 Sat, 07 Aug 2010 16:13:08 +0000 x893 691@http://forums.leaflabs.com/ <p>Can you place your bootloader as binary file ? </p> http://forums.leaflabs.com/topic.php?id=113#post-688 Fri, 06 Aug 2010 02:51:30 +0000 x893 688@http://forums.leaflabs.com/ <p>Yes - i not use maple bootloader currently. Also i remove SPI and NOR download and add RAM download. I see dfu-util source - it's very easy. May be problem in libusb on W7. Can't say exactly - need time for investigation. </p> http://forums.leaflabs.com/topic.php?id=113#post-686 Thu, 05 Aug 2010 23:27:14 +0000 poslathian 686@http://forums.leaflabs.com/ <p>interesting. so youre using the ST DFUse firmware as a bootloader running on maple? You are NOT using the maple bootloader....if you are than I will be very surprised! </p> http://forums.leaflabs.com/topic.php?id=113#post-684 Thu, 05 Aug 2010 17:20:54 +0000 x893 684@http://forums.leaflabs.com/ <p>I make next actions for test<br /> 1. Adopt Device_Firmware_Upgrade from ST for Maple platform with led blinks, delay and USB pin analyzing/disconnect.<br /> 2. Convert Blink.cpp.bin to dfu format and upload it to Maple via DfuSeDemo.exe<br /> Perfect result under Windows 7. All write correctly.<br /> 3. Make a simplest dfu-util (on C#) which convert .....cpp.bin (from maple-ide) to ST dfu file and upload it via ST dfu protocol.</p> <p>Now not a problem with Windows 7<br /> Thanks for all </p> http://forums.leaflabs.com/topic.php?id=113#post-682 Thu, 05 Aug 2010 12:25:15 +0000 poslathian 682@http://forums.leaflabs.com/ <p>Ill have to hunt around for the source of our version of dfu-util, i think it was a snapshot of the repo from a while ago, it was stable to we held on to it. I believe dfu-util is back under active maintenance. </p> <p>The ST DFU upload will not work with the maple bootloader. In fact, the ST DFU is not DFU at all, but "DFUse" where the "se" stands for "st extended." This program is designed to work only with the ST DFU firmware (feel free to give this a try!) and it is not in anyway DFU compliant. the DFUse firmware wraps a propietary non-dfu protocol around a set of DFU device enumeration descriptors, and most of the heavy lifting (flash page clear/write algorithm) is left up to the host PC "DFU firmware uploader" software. Do let us know if you are able to use that software though. </p> <p>Can you share some of these binaries with us? We officially dont support win7 yet, but were getting there, and have are building a win7 test box. We have had several successful reports of users working with win7, but were still building up the list of "caveates" for us to fix for an official win7 release. Thanks for your help pointing out these problems! </p> http://forums.leaflabs.com/topic.php?id=113#post-680 Thu, 05 Aug 2010 03:09:11 +0000 x893 680@http://forums.leaflabs.com/ <p>Hi poslathian,</p> <p>first question - answer yes</p> <p>i program first 20K (from 8000000) via serial line (system bootloader) and STMicroelectronics flash loader.exe. It's equal maple-bootloader and work fine.</p> <p>After i use maple-ide to compile/upload code (simple blinky sketch) to board.<br /> It's say all ok but not work. I switch system bootloader again and read flash (from 800000 or from 8005000) and compare - from 8000000 to 8004FFFF with maple-bootloader and 80050000-.... with blink bin file (from TEMP/..... folder).</p> <p>I can find sources of dfu-util only from Openmoko but it's not equal to maple dfu-util.<br /> Where i can find sources for your version of dfu-util ?</p> <p>Also i start to adopt project Device_Firmware_Upgrade from ST (um0424.zip) to compare with dfu-util (for maple pins).</p> <p>Thanks<br /> Mitek </p>