On 04/09/2012 04:06 PM, Vaclav Peroutka wrote:
Load the init script: reset init
For flashing test.hex: flash write_image test.hex
Salvador, thank you, I forgot reset init. Anyway, programming and
debugging is terribly slow. I use Segger JLink with TCK set to 200
kHz. Programming of the
Load the init script: reset init
For flashing test.hex: flash write_image test.hex
Salvador, thank you, I forgot reset init. Anyway, programming and debugging
is terribly slow. I use Segger JLink with TCK set to 200 kHz. Programming of
the chip is even incorrect. So I tried to burn the
To check again, the chip I have is a PIC32MX220F032B,
CPUTAPID 0x40916053
Hi, are you sure about that ? Today I started to play with OpenOCD and PIC32. I
have exactly the same chip and my CPUTAPID is 0x04a00053.
What is the correct setting of WORKAREASIZE ? I use 0x1000. This PIC32 has 8kB
Hi, are you sure about that ? Today I started to play with OpenOCD and PIC32.
I
have exactly the same chip and my CPUTAPID is 0x04a00053.
What is the correct setting of WORKAREASIZE ? I use 0x1000. This PIC32 has 8kB
but first 2kB must be free, right ?
For development, do you use stock
On 04/08/2012 06:05 PM, Vaclav Peroutka wrote:
Hi, are you sure about that ? Today I started to play with OpenOCD and
PIC32. I
have exactly the same chip and my CPUTAPID is 0x04a00053.
What is the correct setting of WORKAREASIZE ? I use 0x1000. This PIC32 has
8kB
but first 2kB must be
On 20.03.2012 23:21, Spencer Oliver wrote:
strange the log points to issues with executing code from ram.
to help debug we need to split your cmd's up.
# erase full chip
flash erase_sector pic32mx.flash0 0 last
flash erase_sector pic32mx.flash1 0 last
# write image
flash write_image
On 21.03.2012 21:57, Vaclav Peroutka wrote:
in erase check, there is no error. And it ends with command_print():
successfully checked erase state message. But sections are marked as
not erased, right ? How long does the check take ?
about 70 sec
Can you read small block of FLASH in
On 20.03.2012 10:29, Spencer Oliver wrote:
according to the data the PIC32MX220F032B only has 8KB of RAM, so
set WORKAREASIZE 0X2000
before we try anything else you need to configure the correct working area.
Spencer,
doesn't change anything. Exactly the same result.
Cheers
Uhrheber
On 20 March 2012 10:09, Uhrheber uhrhe...@gtfe.de wrote:
On 20.03.2012 10:29, Spencer Oliver wrote:
according to the data the PIC32MX220F032B only has 8KB of RAM, so
set WORKAREASIZE 0X2000
before we try anything else you need to configure the correct working area.
Spencer,
doesn't
On 20.03.2012 11:10, Spencer Oliver wrote:
just realised you are using a 2x target - are you using the following patch ?
http://openocd.zylin.com/500
No.
Therefore my question about the status of the PIC32 support.
I should have been more specific.
I will try this.
BTW:
Exactly how do I
On 20 March 2012 10:45, Uhrheber uhrhe...@gtfe.de wrote:
On 20.03.2012 11:10, Spencer Oliver wrote:
just realised you are using a 2x target - are you using the following patch ?
http://openocd.zylin.com/500
No.
Therefore my question about the status of the PIC32 support.
I should have been
I applied the patch, but with no success.
Now I get other errors.
The code file works, t's a simple blink program.
I can flash it with a Pickit3.
Ideas?
Hi,
can you run any code from the RAM ? At least LED blinking ? I see this is first
error:
Error: 499 41826 mips32_pracc.c:1349
Hi.
Would anybody be so nice to give me an overview of the current status of
the PIC32 support?
I tried to flash a PIC32MX220F032B using a FT2232 based JTAG programmer
(PicoTAP).
The version I used was openocd-0.6.0-dev-120229143915 for Windows.
I was able to get contact to the MCU, I can read,
On 19 March 2012 12:35, Uhrheber uhrhe...@gtfe.de wrote:
Hi.
Would anybody be so nice to give me an overview of the current status of
the PIC32 support?
Should be working fine.
I tried to flash a PIC32MX220F032B using a FT2232 based JTAG programmer
(PicoTAP).
The version I used was
On 19.03.2012 14:21, Spencer Oliver wrote:
Thank you for your quick answer.
Than really makes things much clearer.
It will be very slow (but not that slow) without a working area
defined for your target.
How would I do that for the PIC32MX220F032B?
This chip has 4 memory areas with RAM, code
On 19 March 2012 13:37, Uhrheber uhrhe...@gtfe.de wrote:
On 19.03.2012 14:21, Spencer Oliver wrote:
Thank you for your quick answer.
Than really makes things much clearer.
It will be very slow (but not that slow) without a working area
defined for your target.
How would I do that for the
On 19.03.2012 16:01, Spencer Oliver wrote:
set WORKAREASIZE 8192
This makes 32kbytes.
how - 8192 bytes
It's a 32bit processor, so 8192 * 4 bytes makes 32kBytes.
Flash is defined in the same file as above - target/pic32mx.cfg
As long as your resulting hex/s19/elf has the correct memory
On 19 March 2012 15:36, Uhrheber uhrhe...@gtfe.de wrote:
On 19.03.2012 16:01, Spencer Oliver wrote:
set WORKAREASIZE 8192
This makes 32kbytes.
how - 8192 bytes
It's a 32bit processor, so 8192 * 4 bytes makes 32kBytes.
working area is in bytes honest.
Flash is defined in the same file
18 matches
Mail list logo
