Anda di halaman 1dari 6

AS7_D eSW

Shirokikh, Vasily (NSN - RU/Moscow) 63 posts since Feb 1, 2012


AS7_D eSW Mar 25, 2014 12:59 PM
Hi Experts,
Could you inform why AS7_D primary image (FlexiBSC) could be not updated properly?
For example, we had version 1.4-0 on both AS7s in BCSU-3:
BCSU-3

AS7-13

DMX SUPPORT FPGA


ACTIVE IMAGE:

PRIMARY (b3)

PRIMARY IMAGE: D1XRADGX.PAC 1.4-0 09/02/26 PL


DISK IMAGE:

D1XRADGX.PAC 1.4-0 09/02/26 PLAENVBE.PAC

FPGA IMAGE:

AD7FPGPY.PAC 1.7-0 11/10/03 PL

PCI BRIDGE FPGA


ACTIVE IMAGE:
DISK IMAGE:

--

PIU BOOT SW:


DISK IMAGE:

--

BOPASDGX.PAC 1.14-0 12/01/03


BOPASDGX.PAC 1.14-0 12/01/03

( AD7BOPPY.PAC 1.14-0 12/01/03 PLAENVBD.PA )


PROG PACKAGE IDENTIFICATION CODE PACKAGE AREA
CID: AD7COMPY.PAC 2.35-0 12/05/18

3FE7.6F10...3FEE.A7BC

(AS7_D in 14th slot has the same)


But in BCSU-0 the both AS7s have version 1.1-0:
BCSU-0

AS7-13

DMX SUPPORT FPGA

Generated by Jive on 2014-06-12Z


1

AS7_D eSW

ACTIVE IMAGE:

PRIMARY (700d)

PRIMARY IMAGE: D1XADVGX.PAC 1.1-0 08/05/12 PL


DISK IMAGE:

FPGA IMAGE:

D1XADVGX.PAC 1.1-0 08/05/12 PLAENVBE.PAC

AD7FPGPY.PAC 1.7-0 11/10/03 PL

PCI BRIDGE FPGA


ACTIVE IMAGE:
DISK IMAGE:

PIU BOOT SW:


DISK IMAGE:

---

BOPASDGX.PAC 1.14-0 12/01/03


BOPASDGX.PAC 1.14-0 12/01/03

( AD7BOPPY.PAC 1.14-0 12/01/03 PLAENVBD.PA )


PROG PACKAGE IDENTIFICATION CODE PACKAGE AREA
CID: AD7COMPY.PAC 2.35-0 12/05/18

3FE7.6F10...3FEE.A7BC

After upgrade (WDH:UT=BCSU,UI=0,PT=AS7_D;) AS7-14 has been upgraded up to 1.4-0 but AS7-13 still
remain on the 1.1-0.
What could it be?
Could it be depend on AS7_D vendor (Advantech, RadiSys)?
Thanks in advance!
BR,
Vasily.

Bahl, Prashant (NSN - FI/Tampere) 236 posts since Jun 6, 2011


Re: AS7_D eSW Mar 25, 2014 1:02 PM
Hello Vasily,
As per my understanding it is updated properly & I can see correct boot versions 1.4-0 for RADISYS & 1.1-0 for
ADVANTECH.
May be you have different HW variants for AS7 cards ? Can you please check & confirm ?
Thanks

Generated by Jive on 2014-06-12Z


2

AS7_D eSW

BR,Prashant
Embedded SW.jpg 73.0 K

Shirokikh, Vasily (NSN - RU/Moscow) 63 posts since Feb 1, 2012


Re: AS7_D eSW Mar 25, 2014 1:12 PM
in response to Bahl, Prashant (NSN - FI/Tampere)
Thank you Prashant,
I have two additional questions:
1) Is it possible to detect AS7_D vendor via MML?
If DX200 system can understand which image should be loaded to the certain board suspect it can be detected
remotely.
2) What about compatibility of different AS7_D vendors in one BCSU (FlexiBSC)?
Is there any known restrictions/bugs?
3) If we have non-updated AS7_Ds in FlexiBSC could it impach on BCSU test result (unsuccessful ZUDU)?
Thanks!
BR,
Vasily.

Bahl, Prashant (NSN - FI/Tampere) 236 posts since Jun 6, 2011


Re: AS7_D eSW Mar 25, 2014 1:29 PM
in response to Shirokikh, Vasily (NSN - RU/Moscow)
Hello Vasily,
I would say very logical & interesting questions,
1. As per my understanding,I would always check the layout of PIU physically to get to know the AS7 HW
make.But there should be some way to check the same.I requested Pasi to check if there is any way and if yes
it will be a great information for me as well :-)
2.No Restrictions (Just you need to make sure about jumper settings/Switches)
3. It should not impact any Diagnostic results as generally Internal PCM positions and HW basic check is done
for AS7 when we do the diagnostics.

Generated by Jive on 2014-06-12Z


