>
> 3. I've written a Python script that will run a C file declaring a naked
> function through arm-none-eabi-gcc to generate an assembly listing, then
> extract the opcodes and output them as a C file that defines a static const
> uint8_t[] array, like kinetis_flash_write_code in kinetis.c. Where would
> be the best place to put this? Should I cut and paste the code into
> kinetis.c (following existing convention) or #include it from elsewhere?
>
> There is a simpler way: src/helper/bin2char.sh - see
> http://openocd.zylin.com/#/c/3134/
> and http://openocd.zylin.com/#/c/3235/
>
Ah, that looks more portable (although the output is less pretty -- my
script gives you the C listing and assembly as well as just the bytes :)
). It looks like the code in contrib/loaders/flash/at91sam7x shows how to
compile C down to binary. I'll see what I can do with that.
Thanks!
Phil
------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
_______________________________________________
OpenOCD-devel mailing list
OpenOCD-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openocd-devel
