andr...@fritiofson.net wrote:
On Fri, Dec 17, 2010 at 4:36 PM, Jonathan dumaresq
jdumar...@cimeq.qc.ca wrote:
Hi all,
Here my first patches to be able to use the CFI driver on cortex M3
with the helper code on target. This is probably not the better way
of
doing it, but at least it's
openocd-development-boun...@lists.berlios.de wrote:
On Sun, Dec 19, 2010 at 3:56 AM, Michael Schwingen
rincew...@discworld.dascon.de wrote:
I think it is time to re-factor that target-algorithm code and pull
the target dependencies out of the CFI code, but that would be a
separate step.
On Fri, Dec 17, 2010 at 4:36 PM, Jonathan dumaresq
jdumar...@cimeq.qc.ca wrote:
Hi all,
Here my first patches to be able to use the CFI driver on cortex M3 with the
helper code on target. This is probably not the better way of doing it, but
at least it's work. This have been tested on real
On Sun, Dec 19, 2010 at 3:56 AM, Michael Schwingen
rincew...@discworld.dascon.de wrote:
I think it is time to re-factor that target-algorithm code and pull the
target dependencies out of the CFI code, but that would be a separate step.
Fully agree!
Hi all,
Here my first patches to be able to use the CFI driver on cortex M3 with the
helper code on target. This is probably not the better way of doing it, but
at least it's work. This have been tested on real hardware. The default cfg
that enable the fsmc can be used. Right now only the 16 bit
: Jonathan dumaresq
Cc : 'Antonio Borneo'; openocd-development@lists.berlios.de
Objet : Re: [Openocd-development] Problem loading to CFI flash
On 06/12/2010 14:42, Jonathan dumaresq wrote:
Have you fond some time to test this ?
I have run a quick test and it fails for me also.
As a quick test i
...@lists.berlios.de] De la part de Jonathan
dumaresq
Envoyé : 7 décembre 2010 11:25
À : 'Spencer Oliver'
Cc : openocd-development@lists.berlios.de
Objet : Re: [Openocd-development] Problem loading to CFI flash
Hi Spen,
I'm happy that i'm not the only one !!!
Is it possible to send or put somewhere a windows
-development-boun...@lists.berlios.de] De la part de Jonathan
dumaresq
Envoyé : 14 décembre 2010 13:27
À : 'Spencer Oliver'
Cc : openocd-development@lists.berlios.de
Objet : Re: [Openocd-development] Problem loading to CFI flash
Hi,
I have pull the head branch of openocd and now I can write
On Tue, Dec 14, 2010 at 7:26 PM, Jonathan dumaresq
jdumar...@cimeq.qc.ca wrote:
Hi,
I have pull the head branch of openocd and now I can write to the cfi at a
slow speed. I want to modify openocd to use the asm code for the cortex. I
have used the sample contrib file as starting point for
Hi Spen,
I'm happy that i'm not the only one !!!
Is it possible to send or put somewhere a windows version that works ? I
have never compiled openocd so, if you can provide the binary file i'll be
happy. If not I can try to compiled it too.
Regards
Jonathan
Spencer Oliver wrote:
On 06/12/2010
On 06/12/2010 14:42, Jonathan dumaresq wrote:
Have you fond some time to test this ?
I have run a quick test and it fails for me also.
As a quick test i commented out block writes (cfi_write_words) and it
works as expected - albeit even slower.
Also found this patch where they have
Hi Spen,
Spencer Oliver wrote:
On 23/11/2010 03:04, Antonio Borneo wrote:
Jonathan,
could you please report the full part number of the flash chip?
Form the log, seems Numonyx M29W128G
Flash Manufacturer/Device: 0x0020 0x227e
Spencer,
the flash M29W128G has a HW bug. Numonyx
Hi Michael,
openocd-development-boun...@lists.berlios.de wrote:
On 11/22/2010 07:10 PM, Jonathan dumaresq wrote:
Cannot see anthing wrong with that log - except it is probably slow.
Cheers
Spen
The problem seem to me that the remaining bytes should be zero at the
end of the flashing ?
Hi Antonio,
Antonio Borneo wrote:
Jonathan,
could you please report the full part number of the flash chip?
Form the log, seems Numonyx M29W128G
Flash Manufacturer/Device: 0x0020 0x227e
Yes this is the part in question. M29W128GL70N6E
Spencer,
the flash M29W128G has a HW bug. Numonyx
On 23/11/2010 03:04, Antonio Borneo wrote:
Jonathan,
could you please report the full part number of the flash chip?
Form the log, seems Numonyx M29W128G
Flash Manufacturer/Device: 0x0020 0x227e
Spencer,
the flash M29W128G has a HW bug. Numonyx application note in
Antonio Borneo wrote:
On Sat, Nov 20, 2010 at 4:51 AM, Jonathan dumaresq
jdumar...@cimeq.qc.ca wrote:
Hi all,
I try to get my cfi external nor flash programmed with openocd.
flash write_image test.hex 0x6400 bin
current target isn't an ARMV7M target
I have no idea why ARMV7M is
Hi Spencer,
Spencer Oliver wrote:
On 20/11/2010 01:39, Antonio Borneo wrote:
Ciao Jonathan,
OpenOCD runs binary code on the target CPU to speed-up some operation
that through JTAG would take too long.
Programming the Flash is one of them.
In the CFI driver there is the binary code for
Hi spencer,
Spencer Oliver wrote:
On 20/11/2010 01:39, Antonio Borneo wrote:
Ciao Jonathan,
OpenOCD runs binary code on the target CPU to speed-up some operation
that through JTAG would take too long.
Programming the Flash is one of them.
In the CFI driver there is the binary code for
What you found is a missing feature of OpenOCD.
The fix would require one of the following:
- a specific code for ARMV7M (this will solve your case only)
- a fall-back C code in case of no binary for target (solves all
cases, but slow)
I tried this approach but the writing of the image hangs.
Hi,
Spencer Oliver wrote:
What you found is a missing feature of OpenOCD.
The fix would require one of the following:
- a specific code for ARMV7M (this will solve your case only)
- a fall-back C code in case of no binary for target (solves all
cases, but slow)
I tried this approach but
On 11/22/2010 07:10 PM, Jonathan dumaresq wrote:
Cannot see anthing wrong with that log - except it is probably slow.
Cheers
Spen
The problem seem to me that the remaining bytes should be zero at the end of
the flashing ?
It should be, yes.
However, I can't see the end in the log - did it
Jonathan,
could you please report the full part number of the flash chip?
Form the log, seems Numonyx M29W128G
Flash Manufacturer/Device: 0x0020 0x227e
Spencer,
the flash M29W128G has a HW bug. Numonyx application note in
http://www.numonyx.com/Documents/Application%20Notes/AN309814.pdf
You
On 20/11/2010 01:39, Antonio Borneo wrote:
Ciao Jonathan,
OpenOCD runs binary code on the target CPU to speed-up some operation
that through JTAG would take too long.
Programming the Flash is one of them.
In the CFI driver there is the binary code for generic ARM only.
Hi all,
I try to get my cfi external nor flash programmed with openocd.
I use en stm32 chip with the FSMC to talk to the CFI flash. Write now I can
get the openocd reconised the cfi chip.
cfi information:
mfr: 0x0020, id:0x227e
qry: 'QRY', pri_id: 0x0002, pri_addr: 0x0040, alt_id: 0x,
On Sat, Nov 20, 2010 at 4:51 AM, Jonathan dumaresq
jdumar...@cimeq.qc.ca wrote:
Hi all,
I try to get my cfi external nor flash programmed with openocd.
I use en stm32 chip with the FSMC to talk to the CFI flash. Write now I can
get the openocd reconised the cfi chip.
snip
flash write_image
25 matches
Mail list logo
