Am 14.07.2013 00:45, schrieb Pete Batard:
> On 2013.07.12 10:21, Andreas Fritiofson wrote:
>> Are you talking about the same patches that are published in gerrit,
>> ending with http://openocd.zylin.com/1464 ?
>
> Dunno. I was pointed to a mips github repo, that may or may not include
> these patch
On 2013.07.12 10:21, Andreas Fritiofson wrote:
> Are you talking about the same patches that are published in gerrit,
> ending with http://openocd.zylin.com/1464 ?
Dunno. I was pointed to a mips github repo, that may or may not include
these patches, and this is what I have been using for my test
On Fri, Jul 12, 2013 at 1:21 AM, Pete Batard wrote:
>
> At any rate, this looks fairly good to me. Nice work!
>
>
Are you talking about the same patches that are published in gerrit, ending
with http://openocd.zylin.com/1464 ? Then please post your feedback there.
Most maintainers are relatively
Hi Oleksij, sorry for the late reply.
On 2013.07.04 18:44, Oleksij Rempel wrote:
> It doesn’t meter what do you use. Just dissas, first part of first stage
> boot loader and try to use break points. And compare your results with
> disassembled code.
>
> Here is one example:
> reset; sleep 1; halt
Am 04.07.2013 01:35, schrieb Pete Batard:
> On 2013.07.03 06:22, Oleksij Rempel wrote:
>>> And once more, many thanks for the help there. If there's additional
>>> feedback you'd like to have, let me know - I'll see what I can do.
>>
>> Yes, i need some tests on breakpoints and watchpoints.
>>
>> I
On 2013.07.03 06:22, Oleksij Rempel wrote:
>> And once more, many thanks for the help there. If there's additional
>> feedback you'd like to have, let me know - I'll see what I can do.
>
> Yes, i need some tests on breakpoints and watchpoints.
>
> If you can dissamble you bootloader it will be grea
Am 03.07.2013 03:08, schrieb Pete Batard:
> On 2013.07.02 08:08, Oleksij Rempel wrote:
>> enable debug mode and you will get some thing like "EJTAG: features ..."
>
> Debug: 261 45327 mips_ejtag.c:352 mips_ejtag_init(): impcode: 0x00800904
> Debug: 262 45327 mips_ejtag.c:359 mips_ejtag_init(): EJTA
On Wed, Jul 3, 2013 at 9:08 AM, Pete Batard wrote:
> By the way, is there an option to specify libftdi 1.0 over 0.x? Right
> now I'm replacing the -lftdi with -lftdi1 in configure.ac & Makefile.am,
> but I'm wondering if I'm missing something in terms of conf.
>
Yes it is good to migrate from lib
On 2013.07.02 08:08, Oleksij Rempel wrote:
> enable debug mode and you will get some thing like "EJTAG: features ..."
Debug: 261 45327 mips_ejtag.c:352 mips_ejtag_init(): impcode: 0x00800904
Debug: 262 45327 mips_ejtag.c:359 mips_ejtag_init(): EJTAG: Version 1 or
2.0 Detected
Debug: 263 45327 mip
Am 30.06.2013 22:05, schrieb Pete Batard:
> Hi Oleksij, thanks for the reply.
>
> On 2013.06.30 07:15, Oleksij Rempel wrote:
>> right now i'm fighting one of broadcom SOCs. But it seems like yours is
>> other kind. Can you please tell which EJTAG version is it?
>
> I actually have no idea. Is there
Hi Oleksij, thanks for the reply.
On 2013.06.30 07:15, Oleksij Rempel wrote:
> right now i'm fighting one of broadcom SOCs. But it seems like yours is
> other kind. Can you please tell which EJTAG version is it?
I actually have no idea. Is there a way to find out that information
without having
Hi Pete
right now i'm fighting one of broadcom SOCs. But it seems like yours is
other kind. Can you please tell which EJTAG version is it?
Any way. About endians
you can check CP0 Status and Config registers by using this commands:
mips32 cp0 12 0
mips32 cp0 15 0
At least it should display what
Well, since I'm here, and never got around to report the following:
I've been using OpenOCD 7.0 in order to access a Broadcom BCM6338 (MIPS
big endian) based board that also sports 4 MiB of Spansion
S29GL032A90TFIR4 flash.
Eventually, what I'd like to do is be able to use the OpenOCD CFI
imple
13 matches
Mail list logo
