- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hope this note find you all well in 2019.
As per Arrow FAE recommendation we used migration path Flash chips on our boards, but we are having some technical issues. I will really appreciate if you could please help and resolve this issue for us.
We made custom board based of 440EPX Sequoia board with S29GL512P flash in year 2010. We were able to get those boards working all these years. Now those S29GL512P flash chips are obsolete and so we used the migration path chip S29GL512S in our latest boards. We tried to use the same Uboot, etc on these boards and they don’t work.
We really appreciate if you could help us debug and resolve this problem.
Best regards
Madhu
Following is the dump of the old working board setup: (S29GL512P)
U-Boot 2009.06-OADS_UBOOT_11232016 (Nov 23 2016 - 14:53:07)
CPU: AMCC PowerPC 440EPx Rev. A at 528 MHz (PLB=132, OPB=66, EBC=66 MHz)
No Security/Kasumi support
Bootstrap Option C - Boot ROM Location EBC (16 bits)
Internal PCI arbiter enabled, PCI async ext clock used
32 kB I-Cache 32 kB D-Cache
Board: Oads - AMCC PPC440EPx Board, Rev. 0, PCI=33 MHz
I2C: ready
DRAM: 256 MB
FLASH: 64 MB
*** Warning - bad CRC, using default environment
PCI: Bus Dev VenId DevId Class Int
USB: Host(int phy) Device(ext phy)
Net: No ethernet found.
Abort auto-boot, then run [flash_self|flash_nfs|net_nfs]
Hit any key to stop autoboot: 0
Wrong Image Format for bootm command
ERROR: can't get kernel image!
OADS>
OADS>
OADS>
OADS>
OADS>
OADS> setenv ethaddr c0:ff:ee:c0:ff:ee
OADS> setenv ipaddr 192.168.2.5
OADS> saveenv
Saving OADS Environment to Flash...
. done
Un-Protected 1 sectors
. done
Un-Protected 1 sectors
Erasing Flash...
. done
Erased 1 sectors
Writing to Flash... done
. done
Protected 1 sectors
. done
Protected 1 sectors
OADS> reset
Following is the dump of the new working board setup: (S29GL512S)
U-Boot 2009.06-OADS_UBOOT_11232016 (Nov 23 2016 - 14:53:07)
CPU: AMCC PowerPC 440EPx Rev. A at 528 MHz (PLB=132, OPB=66, EBC=66 MHz)
No Security/Kasumi support
Bootstrap Option C - Boot ROM Location EBC (16 bits)
Internal PCI arbiter enabled, PCI async ext clock used
32 kB I-Cache 32 kB D-Cache
Board: Oads - AMCC PPC440EPx Board, Rev. FF, PCI=33 MHz
I2C: ready
DRAM: 256 MB
FLASH: 64 MB
*** Warning - bad CRC, using default environment
PCI: Bus Dev VenId DevId Class Int
USB: Host(int phy) Device(ext phy)
Net: No ethernet found.
Abort auto-boot, then run [flash_self|flash_nfs|net_nfs]
Hit any key to stop autoboot: 0
Wrong Image Format for bootm command
ERROR: can't get kernel image!
OADS>
OADS>
OADS>
OADS>
OADS> setenv ethaddr c0:ff:ee:c0:ff:ee
OADS> setenv ipaddr 192.168.2.6
OADS> saveenv
Saving OADS Environment to Flash...
. done
Un-Protected 1 sectors
. done
Un-Protected 1 sectors
Erasing Flash...
. done
Erased 1 sectors
Writing to Flash... Flash buffer write timeout at address fff40000 data a4a0a4a
Timeout writing to Flash
Flash protect timeout at address fff60000 data a4a0a4a
. done
Protected 1 sectors
Flash protect timeout at address fff40000 data a4a0a4a
. done
Protected 1 sectors
OADS>
Solved! Go to Solution.
- Labels:
-
Parallel NOR
-
Part Number Query
-
Serial NOR
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
Did you refer our migration guide from GL-P to GL-S device? You can download it from following link, https://www.cypress.com/file/199261/download. It explains all the differences between GL-P and GL-S devices and the software changes required.
Thanks and Regards,
Sudheesh
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
Did you refer our migration guide from GL-P to GL-S device? You can download it from following link, https://www.cypress.com/file/199261/download. It explains all the differences between GL-P and GL-S devices and the software changes required.
Thanks and Regards,
Sudheesh
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Sudheesh,
Thank you for your prompt response. We will take a look at the migration guide.
Thanks
Madhu