![]() ![]() (I’ve not had chance to touch this in a long time though):some may help point you in the right direction (obv paths will need fixing)Download and install Segger Embedded Studio for ARMDownload and install Crossworks for ARM evaluation (code size limited) version - Open Crossworks and install following packages via the package manager: - ARM CPU support package - CMSIS 5 CMSIS-Core(M) support package - Crossworks Tasking Library - STM32F10x Standard Peripherals Library Updates -> C:\Users\Davidw\AppData\Local\SEGGER\SEGGER Embedded Studio\v3\packages\targets\STM32F10x Copy the packages directory from Crossworks to Segger, on Mac these are C:\Program Files\Rowley Associates Limited\CrossWorks for ARM 4.7 - ~/Library/SEGGER/SEGGER Embedded Studio/v3/packages - ~/Library/Rowley Associates Limited/CrossWorks for ARM/v4/packages Xcopy "C:\Users\Davidw\AppData\Local\Rowley Associates Limited\CrossWorks for ARM\v4\packages\*.*" "C:\Users\Davidw\AppData\Local\SEGGER\SEGGER Embedded Studio\v3\packages" /s /e Merge the include directory from Crossworks into Segger, replacing all newer files - ~/Applications/Segger./include on Windows this is in ProgramData (?) XCopy "C:\Program Files\Rowley Associates Limited\CrossWorks for ARM 4.7\include\*.*" "C:\Program Files\SEGGER\SEGGER Embedded Studio for ARM 5.34\include" /s /e /y Clone the LoxLink and ctl_fifo projects to your PC git clone ctl_fifo to Loxlink/Project/lib/ Execute downloadLoxoneAESKeys.py Change the extension of LoxLink_CW4.6.hzp to *.emproject and open itren LoxLink_CW4.6.hzp LoxLink_CW4.6.emprojectren LoxLink.hzp LoxLink.emproject Change the Project options for common build configuration Build - Correct memory map file - Correct DeviceVectorsFile under Project Macros - Correct target processor Debugger - Change whatever is necessary Preprocessor definitions in. I’ve just had a look at the notes I made a while ago on getting this working on windows. You are ether in boot mode or facing the same problem I did: #2 When the LEDs aren't blinking the application does not start. Your boards LED are on GPIOB, GPIO_PIN_13 and GPIO_PIN_14, as in the example from sarnau. Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned. when the two leds are blinking, the application is running, so you are not in the boot loader. if boot0 is set to 0 it does not matter what settings you have on boot1. The jumpers are for the boot mode of the stock boot loader of the stm32. David I started with the same board as you. On Sat,, 17:43 matlab22, wrote: I'm connected the board to loxlink but not getting too far at the moment, need to try and find a schematic for the board I have which is can then try and find out what LED is what, and that the two jumpers marked 0 and 1 are. I've not got as far as blinking leds, any ideas what io is allocated to d2 and d3?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |