Well...that is great and now everyone knows about your important
contributions to the project. Good for you!
On 9/1/09 5:12 PM, "Duane Ellis" wrote:
> I did *QUITE* a lot for the at91sam7 chips a when we first introduced
> TCL to openocd.
> I also did some more for the STM32 chip.
Gary Carlson wrote:
> I can now see that I left off a critical detail! :)
>
> Yes, you most certainly can use a TCL set command to accomplish this. The
> only issue is you have to spend an inordinate amount of time entering the
> values by hand. That in itself is another source for errors -- esp
On Monday 31 August 2009, Michael Schwingen wrote:
> > 3) One feature that I think may make sense to add at some point in the
> > future to the main software is support for label/value associations that
> > allow hexadecimal register values to be associated with more legible and
> > understandable
> Hm - yes, that might be useful. I have used objdump to extract the
> initialization tables from my board-init code to create BDI2000/OpenOCD
> init scripts.
Now, if we could do that in some *nice* way it would be quite
a powerful method. Most every PCB out there has some working
sample code
Øyvind Harboe wrote:
>> What advantage does that provide?
>> You need a disassembler to view the effective board-init sequence, you
>> need a cross-toolchain to modify the code, in comparison to just
>> changing a script file.
>>
>
> You can use the header files for the target file without hav
On Tue, Sep 1, 2009 at 10:24 AM, Michael
Schwingen wrote:
> Øyvind Harboe wrote:
>> Crazy idea:
>>
>> - write a small C app for the target that goes along with board config file
>> - this .elf file is loaded by OpenOCD
>> - use built-in ARM simulator to execute fn's in that .elf file
>>
> What adva
Øyvind Harboe wrote:
> Crazy idea:
>
> - write a small C app for the target that goes along with board config file
> - this .elf file is loaded by OpenOCD
> - use built-in ARM simulator to execute fn's in that .elf file
>
What advantage does that provide?
You need a disassembler to view the effe
Crazy idea:
- write a small C app for the target that goes along with board config file
- this .elf file is loaded by OpenOCD
- use built-in ARM simulator to execute fn's in that .elf file
?
--
Øyvind Harboe
Embedded software and hardware consulting services
http://www.zylin.com
_
On 9/1/09 12:04 AM, "Øyvind Harboe" wrote:
>> 2) One possible process improvement that I believe makes sense is to start
>> enforcing a rule that authors of new configuration files must include a
>> minimal comment header at the top of the file that specifies the exact
>> hardware/debugger co
I can now see that I left off a critical detail! :)
Yes, you most certainly can use a TCL set command to accomplish this. The
only issue is you have to spend an inordinate amount of time entering the
values by hand. That in itself is another source for errors -- especially
on processors with la
>> 3) One feature that I think may make sense to add at some point in the
>> future to the main software is support for label/value associations that
>> allow hexadecimal register values to be associated with more legible and
>> understandable names. Looking at "mww 0x3ec2 0x2" in a configura
> 2) One possible process improvement that I believe makes sense is to start
> enforcing a rule that authors of new configuration files must include a
> minimal comment header at the top of the file that specifies the exact
> hardware/debugger combination used. The SAM-ICE (J-link) debugger I am
Gary Carlson wrote:
> 1) One of the features that the software currently allows is configuration
> setting inheritance from board to target to CPU. While I generally am a big
> advocate of extensibility in most software projects, I have been very leery
> of doing this for hardware-specific configu
Hi Øyvind,
Yes, you are absolutely correct that configuration files are a lot of work
to put together. And I might add critical too! :)
One of the things I wanted to do is throw out some ideas for everyone to
think about as possible improvements to this configuration file development
process.
14 matches
Mail list logo
