>> Also if i remember correctly the flash controller is not exactly the >> same as the stm32f1x, may be worth checking the em357 driver. >> The em35x family are the same device as the stm32w.
The chip I have is the STM32w108CB, which has 8kb of ram and 128kb of flash. The Ember 351 and 357 both have 12kb of ram and 128/192kb of flash, respectively. I suppose this ram difference won't really matter for the purpose of flashing a program? Interestingly, when I do: set _CHIPNAME em357 and then run openocd, and telnet in and do: > flash probe 0 flash size = 192kbytes flash 'em357' found at 0x08000000 Which indicates to me that perhaps it isn't really probing the chip but is just using what is hard coded into em357.c (i.e., 192kb, instead of 128kb)? Looking into that file indicates that this is the case (lines 718-720 of em357.c). Does this then mean I would need to write a different driver for the em351/stm32w108cb? Or can this be dealt with purely with configuration files (i.e. the .cfg tcl files)? ~Luke ------------------------------------------------------------------------------ Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d _______________________________________________ OpenOCD-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
