Reply
New Member
Posts: 11
Registered: ‎08-25-2014

Re: NOW THE LOCO IS ALIVE !!!!

Thanks Acidu it really helped a lot . Man Happy

Regular Member
Posts: 345
Registered: ‎12-17-2009
Kudos: 34

Re: ns loco m2 lost his WLAN MAC and how to repair a bad flash memory nano station loco m2

Good luck then resurecting your devices ! Man Happy
Senior Member
Posts: 2,569
Registered: ‎03-23-2008
Kudos: 515
Solutions: 18

Re: ns loco m2 lost his WLAN MAC and how to repair a bad flash memory nano station loco m2

Good work acidu !!!  I love people that can do this! ThumbsupThumbsupThumbsup

Best Regards ... Joe

If the communication industry had been built on the backs of yes-men,
we would be submitting our forum posts at the telegraph office in town.
Regular Member
Posts: 345
Registered: ‎12-17-2009
Kudos: 34

Re: ns loco m2 lost his WLAN MAC and how to repair a bad flash memory nano station loco m2

[ Edited ]

yeah... THX... only Dave-D does not like this...because he has tones of money buying dirty-cheap new devices all the time!... nice for him... so..... let`s ALL move to north america where dirty-cheap devices grow up in trees.

New Member
Posts: 16
Registered: ‎09-25-2013
Kudos: 1
Solutions: 1

Re: NOW THE LOCO IS ALIVE !!!!

[ Edited ]

Hi Acidu,

 

Thanks for sharing your information to the forum.

 

I am sure someone out there who likes to have a go on resurrecting their faulty NLM2

will be delighted to find this post!Icon Razz

 

Anyway, wow! Icon Smile, I thought your post never got finished

after not hearing from you for almost a year (since 2013)......

 

As for my faulty unit, I managed to upload the firmware(using recovery method) and

got everything back to normal, but...but...my unit is still in the cabinet...doing absolute

nothing at all.

 

If I do find time, I will test it again, and this time using a CAT6 STP cable with metal

network plugs for proper grounding. Previously there is no grounding since I was using

normal plastic see-through network plugs. But I cannot be very confident that this

problem will not occur again. After reading your post, most likely the problem is the

ACTUAL nand flash chip itself (not very reliable). But correct me if I am wrong, how

many times, can you actually flash the chip. I believe the more you flash it whenever

the problem arise, the more likely it will wear out the memory cells in the chip, right???Confused

 

My question is, how do manage to find out your faulty units's MAC address when

it is faulty and no way of accessing it? (You need a unique MAC address for every

networking device)

 

Or  did you make up a new MAC address (just a random HEX address) on your own?

 

Thank you.

 

Senior Member
Posts: 2,569
Registered: ‎03-23-2008
Kudos: 515
Solutions: 18

Re: ns loco m2 lost his WLAN MAC and how to repair a bad flash memory nano station loco m2

Well, if it's not too old and worn, I guess you could read it off of the label on the case?

Best Regards ... Joe

If the communication industry had been built on the backs of yes-men,
we would be submitting our forum posts at the telegraph office in town.
New Member
Posts: 16
Registered: ‎09-25-2013
Kudos: 1
Solutions: 1

Re: ns loco m2 lost his WLAN MAC and how to repair a bad flash memory nano station loco m2

 

Hi JustJoe,

 

My label on the unit is = 1237TDC9FDB183864

 

So the MAC address  of my unit is actually derive = DC-9F-DB-18-38-64 (12 digits)?

Right?Confused5

 

So lesson learnt here.....always keep your the label of MAC address intact

 

Does any of old Ubuiquiti models suffer the same problem as the NSLM2? What about the NSM2?

Senior Member
Posts: 2,569
Registered: ‎03-23-2008
Kudos: 515
Solutions: 18

Re: ns loco m2 lost his WLAN MAC and how to repair a bad flash memory nano station loco m2

Yes, that is exactly correct on the MAC. 

The previous 5 characters are the manufacturing date code.  I remember that the 12 indicates year as in 2012, I don't remember the exact format of the other 3.

 

I can't answer about the NSM2, acidu may have worked on those?

Best Regards ... Joe

If the communication industry had been built on the backs of yes-men,
we would be submitting our forum posts at the telegraph office in town.
Regular Member
Posts: 345
Registered: ‎12-17-2009
Kudos: 34

Re: ns loco m2 lost his WLAN MAC and how to repair a bad flash memory nano station loco m2

[ Edited ]

even if the unit is dead or not booting corectly or not booting at all you can still find the mac insite the flash, there is a section in flash called eeprom that starts someware offser 007F0000 ... nice choice UBI for that... double O seven Man Happy) where there is no writing, only once i think, at the factory, even if you flash it in a normal way...when it worked, it will not touch that section of eeprom where manufacture calibration data is stored...like mac-s, and yes....you can read the labels, you will still have a label inside on the ram chip with the mac, i did not try to put other mac-s, i will try and see what happens Man Happy)

Regular Member
Posts: 345
Registered: ‎12-17-2009
Kudos: 34

Re: ns loco m2 lost his WLAN MAC and how to repair a bad flash memory nano station loco m2

[ Edited ]

I resurected allso airgrid m2 hp...it had a winbound chip....and change it with a mx chip, but in this case i get counterfaith device, and i have tryed older fws untill version 5.5 worked ok and I am happy that it works,

 

 

 

do not know theyer method of detecting, if someone knows it PM me, but I doubt that someone will tell me that so again I will have to discover it myself someday, even with this job no one helped me around here, only Dave was ``smashing his stick in a puddle of mud- bored``, and that`s why you did not saw any post since 2013 Man Happy

 

 

