hardware question
Song, Stephen
Did you get the potato-flash utility to work?
With regard to the one Mesh Potato that is not responding to ping:
What firmware is installed on it? Does it give you dialtone when it
is powered on and a phone is plugged into it? Does the WiFi light
blink after it has powered up?
Regards... Steve
On 26 December 2011 22:30, Soumaila M Boukar <smbo...@gmail.com> wrote:
> hey how are doing, i think i have hardware problem. we have 4 mesh that
> working i can be able to ping them, when ping the one that has it wont ping.
> what should i do can some one help thank you
>
>
> On Fri, Dec 23, 2011 at 5:23 AM, Wayne Abroue <ple...@gmail.com> wrote:
>>
>> On Fri, Dec 23, 2011 at 11:49 AM, Song, Stephen <stephe...@gmail.com>
>> wrote:
>> > Hi Wayne,
>> >
>> > On 23 December 2011 11:42, Wayne Abroue <ple...@gmail.com> wrote:
>> >> On Fri, Dec 23, 2011 at 11:39 AM, Wayne Abroue <ple...@gmail.com>
>> >> wrote:
>> >>> I don't use potato flash,, But I notice from the screen shot there is
>> >>> no Valid ip detected from the VB.
>> >>> Did you try manually setting the eth0 IP address to 192.168.1.1?
>> >>>
>> >>> Wayne
>> >>>
>> >>
>> >> Do a : sudo ifconfig eth0 192.168.1.1
>> >> Then try again.
>> >
>> > AFAIK that shouldn't be necessary. The potato-flash utility uses
>> > libpcap which allows it to make its own IP assignments, which it seems
>> > to be doing successfully to judge by the terminal screen capture that
>> > Soumaila sent.
>> >
>>
>> Gotcha, I don't use P-flash at all so wouldnt be any wiser, TFTP /scp
>> has never failed me yet.
>>
>> Just noticed from the screen-shot it had assigned 1.0 to itself. But
>> I see this is normal.
>> Peer MAC: 00:09:45:58:1c:e7
>> Peer IP : 192.168.1.184
>> Your MAC: 00:ba:be:ca:ff:ee
>> Your IP : 192.168.1.0
>> Connecting to Redboot bootloader
>> WARNING: UNPLUGGING POWER WHILE FLASHING MIGHT DAMAGE THE BOOTLOADER
>> HOWEVER: IF YOU SEE NOTHING SHOWING UP BENEATH THIS LINE FOR MORE THAN
>> A MINUTE, START AGAIN...
>> A flash size of 8 MB was detected. rootfs(0x006a0000) +
>> kernel(0x00100000) + nvram(0x00000000) sums up to 0x007a0000 bytes
>> Setting IP address...
>> Initializing partitions...
>> Now uploading kernel...
>> Sending kernel, 1408 blocks...
>> Flashing kernel...
>> Loading rootfs...
>> Sending rootfs, 7424 blocks...
>> Flashing rootfs...
>> Flashing process completed...
>> Restarting device...
>>
>>
>>
>> W
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "village-telco-dev" group.
>> To post to this group, send email to village-...@googlegroups.com.
>> To unsubscribe from this group, send email to
>> village-telco-...@googlegroups.com.
>> For more options, visit this group at
>> http://groups.google.com/group/village-telco-dev?hl=en.
>>
>
> --
> You received this message because you are subscribed to the Google Groups
> "village-telco-dev" group.
> To post to this group, send email to village-...@googlegroups.com.
> To unsubscribe from this group, send email to
> village-telco-...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/village-telco-dev?hl=en.
--
Steve Song
http://manypossibilities.net
http://villagetelco.org
Soumaila M Boukar
Song, Stephen
The fact that that you get a power light and network light suggests
that the MP may still be ok. It seems more likely that the firmware
or the configuration has become corrupted. Are you able to
successfully re-flash the firmware on it?
Regards.... Steve
Soumaila M Boukar
thank you
Song, Stephen
It sounds very much like a failed firmware upgrade. Ultimately you
are going to want to be able to update the firmware on the MPs so I
suggest we try to solve this problem.
Can you try running potato-flash from an Ubuntu LiveCD as previously suggested?
Cheers... Steve
Abdoulaye Siby
I work with Soumaïla and I now have the mesh with me. We have tried
everything we could think of so far. Here is the current state of the
device:
1. When trying to flash it using the potato-flash program, it hang for
minutes, even hours without budging.
2. We have try the screen with all combination of boot sequences with
no success.
3. We have tried to get inside the device and flash it using RedBoot
(tftp, telnet, continuous pings ...). We can clearing see that after
powering up the device, the eth0 on192.168.1.20 comes on for about 5
seconds during which the pings are successful. However, the telnet
command to 192.168.1.20 on port 9000 fails silently. It simply hangs
without throwing.
I will do a last attempt using the serial daughter board that David
Rowe kindly sent to us (thanks David) and I will try to capture the
output and post it here. For that, I am simply waiting for the
USB2Serial adapter to be delivered (Serial ports have gone missing on
modern computer).
If we don't find the reason why this unit when zombie on us, then we
might ship it to who ever can give a better crack at this. We are
preparing to order a lot of units during 2012 and we think that
knowing what can cripple them like than is pretty neat.
Cheers guys, and happy new year 2012.
A. $iby
On Dec 28 2011, 1:46 am, "Song, Stephen" <stephen.s...@gmail.com>
wrote:
> HiSoumaila,
> It sounds very much like a failed firmware upgrade. Ultimately you
> are going to want to be able to update the firmware on the MPs so I
> suggest we try to solve this problem.
>
>
> Cheers... Steve
> On 28 December 2011 08:25,SoumailaM Boukar <smbou...@gmail.com> wrote:
>
>
>
>
>
>
>
>
>
> > the has the firmware 273 i try to update to firmware 287, the problem start
> > from there, i had 3 MP at that time the other 2 works but one didnt. i dont
> > know what to do.
>
> > thank you
>
> > wrote:
>
> >> HiSoumaila,
> >> The fact that that you get a power light and network light suggests
> >> that the MP may still be ok. It seems more likely that the firmware
> >> or the configuration has become corrupted. Are you able to
>
> >> Regards.... Steve
> >> On 27 December 2011 22:48,SoumailaM Boukar <smbou...@gmail.com> wrote:
> >> > Hi Steve how are you doing, the mesh doent do anything can't ping, no
> >> > dial
> >> > tone, no light blinking. only power light is on and when connect the
> >> > netwok
> >> > cable the coming on. and thank you we got the 4 mesh you ship to us.
>
> >> > wrote:
>
> >> >> HiSoumaila,
>
> >> >> Did you get the potato-flashutility to work?
> >> >> With regard to the one Mesh Potato that is not responding to ping:
> >> >> What firmware is installed on it? Does it give you dialtone when it
> >> >> is powered on and a phone is plugged into it? Does the WiFi light
> >> >> blink after it has powered up?
>
> >> >> Regards... Steve
>
> >> >> > hey how are doing, i think i have hardware problem. we have 4 mesh
> >> >> > that
> >> >> > working i can be able to ping them, when ping the one that has it
> >> >> > wont
> >> >> > ping.
> >> >> > what should i do can some one help thank you
>
>
> >> >> >> On Fri, Dec 23, 2011 at 11:49 AM, Song, Stephen
> >> >> >> wrote:
> >> >> >> > Hi Wayne,
> >> >> >> > On 23 December 2011 11:42, Wayne Abroue <plet...@gmail.com> wrote:
> >> >> >> >> On Fri, Dec 23, 2011 at 11:39 AM, Wayne Abroue
> >> >> >> >> wrote:
> >> >> >> >>> I don't use potatoflash,, But I notice from the screen shot
> >> >> >> >>> is
> >> >> >> >>> no Valid ip detected from the VB.
> >> >> >> >>> Did you try manually setting the eth0 IP address to 192.168.1.1?
>
> >> >> >> >>> Wayne
>
> >> >> >> >> Do a : sudo ifconfig eth0 192.168.1.1
> >> >> >> >> Then try again.
>
> >> >> >> > seems
> >> >> >> > to be doing successfully to judge by the terminal screen capture
> >> >> >> > that
> >> >> >> >Soumailasent.
>
> >> >> >> has never failed me yet.
>
> >> >> >> Just noticed from the screen-shot it had assigned 1.0 to itself.
> >> >> >> But
> >> >> >> I see this is normal.
> >> >> >> Peer MAC: 00:09:45:58:1c:e7
> >> >> >> Peer IP : 192.168.1.184
> >> >> >> Your MAC: 00:ba:be:ca:ff:ee
> >> >> >> Your IP : 192.168.1.0
> >> >> >> Connecting to Redboot bootloader
> >> >> >> WARNING: UNPLUGGING POWER WHILE FLASHING MIGHT DAMAGE THE BOOTLOADER
> >> >> >> HOWEVER: IF YOU SEE NOTHING SHOWING UP BENEATH THIS LINE FOR MORE
> >> >> >> THAN
> >> >> >> A MINUTE, START AGAIN...
Abdoulaye Siby
I work with Soumaïla and I now have the mesh with me. We have tried
everything we could think of so far. Here is the current state of the
device:
2. We have try the screen with all combination of boot sequences with
no success.
3. We have tried to get inside the device and flash it using RedBoot
powering up the device, the eth0 (configured with 192.168.1.20) comes
the telnet command to 192.168.1.20 on port 9000 fails silently. It
I will do a last attempt using the serial daughter board that David
USB2Serial adapter to be delivered (Serial ports have gone missing on
modern computer).
might ship it to someone who can give a better crack at this. When
that time comes, we will look for volunteers. We are preparing to
order lots of units during 2012 and we think that knowing what can
cripple them like that is pretty neat.
Elektra (Open-mesh.net)
Hi -
>1. When trying to flash it using the potato-flash program, it hangs
>for minutes, even hours without budging.
does potato-flash start to flash, or does it hang at the point where it says that if it hangs at this point for a minute you should restart the process?
If it always hangs at this point, try another laptop or workstation. Do not use a switch. I had a problem with a Gigabit Ethernet port once.
>3. We have tried to get inside the device and flash it using RedBoot
>(tftp, telnet, continuous pings ...). We could clearly see that after
>powering up the device, the eth0 (configured with 192.168.1.20) comes
>on for about 5 seconds during which the pings are successful. However,
>the telnet command to 192.168.1.20 on port 9000 fails silently. It
>simply hangs without throwing any clue.
Please use putty, it is available for most platforms. Configure putty to use telnet 192.168.1.20 port 9000. You need to hit the connect button as soon as you see the first ping.
Serial is the best way to debug and a last resort.
Cheers,
Elektra
Abdoulaye Siby
> does potato-flash start to flash, or does it hang at the point where it says that if it hangs at this point for a minute you should restart the process?
Gigabit Ethernet Port, the same laptop was able to successfully flash
four (4) other Mesh Potatoes that we have recently purchased (using
the same potato-flash utility). We tried it already from different
computers, but all of them are using Gigabit Ethernet Ports. During
all the tests, we have been using laptop PCs running Ubuntu from a USB
stick. But for the redboot attempts, we have used Mac, Windows, and
Ubuntu Linux with no success.
> Please use putty, it is available for most platforms. Configure putty to use telnet 192.168.1.20 port 9000. You need to hit the connect button as soon as you see the first ping.
We use it on Mac and Windows.
A. $iby
On Jan 4, 2:59 am, "Elektra (Open-mesh.net)" <onelek...@gmx.net>
wrote:
elektra
> Yes. It does hang at that point. However, although it was with a
> Gigabit Ethernet Port, the same laptop was able to successfully flash
> four (4) other Mesh Potatoes that we have recently purchased (using
> the same potato-flash utility). We tried it already from different
> computers, but all of them are using Gigabit Ethernet Ports. During
> all the tests, we have been using laptop PCs running Ubuntu from a USB
> stick. But for the redboot attempts, we have used Mac, Windows, and
> Ubuntu Linux with no success.
is the MP you are having trouble with from a different production run? The MP I had trouble with in combination with a Gigabit port was from the very first production run that came in the plastic outdoor boxes. Switching to a different LAN port (I used a 100Mbit USB-Ethernet dongle) fixed the problem for me.
Cheers,
Elektra
Abdoulaye Siby
very first production run. It has the firmware rv233. I will find an
older computer or a USB Ethernet port that will provide a less then
Gigabit Ethernet and I will post the result here. After a successful
flash, do you think that I will be able to use it with Gigabit
Ethernet Port?
A. $iby
Song, Stephen
Yes. I believe that the mesh I am having trouble with is also from the
very first production run. It has the firmware rv233. I will find an
older computer or a USB Ethernet port that will provide a less then
Gigabit Ethernet and I will post the result here. After a successful
flash, do you think that I will be able to use it with Gigabit
Ethernet Port?
A. $iby
On Jan 4, 11:13 am, elektra <onelek...@gmx.net> wrote:
> Hi -
>
> > Yes. It does hang at that point. However, although it was with a
> > Gigabit Ethernet Port, the same laptop was able to successfully flash
> > four (4) other Mesh Potatoes that we have recently purchased (using
> > the same potato-flash utility). We tried it already from different
> > computers, but all of them are using Gigabit Ethernet Ports. During
> > all the tests, we have been using laptop PCs running Ubuntu from a USB
> > stick. But for the redboot attempts, we have used Mac, Windows, and
> > Ubuntu Linux with no success.
>
> is the MP you are having trouble with from a different production run? The MP I had trouble with in combination with a Gigabit port was from the very first production run that came in the plastic outdoor boxes. Switching to a different LAN port (I used a 100Mbit USB-Ethernet dongle) fixed the problem for me.
>
> Cheers,
> Elektra
--
You received this message because you are subscribed to the Google Groups "village-telco-dev" group.
To post to this group, send email to village-...@googlegroups.com.
To unsubscribe from this group, send email to village-telco-...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/village-telco-dev?hl=en.
elektra
it might be a incompatibility with Gigabit Ethernet in combination with the bootloader and the Ethernet transceiver chip in the first batch of the outdoor MP units. Other than with the flashing, I have no compatibility issues whatsoever. So after it is flashed, all should be fine. Gigabit Ethernet uses all 8 pins of the Ethernet port, while the MP uses 4 pins for 100 Mbit Ethernet and 4 pins for PoE. The problem might be related to the fact that the potato-flash tool uses raw access to the media. Maybe autodetection does not work properly or broadcasts are sent too fast.
Maybe forcing the Ethernet port of your workstation to use 10Mbit or 100Mbit solves the issue.
There is a configuration tool for Ethernet ports, called ethtool. Maybe you can give this a try. I have not tested it myself yet.
As an example, this will switch eth0 to half-duplex mode:
ethtool --change eth0 duplex half
ethtool --change eth0 speed XXX
ethtool --change eth0 autoneg off
I am not sure whether all drivers support tweaking with the utility.
Cheers,
Elektra
Abdoulaye Siby
I will give it a shot.
Cheers
A. $iby
Abdoulaye Siby
I haven't been able to try flashing the Mesh from another computer.
However, I got myself the usb serial port adapter and it seems to be
working like a charm on a Mac. I used it for observing the mesh at
work using simply:
# cat /dev/tty.usbserial
And here is the result:
------------- Begin
Ethernet eth0: MAC address 00:09:45:58:e6:3d
IP: 192.168.1.20/255.255.255.0, Gateway: 192.168.1.1
Default server: 192.168.1.1
RedBoot(tm) bootstrap and debug environment [ROMRAM]
Non-certified release, version v1.3.0 - built 14:07:19, Jun 9 2009
Copyright (C) 2000, 2001, 2002, 2003, 2004 Red Hat, Inc.
Board: ap61
RAM: 0x80000000-0x81000000, [0x8003dd50-0x80fe1000] available
FLASH: 0xa8000000 - 0xa87e0000, 128 blocks of 0x00010000 bytes each.
== Executing boot script in 5.000 seconds - enter ^C to abort
RedBoot> fis load -l vmlinux.bin.l7
Image loaded from 0x80041000-0x80253086
RedBoot> exec
Now booting linux kernel:
Base address 0x80030000 Entry 0x80041000
Cmdline :
------------- End
My knowledge about RedBoot is limited. So I am not sure if Cmdline
means that the Mesh is waiting for an input or not. In any case, it is
hanging there forever.
I will use telnet and try to flash it.
Cheers
A. $iby
Abdoulaye Siby
Elektra (Open-mesh.net)
this is normal behaviour. The MP is using the serial port for sending/receiving audio data from the telephone port. Hence there is no serial console as soon as the Linux kernel takes over, because the serial port driver is not compiled in. This would cause a conflict when loading the FXS port driver.
You can now stop the boot loader from executing the boot script by hitting CTRL+C and use the serial console to control manual flashing via tftp, as described in the wiki:
http://wiki.villagetelco.org/index.php?title=Mesh_Potato_HOWTOs#Reflash_the_firmware_from_RedBoot
Cheers,
Elektra
--
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.
Abdoulaye Siby
successfully brought the Mesh Potato unit back to life. It seems to be
working well now. Although it took two or three attempts (after the
flashing procedure) before it could boot up properly.
We have notice something that could make it very difficult to use the
serial port. When using the serial port, if you make a typo, there is
no point correcting it by using the <Delete> or the <Backspace> key on
the keyboard. That will only correct the visual aspect of the command.
As a result, after pressing <ENTER>, the command will fail. We were
having that problem because we didn't have the luxury of being able to
paste something in the serial console. You basically have two solution
for that:
1. Get a serial console software that lets you copy a text from
somewhere else and paste it in the console.
2. Be very careful and avoid making typos.
Also, get the serial console to connect to the mesh about 1 or 2
seconds after powering it up. We have noticed that trying to connect
it long before turning the MP on will not give any result. The console
will stay empty throughout the boot up process.
If you are pinging continously the the MP and you see that the pings
are successful, than it is too late for the serial port. At that
point, turn the MP off, and than back on and try again.
We used the revision 287 of the MP firmware.
Thanks again.
Cheers
A. Siby
On Jan 7, 6:33 am, "Elektra (Open-mesh.net)" <onelek...@gmx.net>
wrote:
>
> this is normal behaviour. The MP is using the serial port for sending/receiving audio data from the telephone port. Hence there is no serial console as soon as the Linux kernel takes over, because the serial port driver is not compiled in. This would cause a conflict when loading the FXS port driver.
>
> You can now stop the boot loader from executing the boot script by hitting CTRL+C and use the serial console to control manual flashing via tftp, as described in the wiki:
>
Song, Stephen
Cheers... Steve