![]() |
|
![]() |
![]()
Сообщение
#1
|
|
![]() Опытный реаниматор ![]() ![]() ![]() ![]() Группа: Разработчики Сообщений: 178 Регистрация: 27.11.2007 Из: Moscow Пользователь №: 34 Спасибо сказали: 87 раз(а) Девайс:O2 XDA FLAME ![]() |
One man from XFU have a bricked Atom Life. Look for decision here.
Step 1. JTAG points discovery. Need: detail foto the PCB (motherboad) with both side. Step 2. Hardware preparation. Make a JTAG interface, for example very simple Xilinx or better Wiggler (download attached scheme from this post: http://forum.pda2u.ru/forum/index.php?showtopic=...ost&p=4988) Step 3. Software preparation. Need: - Bootloader for this device; - full damp from working device (optionally). Download h-jtag from .www.hjtag.com. Step 4. Software tools. Atom Life has PXA270 with a DOC. What I think jFlashMM will do. |
![]() |
|
![]() |
![]()
Сообщение
#2
|
|
Новичок ![]() Группа: Members Сообщений: 6 Регистрация: 10.6.2008 Пользователь №: 1585 Спасибо сказали: 0 раз(а) Девайс:O2 Atom Life ![]() |
One man from XFU have a bricked Atom Life. Look for decision here. Step 1. JTAG points discovery. Need: detail foto the PCB (motherboad) with both side. Step 2. Hardware preparation. Make a JTAG interface, for example very simple Xilinx or better Wiggler (download attached scheme from this post: http://forum.pda2u.ru/forum/index.php?showtopic=...ost&p=4988) Step 3. Software preparation. Need: - Bootloader for this device; - full damp from working device (optionally). Download h-jtag from .www.hjtag.com. Step 4. Software tools. Atom Life has PXA270 with a DOC. What I think jFlashMM will do. It was return message when i use jflashmm as follow: D:\Flame\ATOM EXEC JTAG\RepairBootLoader(EXEC)\JFlash_MM>jflashmm pxa27x32 ebo_ .nb0 N 0 PAR JFLASH Version 5.01.007 COPYRIGHT © 2000 - 2003 Intel Corporation PLATFORM SELECTION: Processor= PXA27x Development System= Mainstone Data Version= 1.00.001 PXA27x revision ?? Upper and Lower flash memory ID does not match. You may have a damaged flash memory. Upper half reads: 90 Lower half reads: F000 Failed to read the Flash ID. Retrying 4 more times... Upper and Lower flash memory ID does not match. You may have a damaged flash memory. Upper half reads: 90 Lower half reads: F000 Failed to read the Flash ID. Retrying 3 more times... Upper and Lower flash memory ID does not match. You may have a damaged flash memory. Upper half reads: 90 Lower half reads: F000 Failed to read the Flash ID. Retrying 2 more times... Upper and Lower flash memory ID does not match. You may have a damaged flash memory. Upper half reads: 90 Lower half reads: F000 Failed to read the Flash ID. Retrying 1 more times... Upper and Lower flash memory ID does not match. You may have a damaged flash memory. Upper half reads: 90 Lower half reads: F000 Failed to read the Flash ID. Retrying 0 more times... Cannot open input file: Flash_f000_2_32.dat This program supports flash devices defined by DAT files contained in the same directory as the executable program. If the file cannot be opened, there are four possibilities: 1 - The flash device installed is not supported. 2 - The flash device is a licensed product. 3 - The device ID could not be read, resulting in a poorly constructed filename. The first numeric value in the filename is the device ID. Verify this value with the component specification. 4 - The memory bus is not functional. Check all CPLD and FPGA devices. Make sure that you are using the correct platform data file. any advise?thanks |
![]() |
|
![]() ![]() |
![]() |
Текстовая версия | Сейчас: 14.4.2025, 23:46 |