astor Posted January 14, 2014 Report Share Posted January 14, 2014 (edited) Опитвам се да съживя един airgrid m5 HP . При качване на firmware 5.4 , web -a дава че продукта не е истински и не може да се качи AirOS. Работеше добре с 5.3.5 но вече не иска да стартира изобщо, само recovery-то баца. Пробвам само с TFT flash , Recovery-то работи но има някакъв проблем.Някой да сподели ако се сеща нещо, целта е да се върне 5.3.5 . Btw Частично зацепваше с 5.2 но даваше артефакти по web -а и нямаше MAC на радиото. Eто boot файла с FM 5.2 boot.txt Edited January 14, 2014 by astor Link to comment Share on other sites More sharing options...
Administrator 111111 Posted January 14, 2014 Administrator Report Share Posted January 14, 2014 имаше проблем с версията европеска / хамериканска Харесай поста ^^^ Форумът е за взаимопомощ а не за свършване на чужда работа ɹɐǝɥ uɐɔ noʎ ǝɹoɯ ǝɥʇ 'ǝɯoɔǝq noʎ ɹǝʇǝınb ǝɥʇ Link to comment Share on other sites More sharing options...
astor Posted January 16, 2014 Author Report Share Posted January 16, 2014 На кой firm или за устройството говориш ? Флашваше се без проблем преди това . Погледни последните редове на boot-а дали не се е прецакала паметта нещо ... Гледам има начин през SERIAL-а някой ако знае нещо да сподели . Link to comment Share on other sites More sharing options...
pavelkamburov Posted January 16, 2014 Report Share Posted January 16, 2014 На кой firm или за устройството говориш ? Флашваше се без проблем преди това . Погледни последните редове на boot-а дали не се е прецакала паметта нещо ... Гледам има начин през SERIAL-а някой ако знае нещо да сподели . Ей така за спорта я премери дали имаш едни 3.3. волта на 3 крак на флаша, че ми е интересно. Пробва ли през AirControl ? Там как е? Някой път от там става да се флашне когато се бъзика устрпйството. Link to comment Share on other sites More sharing options...
astor Posted January 17, 2014 Author Report Share Posted January 17, 2014 (edited) Не съм пробвал с Air Control но ще го направя довечера. Може ли по подробно да ми покажеш точно къде да пробвам за 3.3 -те волта ? на самия чип WINBOUND ли ? по време на флаша или изобщо трябва да ти има ? Интересното е че когато се флашваше успешно при самото флашване LED-овете играеха отгоре надолу и обратно а сега седят само червен и зелен. Иначе в Recovery mode си се сменят по двойки както трябва. Благодаря. Edited January 17, 2014 by astor Link to comment Share on other sites More sharing options...
pavelkamburov Posted January 17, 2014 Report Share Posted January 17, 2014 Не съм пробвал с Air Control но ще го направя довечера. Може ли по подробно да ми покажеш точно къде да пробвам за 3.3 -те волта ? на самия чип WINBOUND ли ? по време на флаша или изобщо трябва да ти има ? Интересното е че когато се флашваше успешно при самото флашване LED-овете играеха отгоре надолу и обратно а сега седят само червен и зелен. Иначе в Recovery mode си се сменят по двойки както трябва. Благодаря. На тоя крак ако не се лъжа трябва да има 3.3 волта когато паметта е разрешена за запис. Случвало се е да не може да се флашне защото или крака се е окислил или се е загубило някуде по платката. Ако не е 3.3 волта а е по-малко примерно или ту го има ту го няма може при флашване да не флашваш читаво самия чип. Случвало ми се е от окислен проходен отвор на платката. Дано не те лъжа за крака ама надявам се схвана идеята. относно Air Control,нямам обяснение. няколко пъти ме е спасявал след калпаво флашване. що се флашва калпаво или що се оправя с Аir Control нямам идея , не съм ровил да видя за кво става въпрос. Това са просто факти от трагичния опит с такива машинки. Link to comment Share on other sites More sharing options...
astor Posted January 17, 2014 Author Report Share Posted January 17, 2014 Нищо не стана с AirControl просто не вижда нищо, поставям го ръчно но пак нищо. За да стане нещо първо трябва да се конектне за да е Меnaget. Нямам никакъв отговор от грида. Пак сложих 5.2 пак няма web но поне има SSH. Записах firm 5.5.6 и с FWUpdate.real -m ъпдейтнах няма никакви грешки при ъпдейта но пак няма ни пинг нито web. Working(3) with block: /dev/mtd5 Copying FIS partition: 5 <= name: 'EEPROM' flash_base: 0x9F7F0000 mem_base: 0x00000000 size: 0x00010000 entry_point: 0x00000000 data_len: 0x00010000 desc_cksum: 0x00000000 file_cksum: 0x00000000 =========================== New FIS entries count 6 Exec Script: '/tmp/bin/preflash' Working(1) with block: /dev/mtd0 Working(2) with block: /dev/mtd0 Unlocking /dev/mtd0(u-boot) ... Unlocking device failed: ioctl(MEMUNLOCK): Operation not supported Writing 'u-boot ' to /dev/mtd0(u-boot ) ... Writing: 0x0002D230 bytes with offset 0x00000000 [%0 ] Block on '/dev/mtd0' at 00000000(len: 00010000) has changes. [%35 ] Block on '/dev/mtd0' at 00010000(len: 00010000) has changes. [%70 ] Block on '/dev/mtd0' at 00020000(len: 0000D230) has changes. [%100] End check: 9F000000 + 00040000 <= 9F040000 Creating FIS partition: 0 => name: 'u-boot' flash_base: 0x9F000000 mem_base: 0x9F000000 size: 0x00040000 entry_point: 0x00000000 data_len: 0x0002D230 desc_cksum: 0x00000000 file_cksum: 0x00000000 =========================== Working(1) with block: /dev/mtd0 Skipping: artificial: 0, unallocated: 0,writeable: 3(WRITEABLE: 3, flags: 7), fw.flash_base: 9F050000 < blk->base: 9F000000 + blk->size: 40000 Working(1) with block: /dev/mtd1 Skipping: artificial: 0, unallocated: 0,writeable: 3(WRITEABLE: 3, flags: 7), fw.flash_base: 9F050000 < blk->base: 9F040000 + blk->size: 10000 Copying FIS partition: 1 => name: 'u-boot-env' flash_base: 0x9F040000 mem_base: 0x00000000 size: 0x00010000 entry_point: 0x00000000 data_len: 0x00010000 desc_cksum: 0x00000000 file_cksum: 0x00000000 =========================== Working(1) with block: /dev/mtd2 Working(2) with block: /dev/mtd2 Unlocking /dev/mtd2(kernel) ... Unlocking device failed: ioctl(MEMUNLOCK): Operation not supported Writing 'kernel ' to /dev/mtd2(kernel ) ... Writing: 0x000FFC60 bytes with offset 0x00000000 [%0 ] Block on '/dev/mtd2' at 00000000(len: 00010000) has changes. [%6 ] Block on '/dev/mtd2' at 00010000(len: 00010000) has changes. [%12 ] Block on '/dev/mtd2' at 00020000(len: 00010000) has changes. [%18 ] Block on '/dev/mtd2' at 00030000(len: 00010000) has changes. [%25 ] Block on '/dev/mtd2' at 00040000(len: 00010000) has changes. [%31 ] Block on '/dev/mtd2' at 00050000(len: 00010000) has changes. [%37 ] Block on '/dev/mtd2' at 00060000(len: 00010000) has changes. [%43 ] Block on '/dev/mtd2' at 00070000(len: 00010000) has changes. [%50 ] Block on '/dev/mtd2' at 00080000(len: 00010000) has changes. [%56 ] Block on '/dev/mtd2' at 00090000(len: 00010000) has changes. [%62 ] Block on '/dev/mtd2' at 000A0000(len: 00010000) has changes. [%68 ] Block on '/dev/mtd2' at 000B0000(len: 00010000) has changes. [%75 ] Block on '/dev/mtd2' at 000C0000(len: 00010000) has no changes. [%81 ] Block on '/dev/mtd2' at 000D0000(len: 00010000) has no changes. [%87 ] Block on '/dev/mtd2' at 000E0000(len: 00010000) has no changes. [%93 ] Block on '/dev/mtd2' at 000F0000(len: 0000FC60) has no changes. [%100] End check: 9F050000 + 00100000 <= 9F150000 Creating FIS partition: 2 => name: 'kernel' flash_base: 0x9F050000 mem_base: 0x80002000 size: 0x00100000 entry_point: 0x80002000 data_len: 0x000FFC60 desc_cksum: 0x00000000 file_cksum: 0x00000000 =========================== Working(1) with block: /dev/mtd2 Skipping: artificial: 0, unallocated: 0,writeable: 3(WRITEABLE: 3, flags: 7), fw.flash_base: 9F150000 < blk->base: 9F050000 + blk->size: 100000 Working(1) with block: /dev/mtd3 Working(2) with block: /dev/mtd3 Unlocking /dev/mtd3(rootfs) ... Unlocking device failed: ioctl(MEMUNLOCK): Operation not supported Writing 'rootfs ' to /dev/mtd3(rootfs ) ... Writing: 0x00560000 bytes with offset 0x00000000 [%0 ] Block on '/dev/mtd3' at 00000000(len: 00010000) has changes. [%1 ] Block on '/dev/mtd3' at 00010000(len: 00010000) has changes. [%2 ] Block on '/dev/mtd3' at 00020000(len: 00010000) has changes. [%3 ] Block on '/dev/mtd3' at 00030000(len: 00010000) has changes. [%4 ] Block on '/dev/mtd3' at 00040000(len: 00010000) has changes. [%5 ] Block on '/dev/mtd3' at 00050000(len: 00010000) has changes. [%6 ] Block on '/dev/mtd3' at 00060000(len: 00010000) has changes. [%8 ] Block on '/dev/mtd3' at 00070000(len: 00010000) has changes. [%9 ] Block on '/dev/mtd3' at 00080000(len: 00010000) has changes. [%10 ] Block on '/dev/mtd3' at 00090000(len: 00010000) has changes. [%11 ] Block on '/dev/mtd3' at 000A0000(len: 00010000) has changes. [%12 ] Block on '/dev/mtd3' at 000B0000(len: 00010000) has changes. [%13 ] Block on '/dev/mtd3' at 000C0000(len: 00010000) has changes. [%15 ] Block on '/dev/mtd3' at 000D0000(len: 00010000) has changes. [%16 ] Block on '/dev/mtd3' at 000E0000(len: 00010000) has changes. [%17 ] Block on '/dev/mtd3' at 000F0000(len: 00010000) has changes. [%18 ] Block on '/dev/mtd3' at 00100000(len: 00010000) has changes. [%19 ] Block on '/dev/mtd3' at 00110000(len: 00010000) has changes. [%20 ] Block on '/dev/mtd3' at 00120000(len: 00010000) has changes. [%22 ] Block on '/dev/mtd3' at 00130000(len: 00010000) has changes. [%23 ] Block on '/dev/mtd3' at 00140000(len: 00010000) has changes. [%24 ] Block on '/dev/mtd3' at 00150000(len: 00010000) has changes. [%25 ] Block on '/dev/mtd3' at 00160000(len: 00010000) has changes. [%26 ] Block on '/dev/mtd3' at 00170000(len: 00010000) has changes. [%27 ] Block on '/dev/mtd3' at 00180000(len: 00010000) has changes. [%29 ] Block on '/dev/mtd3' at 00190000(len: 00010000) has changes. [%30 ] Block on '/dev/mtd3' at 001A0000(len: 00010000) has changes. [%31 ] Block on '/dev/mtd3' at 001B0000(len: 00010000) has changes. [%32 ] Block on '/dev/mtd3' at 001C0000(len: 00010000) has changes. [%33 ] Block on '/dev/mtd3' at 001D0000(len: 00010000) has changes. [%34 ] Block on '/dev/mtd3' at 001E0000(len: 00010000) has changes. [%36 ] Block on '/dev/mtd3' at 001F0000(len: 00010000) has changes. [%37 ] Block on '/dev/mtd3' at 00200000(len: 00010000) has changes. [%38 ] Block on '/dev/mtd3' at 00210000(len: 00010000) has changes. [%39 ] Block on '/dev/mtd3' at 00220000(len: 00010000) has changes. [%40 ] Block on '/dev/mtd3' at 00230000(len: 00010000) has changes. [%41 ] Block on '/dev/mtd3' at 00240000(len: 00010000) has changes. [%43 ] Block on '/dev/mtd3' at 00250000(len: 00010000) has changes. [%44 ] Block on '/dev/mtd3' at 00260000(len: 00010000) has changes. [%45 ] Block on '/dev/mtd3' at 00270000(len: 00010000) has changes. [%46 ] Block on '/dev/mtd3' at 00280000(len: 00010000) has changes. [%47 ] Block on '/dev/mtd3' at 00290000(len: 00010000) has changes. [%48 ] Block on '/dev/mtd3' at 002A0000(len: 00010000) has changes. [%50 ] Block on '/dev/mtd3' at 002B0000(len: 00010000) has changes. [%51 ] Block on '/dev/mtd3' at 002C0000(len: 00010000) has changes. [%52 ] Block on '/dev/mtd3' at 002D0000(len: 00010000) has changes. [%53 ] Block on '/dev/mtd3' at 002E0000(len: 00010000) has changes. [%54 ] Block on '/dev/mtd3' at 002F0000(len: 00010000) has changes. [%55 ] Block on '/dev/mtd3' at 00300000(len: 00010000) has changes. [%56 ] Block on '/dev/mtd3' at 00310000(len: 00010000) has changes. [%58 ] Block on '/dev/mtd3' at 00320000(len: 00010000) has changes. [%59 ] Block on '/dev/mtd3' at 00330000(len: 00010000) has changes. [%60 ] Block on '/dev/mtd3' at 00340000(len: 00010000) has changes. [%61 ] Block on '/dev/mtd3' at 00350000(len: 00010000) has changes. [%62 ] Block on '/dev/mtd3' at 00360000(len: 00010000) has changes. [%63 ] Block on '/dev/mtd3' at 00370000(len: 00010000) has changes. [%65 ] Block on '/dev/mtd3' at 00380000(len: 00010000) has changes. [%66 ] Block on '/dev/mtd3' at 00390000(len: 00010000) has changes. [%67 ] Block on '/dev/mtd3' at 003A0000(len: 00010000) has changes. [%68 ] Block on '/dev/mtd3' at 003B0000(len: 00010000) has changes. [%69 ] Block on '/dev/mtd3' at 003C0000(len: 00010000) has changes. [%70 ] Block on '/dev/mtd3' at 003D0000(len: 00010000) has changes. [%72 ] Block on '/dev/mtd3' at 003E0000(len: 00010000) has changes. [%73 ] Block on '/dev/mtd3' at 003F0000(len: 00010000) has changes. [%74 ] Block on '/dev/mtd3' at 00400000(len: 00010000) has changes. [%75 ] Block on '/dev/mtd3' at 00410000(len: 00010000) has changes. [%76 ] Block on '/dev/mtd3' at 00420000(len: 00010000) has changes. [%77 ] Block on '/dev/mtd3' at 00430000(len: 00010000) has changes. [%79 ] Block on '/dev/mtd3' at 00440000(len: 00010000) has changes. [%80 ] Block on '/dev/mtd3' at 00450000(len: 00010000) has changes. [%81 ] Block on '/dev/mtd3' at 00460000(len: 00010000) has changes. [%82 ] Block on '/dev/mtd3' at 00470000(len: 00010000) has changes. [%83 ] Block on '/dev/mtd3' at 00480000(len: 00010000) has changes. [%84 ] Block on '/dev/mtd3' at 00490000(len: 00010000) has changes. [%86 ] Block on '/dev/mtd3' at 004A0000(len: 00010000) has changes. [%87 ] Block on '/dev/mtd3' at 004B0000(len: 00010000) has changes. [%88 ] Block on '/dev/mtd3' at 004C0000(len: 00010000) has changes. [%89 ] Block on '/dev/mtd3' at 004D0000(len: 00010000) has changes. [%90 ] Block on '/dev/mtd3' at 004E0000(len: 00010000) has changes. [%91 ] Block on '/dev/mtd3' at 004F0000(len: 00010000) has changes. [%93 ] Block on '/dev/mtd3' at 00500000(len: 00010000) has changes. [%94 ] Block on '/dev/mtd3' at 00510000(len: 00010000) has changes. [%95 ] Block on '/dev/mtd3' at 00520000(len: 00010000) has no changes. [%96 ] Block on '/dev/mtd3' at 00530000(len: 00010000) has no changes. [%97 ] Block on '/dev/mtd3' at 00540000(len: 00010000) has changes. [%98 ] Block on '/dev/mtd3' at 00550000(len: 00010000) has no changes. [%100] End check: 9F150000 + 00660000 <= 9F7B0000 Creating FIS partition: 3 => name: 'rootfs' flash_base: 0x9F150000 mem_base: 0x9F150000 size: 0x00660000 entry_point: 0x00000000 data_len: 0x00560000 desc_cksum: 0x00000000 file_cksum: 0x00000000 =========================== Working(3) with block: /dev/mtd4 Copying FIS partition: 4 <= name: 'cfg' flash_base: 0x9F7B0000 mem_base: 0x00000000 size: 0x00040000 entry_point: 0x00000000 data_len: 0x00040000 desc_cksum: 0x00000000 file_cksum: 0x00000000 =========================== Working(3) with block: /dev/mtd5 Copying FIS partition: 5 <= name: 'EEPROM' flash_base: 0x9F7F0000 mem_base: 0x00000000 size: 0x00010000 entry_point: 0x00000000 data_len: 0x00010000 desc_cksum: 0x00000000 file_cksum: 0x00000000 =========================== New FIS entries count 6 FIS Change: added partition terminator instead of 0x75. New partition count: 0, changes: 1 Writing U-Boot environment to /dev/mtd1 Done Link to comment Share on other sites More sharing options...
mysticall Posted January 17, 2014 Report Share Posted January 17, 2014 (edited) Нищо не стана с AirControl просто не вижда нищо, поставям го ръчно но пак нищо. За да стане нещо първо трябва да се конектне за да е Меnaget. Нямам никакъв отговор от грида. Пак сложих 5.2 пак няма web но поне има SSH. Записах firm 5.5.6 и с FWUpdate.real -m ъпдейтнах няма никакви грешки при ъпдейта но пак няма ни пинг нито web. Unlocking /dev/mtd0(u-boot) ... Unlocking device failed: ioctl(MEMUNLOCK): Operation not supported Според мен, след като се зареди линукса SPI паметта е заключена и не може да се презапише (да се обнови операционната система), евентуален проблем с драйвърите или със самия чип. Още по притеснително е, че новата ОС иска да барника критичен дял: /dev/mtd0(u-boot) - съдържа зареждащата програма, която съживява платката, ако този дял се изтрие и преди да се запише новата информация стане някакъв фал, ще търсеш програматор за чипа. Снабди се с USB to UART TTL от http://www.ebay.com/sch/i.html?_odkw=usb+to+ttl+UART&_osacat=0&_from=R40&_trksid=p2045573.m570.l1313.TR12.TRC2.A0.Xusb+to+UART+ttl&_nkw=usb+to+UART+ttl&_sacat=0 или от http://www.sirius-pcb.com/index.php?mod=catalog&show=600 и виж какво става с устройството преди да зареди ОС. Не пробвай връзка през директен serial порт, понеже през serial порт напрежението играе (ако не се лъжа) от -10v до 10v. В добрия случай ще имаш артефакти на конзолана, а в лошия изгоряло устройство. През UART TTL се подава 0v или 1v за комуникация. Устройството очаква 0v или 1v. Прегледай този пост http://community.ubnt.com/t5/Installation-Troubleshooting/NS-Loco-M5-inaccessible-after-hard-reset/m-p/108830#M20080 за пълен ресет на настройките на антената. Блежка: Бъди много внимателен когато работиш с комантите в u-boot. Никога не използвай erase all !!! Ще изтрие цялото съдържание на флаш паметта. Edited January 17, 2014 by mysticall Link to comment Share on other sites More sharing options...
pavelkamburov Posted January 17, 2014 Report Share Posted January 17, 2014 Unlocking device failed: ioctl(MEMUNLOCK): Operation not supported Не разбрах има ли ги тия 3.3. волта или ги няма . Чипа е повреден или просто не се подава напрежение на крака му който разрешава запис. затова питах за тия 3.3 волта. Я кажи точния модел на флаш паметта. Link to comment Share on other sites More sharing options...
Balthazar Posted January 17, 2014 Report Share Posted January 17, 2014 Сваляш флаш-а и го пишеш на програматора на ново насрал си bootloader-а най вероятно Link to comment Share on other sites More sharing options...
astor Posted January 17, 2014 Author Report Share Posted January 17, 2014 (edited) Unlocking device failed: ioctl(MEMUNLOCK): Operation not supported Не разбрах има ли ги тия 3.3. волта или ги няма . Чипа е повреден или просто не се подава напрежение на крака му който разрешава запис. затова питах за тия 3.3 волта. Я кажи точния модел на флаш паметта. WINBOND W9425G6JH-5 Eто pdf http://www.winbond.com/NR/rdonlyres/11505884-F632-41F9-9438-A3EC025FEAED/0/W9425G6JH.pdf Edited January 17, 2014 by astor Link to comment Share on other sites More sharing options...
pavelkamburov Posted January 17, 2014 Report Share Posted January 17, 2014 (edited) Сваляш флаш-а и го пишеш на програматора на ново насрал си bootloader-а най вероятно е то това е ясно. Въпроса е че, не всеки има като теб и мен програматори ;-) чипа се сваля гадно гадно се запоява, трябва преходник към програматора трябва и читав програматор и т.н. и т.н. а и тоя надпис за заключен чип едва ли има нещо общо с боот лоадера според мен. WINBOND W9425G6JH-5 Eто pdf http://www.winbond.com/NR/rdonlyres/11505884-F632-41F9-9438-A3EC025FEAED/0/W9425G6JH.pdf Това дето си ми написал е DDR RAM не флаш памет WINBOND W9425G6JH-5 Eто pdf http://www.winbond.com/NR/rdonlyres/11505884-F632-41F9-9438-A3EC025FEAED/0/W9425G6JH.pdf Би трябвало да е нещо такова флаша MX 25L6405DZNI-126 Edited January 17, 2014 by pavelkamburov Link to comment Share on other sites More sharing options...
astor Posted January 17, 2014 Author Report Share Posted January 17, 2014 (edited) Winbond 25Q64CVIG http://www.datasheetarchive.com/Winbond%2025Q64CVIG-datasheet.html Edited January 17, 2014 by astor Link to comment Share on other sites More sharing options...
pavelkamburov Posted January 18, 2014 Report Share Posted January 18, 2014 Winbond 25Q64CVIG http://www.datasheetarchive.com/Winbond%2025Q64CVIG-datasheet.html е те за тоя 3-ти крак ти говорех да видиш има ли едни 3.3. волта на него като флашваш чипа. Link to comment Share on other sites More sharing options...
astor Posted January 18, 2014 Author Report Share Posted January 18, 2014 (edited) Ще пробвам . Поръчах серииния интерфейс но кога ще дойде не знам. Благодаря Има 3.3 V на 3-то краче постоянно ,само при рестарт изчезва и при самото флашване варира. А може и да съм на грешния крак но мисля че не от точката която бележи 1-во краче отивам на 3-то. Edited January 18, 2014 by astor Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now