On Mon, May 25, 2009 at 10:09 AM, Xiaofan Chen wrote:
> Now we are testing other hex file. I believe there may be two issues
> involved after Michael fixed the checksum issue for lpc-2148.
>
> 1) Potential J-Link stability issues. I will check out V6. If it is ok
> and V3 is not, then V3/V4 may n
On Mon, May 25, 2009 at 9:58 PM, Xiaofan Chen wrote:
> On Mon, May 25, 2009 at 9:56 PM, Xiaofan Chen wrote:
>> On Mon, May 25, 2009 at 9:46 PM, Xiaofan Chen wrote:
> But it still does not work with the lpcusb isoc hex file.
>>>
>>> According to vbindiff report of the dump file, the first 0x1
On Mon, May 25, 2009 at 9:56 PM, Xiaofan Chen wrote:
> On Mon, May 25, 2009 at 9:46 PM, Xiaofan Chen wrote:
But it still does not work with the lpcusb isoc hex file.
>>
>> According to vbindiff report of the dump file, the first 0x160
>> portion of the dump is not correct. Other than that, i
On Mon, May 25, 2009 at 9:46 PM, Xiaofan Chen wrote:
>>> But it still does not work with the lpcusb isoc hex file.
>
> According to vbindiff report of the dump file, the first 0x160
> portion of the dump is not correct. Other than that, it seems
> to be ok.
>
> dump_isoc.bin is from OpenOCD.
> iso
On Mon, May 25, 2009 at 8:13 PM, Xiaofan Chen wrote:
>>> With the simple script, V1906 can talk to J-Link V6. It seems to
>>> work with your simple LED 1/2 blinking hex file. I tried both
>>> jlink_hw_jtag 2 or 3.
>>>
>>> More tests to follow.
>>
>> But it still does not work with the lpcusb isoc
On Sun, May 24, 2009 at 5:59 PM, Michael Fischer wrote:
>
> But it could be possible that the J-Link had a problem too.
>From all the tests, it seems to me that it is a J-Link problem.
It seems to me that you can flash the LPC-2148 with ft2232
interface or with the Segger J-Flash using J-Link. Bu
On Mon, May 25, 2009 at 8:09 PM, Xiaofan Chen wrote:
> On Mon, May 25, 2009 at 8:02 PM, Xiaofan Chen wrote:
>> With the simple script, V1906 can talk to J-Link V6. It seems to
>> work with your simple LED 1/2 blinking hex file. I tried both
>> jlink_hw_jtag 2 or 3.
>>
>> More tests to follow.
>
On Mon, May 25, 2009 at 8:02 PM, Xiaofan Chen wrote:
> With the simple script, V1906 can talk to J-Link V6. It seems to
> work with your simple LED 1/2 blinking hex file. I tried both
> jlink_hw_jtag 2 or 3.
>
> More tests to follow.
But it still does not work with the lpcusb isoc hex file.
mc.
On Mon, May 25, 2009 at 7:43 PM, Xiaofan Chen wrote:
>> I will try with the J-Link V6 a bit later and report.
>>
> Somehow 1906 can not connect to my J-Link V6 with your script.
With the simple script, V1906 can talk to J-Link V6. It seems to
work with your simple LED 1/2 blinking hex file. I tri
On Mon, May 25, 2009 at 7:31 PM, Xiaofan Chen wrote:
> I will try with the J-Link V6 a bit later and report.
>
Somehow 1906 can not connect to my J-Link V6 with your script.
mc...@ubuntu904:~/Desktop/build/openocd/jlinkv6$ openocd -f jlink.cfg
Open On-Chip Debugger 0.2.0-in-development (2009-05
On Sun, May 24, 2009 at 11:10 PM, Michael Fischer wrote:
> Hello Xiaofan,
>
> I have tesed to flash the program here. I could flash it
> with my ft2232 device. I do not check the functionality
> of the program itself, LED1 was flashing.
And you can switch on/off LED 2 by pressing the
two switches
On Sun, May 24, 2009 at 7:03 PM, Michael Fischer wrote:
> Now I take a look in the openocd manual and found the following
> information:
>
> 13.2.2.1 lpc2000 options
> flash bank lpc2000 0 0[calc
> checksum]
>
> ...and the optional keyword calc checksum, telling the
> driver to calculate a v
On Sun, May 24, 2009 at 5:32 PM, Xiaofan Chen wrote:
> The script from Michael seems to be better and I can halt the target.
> But the flashing problem is still there. Michael is helping me on this.
> He is thinking that the hex file is without a checksum and there are
> some problems with the sta
On Sun, May 24, 2009 at 11:10 PM, Michael Fischer wrote:
> Hello Xiaofan,
>
> I have tesed to flash the program here. I could flash it
> with my ft2232 device. I do not check the functionality
> of the program itself, LED1 was flashing.
In my test, LED 1 is also flashing. The USB virtual
com port
aof...@gmail.com]
Gesendet: Sonntag, 24. Mai 2009 16:02
An: Michael Fischer
Cc: Openocd-Dev; z...@superlucidity.net
Betreff: Re: [Openocd-development] Correct script to flash the lpc-2148
On Sun, May 24, 2009 at 8:55 PM, Xiaofan Chen wrote:
> On Sun, May 24, 2009 at 7:03 PM, Michael Fischer
On Sun, May 24, 2009 at 8:55 PM, Xiaofan Chen wrote:
> On Sun, May 24, 2009 at 7:03 PM, Michael Fischer
> wrote:
>
>> Attached is the main.hex file which should work with the lpc2148 without
>> the calc_checksum key. LED1 and LED2 are flashing.
>
> Yes this works well with my V3 Black Jlink. The
On Sun, May 24, 2009 at 7:03 PM, Michael Fischer wrote:
> Attached is the main.hex file which should work with the lpc2148 without
> the calc_checksum key. LED1 and LED2 are flashing.
Yes this works well with my V3 Black Jlink. The two LEDs are flashing now.
I updated to the latest SVN with your
Hello list,
now I could reproduce the problem here with the original
Olimex BLINK example. It will not work, the problem is the
checksum.
The startup code looks like:
_vectors: ldr PC, Reset_Addr
ldr PC, Undef_Addr
ldr PC, SWI_Addr
Hello Xiaofan,
>With your script, I can flash the files and I can halt the target.
>However the flashing is apparently not correct as it does not
>work. Using lpc21isp it works.
first of all I think it is a checksum problem which control a
valid user code. Take a look in the LPC2148 user manual.
On Sun, May 24, 2009 at 5:04 PM, Magnus Lundin wrote:
> Hi
>
> This looks like a reset problem, not a write to flash problem. This is the
> type of problems we are trying fix with the latest jtag/jlink/ft2232
> patches.
>
> What is the target configuration.
>
Here it is.
source [find target/lpc2
On Sun, May 24, 2009 at 4:42 PM, Xiaofan Chen wrote:
> I am using the following simple script and J-Link V3.
> I will try yours as well.
>
With your script (replace with JLink) it seems to be ok. Thanks.
Occasionally there are some timeout though.
mc...@ubuntu904:~/Desktop/build/openocd/jlinkv3/
On Sun, May 24, 2009 at 5:02 PM, Xiaofan Chen wrote:
> On Sun, May 24, 2009 at 4:42 PM, Xiaofan Chen wrote:
>> I am using the following simple script and J-Link V3.
>> I will try yours as well.
>>
>
> With your script (replace with JLink) it seems to be ok. Thanks.
> Occasionally there are some t
Hi
This looks like a reset problem, not a write to flash problem. This is
the type of problems we are trying fix with the latest jtag/jlink/ft2232
patches.
What is the target configuration.
Best regards
Magnus
Xiaofan Chen skrev:
> Relative long email.
>
> I have not tried to use flashing so
On Sun, May 24, 2009 at 4:08 PM, Michael Fischer wrote:
> Here I have a Olimex LPC-P2148 board too, tested with a FT2232
> device under windows, with the r1893.
>
> For testing, I have a short hex file, called test_rom.hex
>
> 1) flash write_image test_rom.hex 0x0
> 2) dump_image dump.bin 0x0 364
Hello Xiaofan,
>I have not tried to use flashing so far. So today I tried to learn how to
>flash the LPC2148 on board of the Olimex LPC-P2148.
>
>I tried to halt the target and then use
>"flash write_image isoc_io_sample.hex 0x0 ihex" but this does
>not seem to work.
Here I have a Olimex LPC-P21
On Sun, May 24, 2009 at 11:18 AM, Xiaofan Chen wrote:
> After this error, I have to unplug everything and then use lpc21isp
> to flash the target so that I can run OpenOCD again with J-Link V3.
>
> I know the hex is correct since the target works when flashing
> with lpc21isp. The hex file is buil
Relative long email.
I have not tried to use flashing so far. So today I tried to learn how to
flash the LPC2148 on board of the Olimex LPC-P2148.
I tried to halt the target and then use
"flash write_image isoc_io_sample.hex 0x0 ihex" but this does
not seem to work. Then I tried to use the follow
27 matches
Mail list logo
