Electronics > Repair
Agilent 34461A corrupted flash
<< < (37/41) > >>
analogRF:

--- Quote from: Eng_tech on January 13, 2025, 01:16:43 pm ---Thanks, very much appreciated, I was looking at past posts and looked like it was mentioned to load the nk.nb0 file at 0x00320000. Anyway, thanks for pointing out my mistake because it looks like I was doing this all wrong. I think I tried DHCP command and didn't do anything but I'll try it again and see if it gets working. Really, thanks for the help. At work so, won't be able to try anything till tonight EST.

--- End quote ---

technically you can upload it anywhere in the ram as long as it is not used at the time but then you have to skip 0x1000 for the start or launch address.
however if you look at your boot record the FW always copies the bin file at 0x361000 and then starts at 0x362000 exactly the same as  in Keysight 3000/2000 scopes.

with DHCP command you need to give the correct addresses too just like above. or u can use tftp to upload it to memory Instead of LOADY from terminal and then use the 'go' command. your tftp server must be up and running.
if the unit still cannot connect to tftp server then I'd say there is still some hardware problem to be sorted out specially since she thinks the ethernet is connected while it isn't

I once had a case when the LAN controller chip LAN8710A needed to be replaced as well but never saw such a case again
Eng_tech:
Must still be a hardware problem. Maybe I will go back a try reheating the spear process again. Or I have RAM issues. I get the same result as I have with booting from the NAND. It boots but gets a partial screen that is white with about 1/5 of the top of the display has a blue background. Here is the boot log. I did this with Ymodem. :( >:( :palm: :wtf:

Just for fun :-DD |O I'm going to do DHCP knowing full well it ain't gonna work.  I'll heat that Spear up more tomorrow at work. Just tried DHCP, gives no ethernet adapter found, same with tftp command

Also, any idea about the 2 leds next to the FPGA on the main board. The one closest to the FPGA is always flashing and the one farthest away is always on. Is this normal behavior?

Maybe this thing is too far gone. It partially boots but stops that was giving me some hope.



--- Code: ---## Starting application at 0x00362000 ...
Windows CE Kernel for ARM (Thumb Enabled) Built on Mar  8 2013 at 17:05:33
Setting up for a Cold Reboot
Done Setting up for a Cold Reboot
Windows CE Firmware Init
BSP 1.0.0 for the SPEARHEAD600AB board (built Oct 19 2017)
Adaptation performed by ADENEO (c) 2005
+OALIntrInit
-OALIntrInit(rc = 1)
Initialize driver globals Zeros area...
pDrvGlobalArea 0xa0060000  size 0x800 (0xa0060800 -0xa0060000)
Initialize driver globals Zeros area...done
 OALKitlStart
Firmware Init Done.
OALIoctlHalEnterI2cCriticalSection init i2c cs
ERROR: C:\WINCE600\PLATFORM\COMMON\SRC\SOC\STM\SPEARHEAD600\DRIVERS\NandFlash\.\sh600_NandFlash.c line 57: ConfigTimming - Unable to open device registry entry
ERROR: C:\WINCE600\PLATFORM\COMMON\SRC\SOC\STM\COMMON\DRIVERS\NandFlash\.\stm_NandFlash.c line 1043: LLD_GetInfo - Unable to open device registry entry
++SER_Init: context Drivers\Active\10
SER_Init, dwIndex:2
GPIO_Select0 Register 0xB300_0024: 0x80000000
Control Register 0xB300_0010 : 0x00000040
RAS Select Register 0xB300_000C: 0xffffacf4
CORE_CLK_CFG 0xB300_0024: 0x80000000
SER2 got sysintr:0x00000013
SER2 Serial Port, new baud rate:0x1c200  (UARTCLK:83250000 IBRD:0x2d FBRD:0xa)
++SER_Init: context Drivers\Active\11
SER_Init, dwIndex:3
GPIO_Select0 Register 0xB300_0024: 0x80000000
Control Register 0xB300_0010 : 0x00000040
RAS Select Register 0xB300_000C: 0xffffacf4
CORE_CLK_CFG 0xB300_0024: 0x80000000
+OALIntrRequestSysIntr IRQ (1) already used by SYSINTR (19)
SER3 got sysintr:0x00000014
SER3 Serial Port, new baud rate:0x1c200  (UARTCLK:83250000 IBRD:0x2d FBRD:0xa)
OHCI\system.c, GCFG_USBH1_SW_RST
OHCI\system.c, GCFG_USBH2_SW_RST
-EDeviceLoadEeprom 80:09:02:01:BF:42
Phy not found
WaitForLink Start (ticks=3751)
Link Detected (ticks=3753)

 GMAC Init : 100 Mbit/s FULL DUPLEX (MII)
Flushed Transmit Buffer
phyCfg->dwSpeed 0x64
<--EDeviceInitialize

GMAC DMA status register = 0x600004
GMAC Device enable interrupt
DriverStart
GMAC Device enable interrupt
Resetting the USB-device silicon
sh600_pdd, IOCTL_BUS_POSTINIT
ERROR: C:\WINCE600\3RDPARTY\Agilent\HPP\Common\Drivers\stm320_UsbFnBusDriver\.\ufnbus.cpp line 1137: failed opening \Agilent Flash\SPD\usbOverride
                                                           ERROR: OALIoCtlHalGetDeviceInfo: Device doesn't support IOCTL_HAL_GET_DEVICE_INFO::SPI_GETUUID
Warning: you are calling IOCTL_HAL_GET_UUID, which has been deprecated.  Use IOCTL_HAL_GET_DEVICE_INFO instead.
ERROR: OALIoCtlHalGetUUID: Device doesn't support UUID
stm320_UsbFnBusDriver, set IST priority 96
--- End code ---
analogRF:
I would insert a USB stick with FW file on it into the device before uploading the bin file and issuing the 'go' command. Still I think the correct kernel should look for update file if it finds a usb flash

for me this is still strange and does not match what I have seen on these meters. Maybe I am wrong but I have many logs of different meters and none
shows up  like this. I mean first it says phy not found and then it shows link detected and 100Mb/sec even though no cable is connected
this is not some internal ethernet communication. this is exactly for the LAN connection.

--- Code: ---Phy not found
WaitForLink Start (ticks=3751)
Link Detected (ticks=3753)

 GMAC Init : 100 Mbit/s FULL DUPLEX (MII)
Flushed Transmit Buffer
phyCfg->dwSpeed 0x64
<--EDeviceInitialize
--- End code ---

it could be that dll files of the WInCE are corrupted as well. The next message you will see after the last line of your log is about loading some dll files.
of course there could be some other stuff going on in between which we are not aware of but as far as the UART messages are concerned the next message is about some dll files. If that's the case we need to force the unit to boot the wince from usb (just like in the keysight 3000A scopes) and thus take the dlls from there
i dont know how it can be done but it must be similar to keysight infiniivision scopes.

still I think a hardware issue is the more likely problem. if you got the cpu from aliexpress, be ready to exchange it again as I had to a couple of times.

also maybe probing around that LAN chip could be useful too
Eng_tech:
I probably won't give up on it yet. I will probably just get another cpu again. I get them from a seller on ebay. They look original. The seller is top-chips and the chips are SPEAR320S-2-AA. Others being sold on ebay are Spear320-2. The seller is good, packages it in anti-static bags and the chips are cut from a reel tape and not loose. He has them cheap at $14 a piece last time I looked. Others sell them at much higher costs. Think I will pick up 2 more. Replacing them is no easy task but I figured out a way to perfectly align them on their pads. I will show you how I manage that if I can get an image of my little fixture/guide on here. It works really good.
Eng_tech:
When I first did the YModem upload and booted I did have my USB flash drive inserted into the front panel with the firmware on it. The flash drive just flashed it's led like it was being read but the meter's screen stayed white. I left it alone giving it some time and watch the serial terminal for any indication that something was happening. After a while, I just shut off the meter and tried the same process but without the flash drive attached. It booted just like it boots off the NAND.
So, you speak of DLL files. They are not part of nk.nb0 that I uploaded via Ymodem? I'm confused. You think they are loaded in at another location in NAND? You could be correct that the boot process halts from a corrupted DLL. It looks like the process just stops as it is trying to display the blue graphics background. Gets a small part of the way and stops.
Navigation
Message Index
Next page
Previous page
There was an error while thanking
Thanking...

Go to full version
Powered by SMFPacks Advanced Attachments Uploader Mod