[mc1322x] OpenOCD custom proc

[Daniel Berenguer]

Yes, that's an option... So in your daily job you just write the RAM
through serial? I may do this too I guess, to avoid useless flash
writes during development.

Thanks Jon for this remark.

Daniel.


On 7 June 2010 18:54, Jon Smirl <jonsmirl at gmail.com> wrote:
> On Mon, Jun 7, 2010 at 12:06 PM, Daniel Berenguer
> <dberenguer at usapiens.com> wrote:
>> Sorry guys to come back with basic issues...
>>
>> I'm trying to flash a binary into one of my EconoTags through a single
>> OpenOCD command as follows:
>>
>> openocd -f ../openocd.cfg -c "run blink-green_redbee-econotag.bin"
>>
>> but I'm getting this error:
>>
>> Runtime error, file "../openocd.cfg", line 80:
>> invalid command name "soft_reset_halt"
>
> Mar can explain the error...
>
> You don't have to flash the mc13224 chips. The chips have 96KB of RAM
> on them. Just send your code into RAM and run it. Only flash when your
> code is working and you want to unplug the econotag and take it
> somewhere else. Developing out of RAM is many times faster than
> flashing.
>
>
>>
>> Same thing with "load_image" if I comment the above command in openocd.cfg.
>>
>> I'm currently using Mar's cfg file with the latest OpeOCD version (0.4.0)
>>
>> On my old OpenOCD version (0.0), I used to halt/wait_halt instead of
>> soft_reset_halt. As for writing new images I used "flash write"
>> instead of load_image. The funny thing is that OpenOCD is accepting
>> both commands via telnet but not through the custom "run" proc.
>>
>> Any help is appreciated. Thanks!
>>
>> Daniel.
>>
>> _______________________________________________
>> mc1322x mailing list
>> mc1322x at devl.org
>> http://devl.org/cgi-bin/mailman/listinfo/mc1322x
>>
>
>
>
> --
> Jon Smirl
> jonsmirl at gmail.com
>