I have two things to contribute.
1. There is the USBDM project (http://usbdm.sourceforge.net) which I
just started using to program my KL15 based boards.
Might be something that could be used as a reference to see what's
needed to fix the Kinetis code.
2. I could test a patched OpenOCD wi
Hi Paul. :)
On Wed, 4 Feb 2015 00:20:30 +0300, Paul Fertser wrote:
>> What would be the preferred implementation - a new stand-alone
>> driver or a "one size fits all" ?
>
> [...] lower maintenance burden long-term [...]
> Usually sharing as much code as reasonably possible helps with that [...]
This is an automated email from Gerrit.
Paul Fertser (fercer...@gmail.com) just uploaded a new patch set to Gerrit,
which you can find at http://openocd.zylin.com/2529
-- gerrit
commit e9242a6444b556040bb5ddc0c11287108c569e84
Author: Paul Fertser
Date: Wed Feb 4 00:49:42 2015 +0300
doc:
Hi Jens :)
On Tue, Feb 03, 2015 at 01:19:21PM +0100, Jens Bauer wrote:
> What would be the preferred implementation - a new stand-alone
> driver or a "one size fits all" ?
In my opinion, preferred would be whatever gets the job done and has
lower maintenance burden long-term, I guess the maintain
Hello,
On Mon, Feb 02, 2015 at 07:00:45PM +0200, Liviu Ionescu wrote:
> I checked the latest openocd.pdf manual (Feb 2), and at page 42 the
> olimex-jtag is listed below the ft2232_layout command.
Right, because the legacy ft2232 driver supports Olimex adapters. It
doesn't mean though that it's t
On Tue, Feb 03, 2015 at 04:11:57PM +0100, Tomas Vanek wrote:
> Situation looks like the driver is little bit abandoned, isn't it?
As far as I can tell, there's no notion of a "driver maintainer" in
OpenOCD. It means that every now and then somebody who is interested
in specific hardware contribute
On 3.2.2015 11:11, Paul Fertser wrote:
> Hi,
>
> On Tue, Feb 03, 2015 at 09:39:34AM +0100, Tomas Vanek wrote:
>> I started working with Kinetis MK22FN1M0VLL12
> There's also an open issue regarding other Kinetis issue which is
> related: http://sourceforge.net/p/openocd/tickets/73/ .
I'm aware of t
hi all:
2015-02-03 19:20 GMT+08:00 vichy :
> hi Spencer:
>
> 2015-02-03 17:58 GMT+08:00 Spencer Oliver :
>> On 3 February 2015 at 07:55, vichy wrote:
>>>
>>> BTW, is it possible we did distcheck in the local instead of push to
>>> jenkins?
>>> such as any script in tools can help me?
>>>
>>> app
On 3.2.2015 12:18, Paul Fertser (Code Review) wrote:
> Paul Fertser has posted comments on this change.
>
> Change subject: psoc4: support for Cypress PSoC 41xx/42xx family
> ..
>
>
> Patch Set 4: Code-Review-2
>
> Hey Tomas,
>
> S
Hi Paul.
This might be slightly off-topic for this thread, but it is connected to the
Kinetis driver.
Tomas - some of the things I mention that differ might also differ on the K22,
if you can, please try verifying.
(My way of verifying was to take a K10 datasheet+RefMan and compare against the
Hi Tomas.
On Tue, 03 Feb 2015 08:22:00 +0100, Tomas Vanek wrote:
> I understand that nobody from maintainers or experienced contributors
> does not want to give
> an important positive review point without trial on real hardware.
>
> On the other hand what is the risk if you help to accept PSoC
On Tue, Feb 03, 2015 at 08:22:00AM +0100, Tomas Vanek wrote:
> BTW: If you don't know what is PSoC4: It is not "yet another small
> ARM MCU", Cypress integrated Cotex M0 core with PLD-based
> programmable logic. I really enjoyed working with the chip and
> programmable logic helped us a lot - we we
hi Spencer:
2015-02-03 17:58 GMT+08:00 Spencer Oliver :
> On 3 February 2015 at 07:55, vichy wrote:
>>
>> BTW, is it possible we did distcheck in the local instead of push to jenkins?
>> such as any script in tools can help me?
>>
>> appreciate your kind help,
>
> just running 'make distcheck' lo
On 3.2.2015 10:08, Andreas Fritiofson wrote:
On Tue, Feb 3, 2015 at 8:22 AM, Tomas Vanek
mailto:tom_...@users.sourceforge.net>>
wrote:
I contributed a NOR flash driver and config for PSoC 4 chip
family 5 months ago.
I did not mean it as a complaint. I was busy too, so I understa
Hi,
On Tue, Feb 03, 2015 at 09:39:34AM +0100, Tomas Vanek wrote:
> I started working with Kinetis MK22FN1M0VLL12
There's also an open issue regarding other Kinetis issue which is
related: http://sourceforge.net/p/openocd/tickets/73/ .
> Warn : 157 148158 kinetis.c:1261 kinetis_read_part_info():
On 3 February 2015 at 07:55, vichy wrote:
>
> BTW, is it possible we did distcheck in the local instead of push to jenkins?
> such as any script in tools can help me?
>
> appreciate your kind help,
just running 'make distcheck' locally will run the same tests as we do
on the server.
It is also wo
On Tue, Feb 3, 2015 at 8:22 AM, Tomas Vanek
wrote:
>
> I contributed a NOR flash driver and config for PSoC 4 chip family 5
> months ago.
>
> Both the flash driver and config does not influence any other code so it
> can not break anything.
>
We're usually don't demand as much for new drivers
Hi all,
I started working with Kinetis MK22FN1M0VLL12
According to reference manual this chip has FTFE with two 512kB flash
blocks nad 4kB sectors.
src/flash/nor/kinetis.c assigns granularity 3 for
KINETIS_K_SDID_K22_M120, what means:
pflash_sector_size_bytes = 4kB ...OK
unsigned num_b
18 matches
Mail list logo
