You are here

3.16.1.0b oddity

3 posts / 0 new
Last post
wb6tae
3.16.1.0b oddity

I updated my Rocket M2 and it is working fine.  However, something is weird.  By accident, I updated with the Nanostation-M2 firmware. But, when I look at the sysinfo, I get the information (attached below) saying this is a Nanostation M.  Really, it isn't, and I have always used the Rocket builds in the past.

So, should I load the Rocket firmware now or just leave it as it is???

Richard - wb6tae

========== cat /proc/cpuinfo ==========
system type        : Atheros AR7241 rev 1
machine            : Ubiquiti Nanostation M
processor        : 0
cpu model        : MIPS 24Kc V7.4
BogoMIPS        : 259.27
wait instruction    : yes
microsecond timers    : yes
tlb_entries        : 16
extra interrupt vector    : yes
hardware watchpoint    : yes, count: 4, address/irw mask: [0x0000, 0x0ff8, 0x0ff8, 0x0ff8]
isa            : mips1 mips2 mips32r1 mips32r2
ASEs implemented    : mips16
shadow register sets    : 1
kscratch registers    : 0
core            : 0
VCED exceptions        : not available
VCEI exceptions        : not available

KG6JEI
That would be expected

That would be expected behavior of loading the NanoStation image.

I would recommend reloading with the rocket image.  While there is no super significant failure in this particular case that I am aware of it is better to be running the correct image file.

technicial info follows:
The machine type in this area is determined by looking at how the hardware was booted. Eqch image contains a different set of boot parameters to inform the operating system what image type it is because there is no such thing as PnP (Plug N Play) on these embedded devices like in Windows or Linux on a full PC.

Many but not all (especially XW) images share a lot of the same basics, but others have unique items.  The NanoStation for example has two ethernet ports. And while we don't use the second port the NanoStation flag tells the core system to know the port exists.   This is why the NanoLoco actually uses the bullet image because it's hardware is basically the same as a bullet just with a second wireless port which is handled internally. The Full NanoStation is basically a bullet with a second ethernet port, but that port needs specific register bits to be set for it tone initialized on chip and for the OS to "register" it internally.

There are also other deeper items that can be affected by these wrong images like GPIO locations and similar.
 

wb6tae
Thanks. That all makes sense.

Thanks.

That all makes sense.

Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer