Re: [Openocd-development] status of cortex-m0
On Thu, 27 Oct 2011 08:45:57 -0500, Christopher Harvey wrote: Xiaofan Chen, aren't you a versaloon developer? Your name is on the versaloon paypal order page. My bad. The Versaloon guy is Qian Xiaochen, not Xiaofan Chen ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] status of cortex-m0
On Thu, 27 Oct 2011 13:08:57 +0800, Xiaofan Chen wrote: On Thu, Oct 27, 2011 at 11:24 AM, Christopher Harvey ch...@basementcode.com wrote: I read a thread about somebody who apparently got cortex m0 cores working with OpenOCD. (based on the m3 code). Did that patch ever get posted somewhere? Anybody following/working on m0 right now? The Cortex M0 support will most likely depend on the SWD support which is now on progress. Reference thread. http://lists.berlios.de/pipermail/openocd-development/2011-June/019303.html Not so sure about the status on Versaloon's swd implementation. You can check with Simon Qian. http://www.versaloon.com/index.html http://lists.berlios.de/pipermail/openocd-development/2011-April/018838.html thanks for the threads. I just ordered a Versaloon Mini. I saw there are swd related files in OpenOCD version 0.5.0, so I assumed it was supported. Also the versaloon site says: I can provide the patch for OpenOCD adding SWD support. OpenOCD will integrate SWD support in 0.5.0 release. Xiaofan Chen, aren't you a versaloon developer? Your name is on the versaloon paypal order page. ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
[Openocd-development] status of cortex-m0
I read a thread about somebody who apparently got cortex m0 cores working with OpenOCD. (based on the m3 code). Did that patch ever get posted somewhere? Anybody following/working on m0 right now? ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] git question.....
On 25/10/11 07:57 PM, jim norris wrote: I do the following... git add file1.c git commit file1.c git push review git add file2.c git commit file2.c git push review git add file3.c git commit file3.c git push review I then realize I made a mistake in file1.c so... -- make the change git add file1.c git commit --amend file1.c However, the comment message I see when I do the commit is from the commit of file3.c. Is this okay? Or did I do something wrong? I've noticed there's a -C option that indicates to pick up information from a previous commit. Is that what should be used? afaik you can only change the last commit with amend. You'd need to do a commit like normal for the last file1.c change, then rebase all the (4) commits interactively and merge the last and 1st onesbut then again this wouldn't be the first time somebody pointed out to me some easier way to do the same thing with git. ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] Request for review: driver for Keil ULINK
On Tue, 21 Jun 2011 18:34:16 +0200, Martin Schmölzer martin.schmoel...@student.tuwien.ac.at wrote: Hi, my ULINK driver for OpenOCD is finally in a usable state. Attached is a patch set that adds this driver + the custom firmware for the ULINK adapter. Currently, this is only tested with an Olimex STM32-P103 development board (STM32F103RBT6). stm32x mass_erase and flash write_image erase both work. The driver/firmware uses one USB bulk endpoint and is designed to queue several commands into one packet for better throughput. The first version of the driver used the naive approach of one packet per command which (of course) had horrible performance (~ 800 Byte/sec flash speed for the STM32). The current implementation reaches about 4.5 kB/sec, which seems to be the maximum I can get out of the Cypress EZ-USB MCU that is used in the ULINK adapter. Some features are still incomplete: - Pathmove commands - TCK speed: Currently, the ULINK only works at its maximum TCK frequency (about 150 kHz, measured using a digital storage oscilloscope). I'm planning to complete these features and further testing by early/mid july. Feedback is highly appreciated! Best regards, Martin Hi Martin, I've got a ulink at home with an MCB board (I forgot the exact number), so this is exciting news for me. I've been wanting to lean the internals of OCD and Jtag for a while, could anybody suggest some technical jtag/gdb/arm documents? I am also curious, how did you figure out the format of the data in the packets you're sending to the Ulink? thanks, -Chris ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
