[ap-utils] SP918 dead

[Jan Rafaj]

On Thu, 20 Jan 2005, [ISO-8859-1] Joăo Seabra wrote:

> Ok.
>  Some more info.
>  The ARP trick doesnt work with the AP.
>  Its a Micronet SP 918 with no web management (SNMP only) and the
> firmware was (i believe) 1.4j.
>  ap-tftp is useless since i cant assign an ip to the AP.
>  The thing is dead and has no warranty.Any ideas?

Yes. It should be possible to program the flash memory in the device
through JTAG pins of AT76C510. I'm already able to successfully read
the entire memory image, but I still have no success in writing
the image back to flash. Should I succeed with this too, it would
be relatively easy - however, it would still require some little
SMD soldering skills, and building simple JTAG interface, which
you'd plug to the LPT port of your linux PC.
At this point I'm sorry to say that I cant promise anything.
I'm afraid there's no other way but to wait for my (or someone
elses) success with writing the image back.
I have several valid memory images that would apparently work in your
AP. I'll send you one once (if ever) I'll succeed, along with
instructions.

Please send me the FCC ID of SP918, so I can see whether its PCB
exposes JTAG directly...

Regards,

Jan

> On Thu, 20 Jan 2005 20:28:27 +0000, Joăo Seabra wrote:
>
> > Hi.
> >
> >  Thanks for your quick reply.
> >  The AP in question is a Micronet SP 918 and doesnt have any usb port.
> >  I Think it was using something like 1.4.j
> >  So Is there any way to make it work? Theres no firware available at
> > micronet page...
> >
> > On Thu, 20 Jan 2005 17:58:27 +0100 (MET), Jan Rafaj wrote:
> > >
> > > Hi Joăo,
> > >
> > > Please, download the latest ap-utils DEVELOPMENT version, and _READ_
> > > THOROUGHLY AND COMPLETELY:
> > > - the manpage for ap-tftp and
> > > - section relevant to 'free firmware upgrade' in README
> > >
> > > Your AP has suffered from 'dead by reconfiguration' bug due to bug
> > > in (almost all not current) generic ATMEL firmware versions.
> > > The way is to fix by firmware upgrade - and I'm quite sure your
> > > AP was running something like 0.2.2.X firmware version with X < 20 ....
> > >
> > > There's chance you could upgrade to 0.2.2.20 firmware, which is
> > > (finally!) not plaqued by this bug, and has ton of other extra
> > > features - please read the relevant section in the README as noted
> > > above.
> > >
> > > There's apparently no way of how to restore the AP at the moment,
> > > HOWEVER, if your AP has an USB port, and you'd be able to see
> > > something like 'Device with VID/PID 03eb/7611 connected' after
> > > plugging it to your linux box via USB port (provided that you
> > > have *hci.o module installed), then there _IS_ a chance your
> > > AP could be easily restored using so-called 'DFU' ('Device Firmware
> > > Upgrade standard') utility - I have an 'ap-dfu' (linux equivalent
> > > of windows 'DFU' USB utility used for firmware upgrade and
> > > conf. restores) in the works. At the moment, you could try AP restoral
> > > with the windows utility from your vendor. If you can't, you'll,
> > > unfortunately, have to wait until I finish ap-dfu.
> > >
> > > In case your device does not identify itself with VID/PID using USB
> > > connection, it is worse. I'm currently in process of trying onboard
> > > flash reprogramming with valid image through JTAG interface the AT76C510
> > > WiSOC provides, however there's been just partial success with this.
> > > So in this case, I'm afraid, rather than waiting for unsure to
> > > happen, you'd do better returning your AP to your seller for replacement.
> > > If you manage to get a new AP, DO NOT, BY ANY MEANS, FORGET TO UPGRADE
> > > IT TO A SAFE FIRMWARE 0.2.2.20 (provided that your AP qualifies for
> > > free firmware upgrade as described in README).
> > >
> > > Please post closer information about your AP:
> > > - FCC ID of your AP
> > > - firmware version you've used prior your attempt to upgrade firmware
> > > - version of firmware you've tried to upgrade with
> > > - whether your AP has provided web interface for configuration or not
> > >
> > > Thanks,
> > >
> > > Jan
> > > ap-utils co-developer
> > >
> > > On Thu, 20 Jan 2005, [ISO-8859-1] Joăo Seabra wrote:
> > >
> > > > Hi
> > > >
> > > >  Happy New Year :-)
> > > >
> > > >  I changed the primary port from ethernet to wireless while using the
> > > > ap in client mode and now its dead.
> > > >  No AP, doesnt reply to pings and the reset procedure described in the
> > > > micronet page does nothing.The ip configure doesnt work,etc...
> > > >
> > > >  Does anyone know how do i perform a full reset to the damn thing or
> > > > how do i solve my problem?
> > > >
> > > > thanks
> > > >
> > > > _______________________________________________
> > > > ap-utils mailing list
> > > > ap-utils at lists.polesye.net
> > > > http://lists.polesye.net/mailman/listinfo/ap-utils
> > > >
> > >
> > >
> >
>
> _______________________________________________
> ap-utils mailing list
> ap-utils at lists.polesye.net
> http://lists.polesye.net/mailman/listinfo/ap-utils