I did find this https://dev.wlan-si.net/ticket/1101 witch is 13 months or more old and helped me allot.

 

W25Q64CV Flash chip. Memory layout:

256k(u-boot) 0x000000000000-0x000000040000
64k(u-boot-env)0x000000040000-0x000000050000
1024k(kernel) 0x000000050000-0x000000150000
6528k(rootfs) 0x000000150000-0x0000007b0000
256k(cfg) 0x0000007b0000-0x0000007f0000
64k(EEPROM) 0x0000007f0000-0x000000800000

Regular Member
Posts: 345
Registered: ‎12-17-2009
Kudos: 34

Re: ns loco m2 lost his WLAN MAC and how to repair a bad flash memory nano station loco m2

I do not know the manufacture rating of writings on a mx or winbound chip, they may or may not be affected by many flashings...but one thing is for sure, they have really cheap flash nands inside so if you have time it worth trying to resurect it. Did not tryed nsm2 yet but i think is the same structure inside the chip. I have a unifi outdoor ap with dead bootloader from a friend to repair, died after a fw upgrade, died so bad that bootloader is gone so no comm on jtag, useless jtag if the device is dead, i have to find now a working unifi outdoor ap to copy only the bootloader or maybe the whole flash and try to resurect the other one.
Can someone tell me if the uboot is same on unifi like the uboot found on ns?
New Member
Posts: 16
Registered: ‎09-25-2013
Kudos: 1
Solutions: 1

Re: ns loco m2 lost his WLAN MAC and how to repair a bad flash memory nano station loco m2

[ Edited ]

Phew.....I am lucky that I only bought 2 units of NSLM2 for testing.

I bought it because, I want to test out the real power of AIRMAX technology.

and compare to other brand the price was the cheapest and affordable.

 

I am glad that I committed to test the durability of NSLM2 for over a year or so.

Just to find out whether it is built to LAST. But sadly, it did not, Ubiquiti used to build

durable products when 802.11g was around, but no more.Nonod

 

Now that I know there is problem with the Winbound NAND flash chip, my project has come to a halt.

I am definitely staying away from the Ubiquiti products for some period time, and make a switch to Mikrotik instead.

Regular Member
Posts: 345
Registered: ‎12-17-2009
Kudos: 34

Re: ns loco m2 lost his WLAN MAC and how to repair a bad flash memory nano station loco m2

[ Edited ]

