The kw port now supports the Guruplug Server Plus, including both Ethernet interfaces, and probably the other Guruplugs. booting(8) now has the necessary instructions to get started. They are more diverse than one might like because every version of u-boot we get for a new board seems to have had the dhcp, bootp and tftp commands tinkered with to behave slightly differently. We have two Guruplugs and one has been stable but the other is prone to random resets (and runs much warmer than the Sheevaplugs). I'd be interested in hearing from anyone else who sees random resets.
I've imported the flash memory support from native Inferno, other than the flash translation layer, which was developed for nor flash and is suspect with nand flash. flash(3) describes the interface. It seems to work on the Kirkwood boards, but I haven't exercised it extensively. It does implement software ECC. /dev/flash looks like it always returns zero bytes on the igepv2 board, but lack of documentation makes it a little hard to tell what to expect.
>the flash translation layer, which was developed for nor flash and is >suspect with nand flash
it's not "suspect" as such: just not implemented because it's the wrong approach. FTL's design assumes you can rewrite a word, flipping bits off (but never on), to change a physical/logical map efficiently. fine with NOR, it allows that easily. drivers for NAND would need to do something more costly to emulate that effect, because the granularity is much larger, and the organisation and rules generally are different. i don't think they bother (because it's not a good idea) so it probably wouldn't work.
> The kw port now supports the Guruplug Server Plus, including both > Ethernet interfaces, and probably the other Guruplugs. booting(8) now > has the necessary instructions to get started. They are more diverse > than one might like because every version of u-boot we get for a new > board seems to have had the dhcp, bootp and tftp commands tinkered > with to behave slightly differently. We have two Guruplugs and one > has been stable but the other is prone to random resets (and runs much > warmer than the Sheevaplugs). I'd be interested in hearing from > anyone else who sees random resets.
> I've imported the flash memory support from native Inferno, other than > the flash translation layer, which was developed for nor flash and is > suspect with nand flash. flash(3) describes the interface. It seems > to work on the Kirkwood boards, but I haven't exercised it > extensively. It does implement software ECC. /dev/flash looks like > it always returns zero bytes on the igepv2 board, but lack of > documentation makes it a little hard to tell what to expect.
the two guruplugs i had ordered arrived today. i was disappoint to find that i'll need to order the JTAG board before i can do anything. i didn't see this requirement when i ordered them over a month ago. did anyone else miss this?
> The kw port now supports the Guruplug Server Plus, including both > Ethernet interfaces, and probably the other Guruplugs. booting(8) now > has the necessary instructions to get started. They are more diverse > than one might like because every version of u-boot we get for a new > board seems to have had the dhcp, bootp and tftp commands tinkered > with to behave slightly differently. We have two Guruplugs and one > has been stable but the other is prone to random resets (and runs much > warmer than the Sheevaplugs). I'd be interested in hearing from > anyone else who sees random resets.
> I've imported the flash memory support from native Inferno, other than > the flash translation layer, which was developed for nor flash and is > suspect with nand flash. flash(3) describes the interface. It seems > to work on the Kirkwood boards, but I haven't exercised it > extensively. It does implement software ECC. /dev/flash looks like > it always returns zero bytes on the igepv2 board, but lack of > documentation makes it a little hard to tell what to expect.
On Thu, May 13, 2010 at 9:48 AM, Skip Tavakkolian <9...@9netics.com> wrote: > thank you!
> the two guruplugs i had ordered arrived today. i was disappoint to > find that i'll need to order the JTAG board before i can do anything. > i didn't see this requirement when i ordered them over a month ago. > did anyone else miss this?
> > The kw port now supports the Guruplug Server Plus, including both > > Ethernet interfaces, and probably the other Guruplugs. booting(8) now > > has the necessary instructions to get started. They are more diverse > > than one might like because every version of u-boot we get for a new > > board seems to have had the dhcp, bootp and tftp commands tinkered > > with to behave slightly differently. We have two Guruplugs and one > > has been stable but the other is prone to random resets (and runs much > > warmer than the Sheevaplugs). I'd be interested in hearing from > > anyone else who sees random resets.
> > I've imported the flash memory support from native Inferno, other than > > the flash translation layer, which was developed for nor flash and is > > suspect with nand flash. flash(3) describes the interface. It seems > > to work on the Kirkwood boards, but I haven't exercised it > > extensively. It does implement software ECC. /dev/flash looks like > > it always returns zero bytes on the igepv2 board, but lack of > > documentation makes it a little hard to tell what to expect.
> the two guruplugs i had ordered arrived today. i was disappoint to > find that i'll need to order the JTAG board before i can do anything. > i didn't see this requirement when i ordered them over a month ago. > did anyone else miss this?
>> The kw port now supports the Guruplug Server Plus, including both >> Ethernet interfaces, and probably the other Guruplugs. booting(8) >> now >> has the necessary instructions to get started. They are more diverse >> than one might like because every version of u-boot we get for a new >> board seems to have had the dhcp, bootp and tftp commands tinkered >> with to behave slightly differently. We have two Guruplugs and one >> has been stable but the other is prone to random resets (and runs >> much >> warmer than the Sheevaplugs). I'd be interested in hearing from >> anyone else who sees random resets.
>> I've imported the flash memory support from native Inferno, other >> than >> the flash translation layer, which was developed for nor flash and is >> suspect with nand flash. flash(3) describes the interface. It seems >> to work on the Kirkwood boards, but I haven't exercised it >> extensively. It does implement software ECC. /dev/flash looks like >> it always returns zero bytes on the igepv2 board, but lack of >> documentation makes it a little hard to tell what to expect.
On Thu, May 13, 2010 at 12:30 PM, Gorka Guardiola <pau...@gmail.com> wrote: > In the sheeva you can access the Jtag through the usb port...
> - > Curiosity sKilled the cat
> G.
> On May 13, 2010, at 6:48 PM, Skip Tavakkolian <9...@9netics.com> wrote:
> thank you!
>> the two guruplugs i had ordered arrived today. i was disappoint to >> find that i'll need to order the JTAG board before i can do anything. >> i didn't see this requirement when i ordered them over a month ago. >> did anyone else miss this?
>> The kw port now supports the Guruplug Server Plus, including both >>> Ethernet interfaces, and probably the other Guruplugs. booting(8) now >>> has the necessary instructions to get started. They are more diverse >>> than one might like because every version of u-boot we get for a new >>> board seems to have had the dhcp, bootp and tftp commands tinkered >>> with to behave slightly differently. We have two Guruplugs and one >>> has been stable but the other is prone to random resets (and runs much >>> warmer than the Sheevaplugs). I'd be interested in hearing from >>> anyone else who sees random resets.
>>> I've imported the flash memory support from native Inferno, other than >>> the flash translation layer, which was developed for nor flash and is >>> suspect with nand flash. flash(3) describes the interface. It seems >>> to work on the Kirkwood boards, but I haven't exercised it >>> extensively. It does implement software ECC. /dev/flash looks like >>> it always returns zero bytes on the igepv2 board, but lack of >>> documentation makes it a little hard to tell what to expect.
> In the sheeva you can access the Jtag through the usb port...
but the (newer) guruplug does not. it requires the "guruplug jtag board", for accessing the console and they don't make it obvious when you order the guruplug.
On Thu, May 13, 2010 at 1:56 PM, Skip Tavakkolian <9...@9netics.com> wrote: > > In the sheeva you can access the Jtag through the usb port...
> but the (newer) guruplug does not. it requires the "guruplug jtag > board", for accessing the console and they don't make it obvious when > you order the guruplug.
> They actually list the miniusb on the side is the JTAG port on their
>> > In the sheeva you can access the Jtag through the usb port...
>> but the (newer) guruplug does not. it requires the "guruplug jtag >> board", for accessing the console and they don't make it obvious when >> you order the guruplug.
>> They actually list the miniusb on the side is the JTAG port on their > website. Are you saying that doesn't work?
> on the guruplug there's no miniusb for the console; it's jtag and > you'll need the appropriately named "guruplug jtag board".
> >> > In the sheeva you can access the Jtag through the usb port...
> >> but the (newer) guruplug does not. it requires the "guruplug jtag > >> board", for accessing the console and they don't make it obvious when > >> you order the guruplug.
> >> They actually list the miniusb on the side is the JTAG port on their > > website. Are you saying that doesn't work?
