Author Topic: Agilent 34461A corrupted flash  (Read 22907 times)

0 Members and 2 Guests are viewing this topic.

Offline analogRF

  • Super Contributor
  • ***
  • Posts: 1024
  • Country: ca
Re: Agilent 34461A corrupted flash
« Reply #200 on: January 17, 2025, 11:46:59 am »
Jumped the gun I guess. It is randomly doing the same thing upon booting up. Sometimes the meter is working normally and sometimes I just get what I was getting before. It is a big step in the right direction I think. I have to find out why it is randomly working. Yeap, the error had something to do with calibration an serial numbers not matching. But for some reason after looking at the log the errors went away. Still gotta find out what is going on. Maybe I have a bad solder connection on that LAN chip. It was a bit of a pain getting it mounted and soldered. I used hot air on it both on top and below with and Chip Quik paste.

very much sounds like a soldering issue either with the LAN chip or the CPU itself. solder paste can be a pain...
 

Offline Eng_tech

  • Contributor
  • Posts: 26
  • Country: us
Re: Agilent 34461A corrupted flash
« Reply #201 on: January 19, 2025, 02:15:22 am »
Well, it completely stop working. I used the LAN chip from off another front panel. So, desoldering and then resoldering it to another pcb may have done damage to it. Maybe I applied heat too long or too much heat I don't know as it has a ground pad under the chip and had to make sure it connected. In any case I'm pretty sure this can be resolved. I'm ordering a new chip actually a couple from Digikey and replace the one I think is defective. This is going to take about a week or so before I get the new chip and put it on. So, I'll give an update when that is accomplished.
 

Offline Eng_tech

  • Contributor
  • Posts: 26
  • Country: us
Re: Agilent 34461A corrupted flash
« Reply #202 on: January 22, 2025, 06:00:12 am »
Finally, after putting in a new LAN IC, the meter is now working. It is fully functional, and passes both self tests. It is still coming up with an error on bootup that the serial numbers don't match but that is not affecting it's operation in any way. The serial number must be stored in NAND as I replaced the other microcontroller on the front panel with the one from my original front panel that I messed up when changing out the spear processor. I had damaged it pads trying to clean them up with solder wick. A couple pads got stuck to the solder wick and were ripped off. Hopefully it last for awhile. I have 2 spare spear processors on their way to me just in case I have to change it out again. It's not a simple task doing it by ones self. There are places that will professionally change the chip out for you as long as you provide them the chip. The cost I don't know. In all I spent a little over $100.00 to fix this thing. Which is a good deal seeing I got it for free. But anyways, I would like to thank all who gave their helpful advice in troubleshooting the problem. Also, those who posted their issues and troubleshooting methods in previous messages on here.
 
The following users thanked this post: voltsandjolts

Online voltsandjolts

  • Supporter
  • ****
  • Posts: 2592
  • Country: gb
Re: Agilent 34461A corrupted flash
« Reply #203 on: January 22, 2025, 08:36:32 am »
Can you please confirm the PN and markings on your replacement SPEAR?
Can you share the eBay item number?
Thanks.
 

Offline Eng_tech

  • Contributor
  • Posts: 26
  • Country: us
Re: Agilent 34461A corrupted flash
« Reply #204 on: January 22, 2025, 05:11:12 pm »
The seller is top-chips and the chips are SPEAR320S-2-AA. It costs I believe it was $14.00 US dollars for one. He has a limited amount so get them while you can. I have 2 on order from him now for backup spares. They are not easy to replace and must be perfectly aligned on the pads. Also, it is very easy to tear off pads if you use solder wick to remove the excess solder on the pads after removing the faulty chip. The pads need to be level. No high spots from solder or the new chip will not seat correctly. You can use flux but a very thin coating of it because it bubbles up when heated and will cause the new chip not to seat correctly. The pcb should be heated on the underside at about 130 degrees Celsius and on top with a smd hot air station about 450 - 500 celsius maybe a little more if the chip is not coming off. Don't try to pull it up. Just poke it on one of it's sides to see if it moves while heating. Once it moves keep applying heat and gently, and slowly lift it up. I made a guide out of fr4 board that fits snuggly on the front panel pcb. It fits exactly around the spear chip with only a very tiny amount of play so the chip will seat down without hanging up on the guide. It works perfectly aligning the chip up for soldering. I will try and post of picture of it sometime soon if someone wants to do it that way.
« Last Edit: January 22, 2025, 05:16:58 pm by Eng_tech »
 
