Reply
Thread Tools
Posts: 1,067 | Thanked: 2,383 times | Joined on Jan 2012 @ Finland
#41
Hopefully you never tried to flash 280 version, since if you did then you can never go back to 006, that would explain why mcu sw flashing fails.
__________________
IRC: jonni@freenode
Sailfish: ¤ Qt5 SailfishTouchExample ¤ Qt5 MultiPointTouchArea Example ¤ ipaddress ¤ stoken ¤ Sailbox (Dropbox client) ¤
Harmattan: ¤ Presence VNC for Harmattan ¤ Live-F1 ¤ BTinput-terminal ¤ BabyLock ¤ BabyLock Trial ¤ QML TextTV ¤
Disclaimer: all my posts in this forum are personal trolling and I never post in any official capacity on behalf of any company.
 
Posts: 32 | Thanked: 7 times | Joined on Apr 2013
#42
But that's not the case. If That was the scenario I couldn't even flush the rootfs I believe. and
Code:
flashar -i
was supposed to show 280 instead of
Code:
Version of 'sw-release': DFL61_HARMATTAN_40.2012.21-3_PR_006
Then what can be the problem with mcu sw ? I am not getting any hints

Last edited by neel.basu; 2013-04-30 at 06:11.
 
Posts: 1,067 | Thanked: 2,383 times | Joined on Jan 2012 @ Finland
#43
Well there are 2 possibilities, if modem harware is broken, then mcusw flashing fails, or the other possibility, if you have tried to flash any other (ie wrong number) firmware even once, then then its overwritten mcusw with too new mcusw timestamp, and all the subsequental flashes to 006 will fail (because downgrade of mcusw is never allowed).
__________________
IRC: jonni@freenode
Sailfish: ¤ Qt5 SailfishTouchExample ¤ Qt5 MultiPointTouchArea Example ¤ ipaddress ¤ stoken ¤ Sailbox (Dropbox client) ¤
Harmattan: ¤ Presence VNC for Harmattan ¤ Live-F1 ¤ BTinput-terminal ¤ BabyLock ¤ BabyLock Trial ¤ QML TextTV ¤
Disclaimer: all my posts in this forum are personal trolling and I never post in any official capacity on behalf of any company.
 
Posts: 32 | Thanked: 7 times | Joined on Apr 2013
#44
How will I confirm which one of these two possibilities have occurred in my case ? as I can boot in Can I send any commands to cellular modem through terminal to check what version its using (though I don't remember I've ever done that. but still good to have a check) ? or if its broken.

and as flasher -i is reporting 006 doesn't it mean that cmt is also using 006 only ?
 
Posts: 646 | Thanked: 1,124 times | Joined on Jul 2010 @ Espoo, Finland
#45
What about trying to flash with variant 280 (if it's a suitable variant for you) ?
 
Posts: 32 | Thanked: 7 times | Joined on Apr 2013
#46
checked my .bash_history , there is no reference of 280. I've checked all flasher commands that I've ever invoked. and none of them have 280. also I saw I never downloaded 280.

I have only 3 files in My downloads folder

PHP Code:
DFL61_HARMATTAN_40.2012.21-3_PR_LEGACY_006-OEM1-958_ARM.bin
DFL61_HARMATTAN_22.2011.44
-2_PR_LEGACY_006-OEM1-958_ARM.bin
E074DEA5_DFL61_HARMATTAN_30.2012.07
-1_PR_LEGACY_006-OEM1-958_ARM.bin
528DA068_DFL61_HARMATTAN_40.2012.13
-7.MEA_EMMC_MEA.bin 
 
Posts: 32 | Thanked: 7 times | Joined on Apr 2013
#47
So Geeks. No Solution ?
 
Posts: 131 | Thanked: 22 times | Joined on Sep 2012 @ India
#48
I have exactly same issue and you can refer to my posts in this thread.
http://talk.maemo.org/showthread.php...28#post1305428

I have made some progress by trying few things which you can see in latest posts in that thread.
I am still trying to find complete solution.
Please check if those posts help you in any way.
 
Posts: 32 | Thanked: 7 times | Joined on Apr 2013
#49
But I don't see any hint to track. Now I've started to think, its a hardware issue. and The problem is there is no way to make sure. where the problem is. as bootloader can pick up my imei correctly. and I can see it in /proc/cmdline.
 
Posts: 1,225 | Thanked: 1,905 times | Joined on Feb 2011 @ Quezon City, Philippines
#50
I think that at some point, firmware versions have been mismatched on-device.

Using the PR_LEGACY 006 firmware, add "--flash-only=rootfs" to the end of that command line, and on the second run to flash the eMMC, remember to have "--flash-only=emmc".

Don't reboot yet.

Now download the PR1.3 PR_LEGACY 280 rootfs, and "--flash-only=cmt-mcusw".

You should now have a device with PR1.3 006 on the APU, and PR1.3 280 on the MCU (and the MCU's swcert should match with the MCU firmware)

(IIRC mismatching APU and MCU firmware is allowed. In case you get a MALF, flash the PR1.3 Open Mode kernel and follow these instructions)
__________________
N9 PR 1.3 Open Mode + kernel-plus for Harmattan
@kenweknot, working on Glacier for Nemo.

Last edited by Hurrian; 2013-05-14 at 00:47.
 
Reply

Thread Tools

 
Forum Jump


All times are GMT. The time now is 21:31.