3

AS7_D eSW

Thanks
BR,Prashant

Shirokikh, Vasily (NSN - RU/Moscow) 63 posts since Feb 1, 2012


Re: AS7_D eSW Mar 25, 2014 1:41 PM
in response to Bahl, Prashant (NSN - FI/Tampere)
Hello Prashant,
Please ask experts about vendor checking possibility, it would be really helpful.
You say:
>>It should not impact any Diagnostic results as generally Internal PCM positions and HW basic check is done
for AS7 when we do the diagnostics.
So are you sure the following fluctuating issue couldn't be caused by wrong eSW?
DIAGNOSTIC REPORT
BCSU-6
PARTIAL DIAGNOSIS

AS7

DIAGNOSTIC PROGRAM
DIAGNOSIS
EXTRA INFO 1

002E

3810
01AE

EXTRA INFO 2
000D
3810 EXTERNAL LOOP FAILURE IN PREPROCESSOR TEST
END OF REPORT
Sometimes BCSU pass diagnosis, sometimes not.
Seems like SW issue, we suspected eSW.
This issue observed with 1.4-0 image, looks like it's RadiSys.
BR,
Vasily.

Bahl, Prashant (NSN - FI/Tampere) 236 posts since Jun 6, 2011


Re: AS7_D eSW Mar 25, 2014 1:48 PM
in response to Shirokikh, Vasily (NSN - RU/Moscow)
Hello Vasily,

Generated by Jive on 2014-06-12Z


4

AS7_D eSW

I don't agree this LOOP TEST failure to be eSW fault,we had faced lot of similar issues before & one of them
what I remember where we did a nice troubleshooting was this one was NA05273889 from STC.Have a look
there :-)
Anyways a very good information how to troubleshoot AS7 diagnostics failure due to faulty
cable/slot in BCSU by ruling out which all PCMs are getting failed in diagnostics according to
cables plugged in.
We should take ZOQI:4099 from BCSU Service Terminal (after the BCSU has first restarted once after ZUDU
from another MML terminal)
Then, the last 4099 that can be seen before BCSU goes to SE contains the failing PCM, here 3A hex = 58
decimal.
MONITORED MESSAGE: 0022 0004 0071 0000 00 11 0016 4099 0036
00 01 00 E0 2E 00 00 01 00 00 00 00 3A 00 00 3A 00 00
Then by comparing this to the ZWTI output the problematic cable can be found out. Now, after swapping (in
BCSU-6) if it is still 3A, it is not the cable but the slot in one of the ends (cartridge).....
Thanks
BR,Prashant

Nieminen, Pasi (NSN - FI/Tampere) 142 posts since Oct 19, 2011
Re: AS7_D eSW Mar 25, 2014 2:14 PM
in response to Bahl, Prashant (NSN - FI/Tampere)
Hi,
In my understanding there is not any MML to check the manufacturer of AS7 plug-in unit. But as with the
information above you can conclude the manufacturer from different name of module.
Radisys: PRIMARY IMAGE: D1XRADGX.PAC 1.4-0 09/02/26 PL
Advantech: PRIMARY IMAGE: D1XADVGX.PAC 1.1-0 08/05/12 PL
And for updating the software you just need to check the primary image & disk image are the same as below.
PRIMARY IMAGE: D1XRADGX.PAC 1.4-0 09/02/26 PL
DISK IMAGE:

D1XRADGX.PAC 1.4-0 09/02/26 PLAENVBE.PAC

BR,
-Pasi N.

Generated by Jive on 2014-06-12Z


5

AS7_D eSW

Shirokikh, Vasily (NSN - RU/Moscow) 63 posts since Feb 1, 2012


Re: AS7_D eSW Mar 25, 2014 2:16 PM
in response to Bahl, Prashant (NSN - FI/Tampere)
Hello Prashant,
Thanks for nice hint, it's really important info.
If physical connection could be wrong BCSU shouldn't pass diagnosis permanently, isn't it?
But after we restarted or switched over BCSU diag can pass.
Where is the glue with HW issue?
BR,
Vasily.

Bahl, Prashant (NSN - FI/Tampere) 236 posts since Jun 6, 2011


Re: AS7_D eSW Mar 25, 2014 2:20 PM
in response to Shirokikh, Vasily (NSN - RU/Moscow)
Hello Vasily,
Let's not discuss now improvement proposals of our diagnostic programs ;-)
I agree they inform us upto some accuracy of fault but not 100 %.But I am just trying to tell keep your options
open>>this could be a PCM cable fault as well.
Thanks
BR,Prashant

Shirokikh, Vasily (NSN - RU/Moscow) 63 posts since Feb 1, 2012


Re: AS7_D eSW Mar 25, 2014 2:22 PM
in response to Bahl, Prashant (NSN - FI/Tampere)
Ok, thanks all!
I'll try to check cables.
BR,
Vasily.

Generated by Jive on 2014-06-12Z


6