The following users thanked this post: voltsandjolts

Offline coromonadalix

  • Super Contributor
  • ***
  • Posts: 7109
  • Country: ca
Re: Agilent 34461A corrupted flash
« Reply #205 on: January 22, 2025, 05:23:50 pm »
once again   a spear mcu who get defective  BUT  why ??? 

thks for the heads up


can the owners of theses 34461 65 70 series  check their working temperatures  ?
« Last Edit: January 22, 2025, 05:29:44 pm by coromonadalix »
 

Online voltsandjolts

  • Supporter
  • ****
  • Posts: 2592
  • Country: gb
Re: Agilent 34461A corrupted flash
« Reply #206 on: January 22, 2025, 06:33:58 pm »
The seller is top-chips and the chips are SPEAR320S-2-AA. It costs I believe it was $14.00 US dollars for one.

Got it, ebay.com item 395529524773
Thanks for the tip!
 

Offline Eng_tech

  • Contributor
  • Posts: 26
  • Country: us
Re: Agilent 34461A corrupted flash
« Reply #207 on: January 22, 2025, 08:11:15 pm »
Yes, temperature can be read when you put it in calibration mode. Mine is reading 26 degrees Celsius. It has been on for several hours.
 
The following users thanked this post: coromonadalix

Online kanzler

  • Newbie
  • Posts: 8
  • Country: de
Re: Agilent 34461A corrupted flash
« Reply #208 on: February 03, 2025, 10:58:35 am »
Dear analogRF,

could you please share the file nk.nb0 with me? I havent repaired my device yet so I belive it would help me out.

Thanks in advance
 

Offline analogRF

  • Super Contributor
  • ***
  • Posts: 1024
  • Country: ca
Re: Agilent 34461A corrupted flash
« Reply #209 on: February 03, 2025, 11:58:36 am »
Dear analogRF,

could you please share the file nk.nb0 with me? I havent repaired my device yet so I belive it would help me out.

Thanks in advance

which version of FW?
 

Online kanzler

  • Newbie
  • Posts: 8
  • Country: de
Re: Agilent 34461A corrupted flash
« Reply #210 on: February 03, 2025, 03:30:00 pm »
Hi,