I`m allso in a process to change all the ubiquiti devices from a small village with mikrotik SXT...so far so good...I did achive like 50Mbps down speed at 3km with SXT and only on one polarisation, migration is slow because I have to take down all ubi equipment and SELL IT like secound hand.

 

like I saw... sxt uses toshiba flash chip   http://www.cdr.pl/galerie/r/routerboard-sxt-lite2-ou_2871.jpg   ....and that, to me... is a PLUS+++

 

I had bullets there... in more than 3 years only one or two bullets died... but not completely... LAN dead... changed the KENDIN chip and voila... so yes... 802.11b/g devices from ubi were more into fiability...but low performance, now we have better performance with low fiability...so yes... MONEY is INVOLVED.. cutting production cost, choosing cheaper and cheaper parts. not saying that mikrotik SXT are more reliable in time because I don`t know.. time will tell, but I have mikrotik boards working non-stop for more than 6 years... so...

New Member
Posts: 11
Registered: ‎08-25-2014

Re: ns loco m2 lost his WLAN MAC and how to repair a bad flash memory nano station loco m2

[ Edited ]

Can you refer a cheap adapter to program mx25l3206emi Serial Flash , it's $80 on the website Man Tongue . Hoping for a cheap alternative . Man Happy

 

I have Tl866cs . Just need the adaptor .

Regular Member
Posts: 345
Registered: ‎12-17-2009
Kudos: 34

Re: ns loco m2 lost his WLAN MAC and how to repair a bad flash memory nano station loco m2

New Member
Posts: 11
Registered: ‎08-25-2014

Re: ns loco m2 lost his WLAN MAC and how to repair a bad flash memory nano station loco m2

Thanks Brotha , got the adaptor from local shop Man Happy . Do you have Nanostation2 Loco flash memory Backup ? . If yes them please share it with me Smile5 , i dont have a spare device to copy the backup !

Regular Member
Posts: 345
Registered: ‎12-17-2009
Kudos: 34

Re: ns loco m2 lost his WLAN MAC and how to repair a bad flash memory nano station loco m2

Look back on my post from 19 aug, you"ll find it there
New Member
Posts: 1
Registered: ‎11-22-2012

Re: NOW THE LOCO IS ALIVE !!!!

acidu, you are excellent engineer!

 

Thank you very much for sharing this information. Your posts are extremely helpful, informative and give value to this forum.

 

I have 6 PowerBridge M5 (rocket5 logic board). 450-600 days uptime each.

Yesterday one of them refused to upgrade to XM.v5.5.8.20991.140205.1824

After 20+ TFTP attempts here what's going on:

U-Boot 1.1.4.2-s550 (Feb  9 2012 - 17:16:25)

Board: Ubiquiti Networks XM board (rev 1.0 e1a5)
DRAM:  64 MB
Flash:  8 MB
Net:   eth0, eth1
Hit any key to stop autoboot:  0
## Booting image at 9f050000 ...
   Image Name:   MIPS Ubiquiti Linux-2.6.32.54
   Created:      2012-04-06  11:56:34 UTC
   Image Type:   MIPS Linux Kernel Image (lzma compressed)
   Data Size:    1047143 Bytes = 1022.6 kB
   Load Address: 80002000
   Entry Point:  80002000
   Verifying Checksum ... Bad Data CRC
ar7240>
ar7240>
ar7240> help
?       - alias for 'help'
base    - print or set address offset
boot    - boot default, i.e., run 'bootcmd'
bootd   - boot default, i.e., run 'bootcmd'
bootelf - Boot from an ELF image in memory
bootm   - boot application image from memory
cmp     - memory compare
cp      - memory copy
crc32   - checksum calculation
echo    - echo args to console
erase   - erase FLASH memory
flinfo  - print FLASH memory information
go      - start application at address 'addr'
help    - print online help
iminfo  - print header information for application image
imls    - list all images found in flash
loop    - infinite loop on address range
md      - memory display
mii     - MII utility commands
mm      - memory modify (auto-incrementing)
mtdparts- define flash/nand partitions
mtest   - simple RAM test
mw      - memory write (fill)
nm      - memory modify (constant address)
ping    - send ICMP ECHO_REQUEST to network host
printenv- print environment variables
protect - enable or disable FLASH write protection
autoscr - run script from memory
reset   - Perform RESET of the CPU
run     - run commands in an environment variable
saveenv - save environment variables to persistent storage
setenv  - set environment variables
sleep   - delay execution for some time
tftpboot- boot image via network using TFTP protocol
urescue - start TFTP server and wait for firmware
version - print monitor version
ar7240> urescue
Setting default IP 192.168.1.20
Starting TFTP server...
Using eth0 (192.168.1.20), address: 0x81000000
Waiting for connection: |
Receiving file from 192.168.1.1:58034
Received 6896830 bytes
Firmware Version: XM.ar7240.v5.5.8.20991.140205.1824
Setting U-Boot environment variables
Un-Protected 1 sectors
Erasing Flash.... done
Erased 1 sectors
Writing to Flash... done
Protected 1 sectors
Will not overwrite u-boot partition! Skipped.
Copying partition 'kernel' to flash memory:
        erasing range 0x9F050000..0x9F14FFFF: ................ done
Erased 16 sectors
        writing to address 0x9f050000, length 0x00100000 ...
Copying partition 'rootfs' to flash memory:
        erasing range 0x9F150000..0x9F6AFFFF: ..................................                             .................................................... done
Erased 86 sectors
        writing to address 0x9f150000, length 0x00560000 ...

Firmware update complete.

Resetting...

U-Boot 1.1.4.2-s550 (Feb  9 2012 - 17:16:25)

Board: Ubiquiti Networks XM board (rev 1.0 e1a5)
DRAM:  64 MB
Flash:  8 MB
Net:   eth0, eth1
Hit any key to stop autoboot:  0
## Booting image at 9f050000 ...
   Image Name:   MIPS Ubiquiti Linux-2.6.32.54
   Created:      2014-02-05  16:25:36 UTC
   Image Type:   MIPS Linux Kernel Image (lzma compressed)
   Data Size:    1047649 Bytes = 1023.1 kB
   Load Address: 80002000
   Entry Point:  80002000
   Verifying Checksum ... Bad Data CRC
ar7240>

ar7240> imls
Image at 9F050000:
   Image Name:   MIPS Ubiquiti Linux-2.6.32.54
   Created:      2014-02-05  16:25:36 UTC
   Image Type:   MIPS Linux Kernel Image (lzma compressed)
   Data Size:    1047649 Bytes = 1023.1 kB
   Load Address: 80002000
   Entry Point:  80002000
   Verifying Checksum ...    Bad Data CRC
OK
ar7240> mtdparts

device nor0 , # parts = 6
 #: name                        size            offset          mask_flags
 0: u-boot                      0x00040000      0x00000000      0
 1: u-boot-env                  0x00010000      0x00040000      0
 2: kernel                      0x00100000      0x00050000      0
 3: rootfs                      0x00660000      0x00150000      0
 4: cfg                         0x00040000      0x007b0000      0
 5: EEPROM                      0x00010000      0x007f0000      0

active partition: nor0,0 - (u-boot) 0x00040000 @ 0x00000000

defaults:
mtdids  : nor0=ar7240-nor0
mtdparts: mtdparts=ar7240-nor0:256k(u-boot),64k(u-boot-env),1024k(kernel),6528k(rootfs),256k(cfg),64k(EEPROM)

 

No need to say that 20+ failures to tftp new firmware means flash is bad.

From what I see bootloader area is ok.

Is there is a way to save it to tftp server prior to desoldering?

Can you help with instructions if yes?

 

Thank you in advance.

BR,

Alex

 

2014-10-08 11.37.42.jpg
Regular Member
Posts: 345
Registered: ‎12-17-2009
Kudos: 34

Re: ns loco m2 lost his WLAN MAC and how to repair a bad flash memory nano station loco m2

It seems that indeed you have a bad winbound flash chip, in my case, changing winbound chip with a MX chip will cause a counterfeit protection if you will use new firmwares over 5.5, but all you have to do is go to aliexpress.com or any other site that sells winbound chipS, buy a few because they are cheap too , buy yourself an mini pro chip programmer with an sop16 adapter, get the bad winbound out of your board, make a full backup of if on your PC using the mini pro programmer , after that get a new winbound chip and write on it the previous backup you-v made from the bad chip, solder the new programmed chip on your board....start it and see if it goes...if it does not...tftp to it and write any fw. Good luck Man Happy
Regular Member
Posts: 345
Registered: ‎12-17-2009
Kudos: 34

Re: ns loco m2 lost his WLAN MAC and how to repair a bad flash memory nano station loco m2

Oh...and buy few MX chips too, because newer rev boards like I saw , have MX chips
Reply