I`d like the FW 2.17 version if possible.
 

Offline analogRF

  • Super Contributor
  • ***
  • Posts: 1024
  • Country: ca
 

Online kanzler

  • Newbie
  • Posts: 8
  • Country: de
Re: Agilent 34461A corrupted flash
« Reply #212 on: February 03, 2025, 03:53:16 pm »
Thank you very much! As soon as I make it all work out, I will update you!
 

Online kanzler

  • Newbie
  • Posts: 8
  • Country: de
Re: Agilent 34461A corrupted flash
« Reply #213 on: February 08, 2025, 10:28:35 am »
Dear analogRF,

thank ypu very much for your file. Sadly I still cant get my device to work properly and I cant download the file.
I have attached the download in my log. Would you mind take a look at it?

Thanks in advance

Code: [Select]
U-Boot 2010.03 (Oct 09 2012 - 12:48:30)Agilent P510

CPU:   SPEAr320
DRAM:  128 MiB
Unknown id: 0xffffff. Using ST_M23P40
Flash: 64 KiB
NAND:  INTERNAL ECC 128 MiB
failed: 5 0
nand_bbt: Can't scan flash and build the RAM-based BBT
In:    serial
Out:   serial
Err:   serial
SerNum:MY99999999
Chip:  AA Board Rev: 4
init  RTC: 2002-03-08 18:08:29.29
Net:   No ethernet found.
splash RTC: 2002-03-08 18:08:30.32
Press space to stop autoboot:  0
p510> run bootcmd

NAND read: device 0 offset 0x320000, size 0x10000
 65536 bytes read: OK
## Booting kernel from Legacy Image at 00600000 ...
   Image Name:   PBOOT
   Created:      2012-05-22  16:06:43 UTC
   Image Type:   ARM Linux Kernel Image (gzip compressed)
   Data Size:    38780 Bytes = 37.9 KiB
   Load Address: 00000000
   Entry Point:  00000000
   Uncompressing Kernel Image ... OK

Starting kernel ...


Debug serial initialized ........OK
No RTC on 320

Microsoft Windows CE Bootloader Common Library Version 1.4 Built May 22 2012 09:09:57
Microsoft Windows CE 6.0 Ethernet Bootloader for the Agilent P500 board
Adaptation performed by Agilent Technologies (c) 2008

Reading NAND configuration


P500 Boot Loader Configuration :

Mac address .......... (80:09:02:05:E6:FA)
Ip address ........... (192.168.1.222)
Subnet Mask address .. (255.255.255.0)
DHCP ................. (Enabled)
Boot delay (seconds).. (0)
Load image 1 at startup

Image addresses. (0xdxxxxxxx for NAND, 0x8xxxxxxx for RAM)
        1 (0xd0620000)
        2 (0xd2120000)

l) Load memory resident image Load image 1 now
1) Load memory resident image 1 now
2) Load memory resident image 2 now
3) Load memory resident image 3 now
d) Download from platform builder now
u) Start u-boot by resetting
v) Verify Images
>System ready!
Preparing for download...
No RTC on 320
 Downloading image from platform builder
Setting MAC address GMAC_MAC_ADDR_HI_LO[0] = 0x8000FAE6, GMAC_MAC_ADDR_HI_LO[1] = 0x5020980
Auto Negotiation complete in 151430 iterations
Link up
AutoNegotiate Full Duplex
AutoNegotiate 100 Base T
Reading MAC address 0x8009 0x205 0xE6FA
Setting MAC address GMAC_MAC_ADDR_HI_LO[0] = 0x8000FAE6, GMAC_MAC_ADDR_HI_LO[1] = 0x5020980
INFO: GMAC Ethernet controller initialized.
InitDHCP():: Calling ProcessDHCP()
ProcessDHCP()::DHCP_INIT
!CheckUDP: Not UDP (proto = 0x00000002)
!CheckUDP: Not UDP (proto = 0x00000002)
!CheckUDP: Not UDP (proto = 0x00000002)
!CheckUDP: Not UDP (proto = 0x00000002)
!CheckUDP: Not UDP (proto = 0x00000002)
!CheckUDP: Not UDP (proto = 0x00000002)
!CheckUDP: Not UDP (proto = 0x00000002)
!CheckUDP: Not UDP (proto = 0x00000002)
Got Response from DHCP server, IP address: 192.168.0.13

ProcessDHCP()::DHCP IP Address Resolved as 192.168.0.13, netmask: 255.255.255.0
Lease time: 179940 seconds
Got Response from DHCP server, IP address: 192.168.0.13
No ARP response in 2 seconds, assuming ownership of 192.168.0.13
+EbootSendBootmeAndWaitForTftp
Sent BOOTME to 255.255.255.255
Sent BOOTME to 255.255.255.255
Sent BOOTME to 255.255.255.255
Sent BOOTME to 255.255.255.255
Sent BOOTME to 255.255.255.255
Sent BOOTME to 255.255.255.255
Sent BOOTME to 255.255.255.255
Sent BOOTME to 255.255.255.255
Sent BOOTME to 255.255.255.255
Sent BOOTME to 255.255.255.255
Sent BOOTME to 255.255.255.255
Sent BOOTME to 255.255.255.255
Sent BOOTME to 255.255.255.255
Sent BOOTME to 255.255.255.255
Sent BOOTME to 255.255.255.255
Sent BOOTME to 255.255.255.255


« Last Edit: February 08, 2025, 10:44:58 am by kanzler »
 


Share me

Digg  Facebook  SlashDot  Delicious  Technorati  Twitter  Google  Yahoo
Smf