Dead Sagem - Page 2

renwich · 28-02-2010, 10:46 AM

Ok so I was trying to send file not send text file

sending text file I get the following on the hyperterminal screen

Quote:

S32000000000000000000000000000000000001A
unrecognized command SS32000000000000000000000000000000000001A, args[0][0] 0x53
dbox2:root> S0000000000000000000000000000000000000000000000000 00000000090550018903500007EA1AB789A400000000000000 00000000000000000000000000000000000000000000000000 080
unrecognized command S0000000000000000000000000000000000000000000000000 00000000090550018903500007EA1AB789A400000000000000 00000000000000000000000000000000000000000000000000 080, args[0][0] 0x53
dbox2:root> S1247C0004AC4C00012C8041009C800100A07C4903A63F
unrecognized command S1247C0004AC4C00012C8041009C800100A07C4903A63F, args[0][0] 0x53
dbox2:root> S880E1002C8101003081210034814100388161003C81810040 81A100441B
unrecognized command S880E1002C8101003081210034814100388161003C81810040 81A100441B, args[0][0] 0x53
dbox2:root> S07078E7
unrecognized command S07078E7, args[0][0] 0x53
dbox2:root> SE800020058E07C0903A67FE4FB7838A000044E8004212C030 000907C000C41A2FBDC3800000096
unrecognized command SE800020058E07C0903A67FE4FB7838A000044E8004212C030 000907C000C41A2FBDC3800000096, args[0][0] 0x53
dbox2:root> S2418100302C16000041A2FBC0B7
unrecognized command S2418100302C16000041A2FBC0B7, args[0][0] 0x53
dbox2:root> S0107C0803A6382100184E80002000017B98A0
unrecognized command S0107C0803A6382100184E80002000017B98A0, args[0][0] 0x53
dbox2:root> S0801EFFEC3860FFFD7FC0F21441820034880400013929FFD0 2C00003A2F8900041C
unrecognized command S0801EFFEC3860FFFD7FC0F21441820034880400013929FFD0 2C00003A2F8900041C, args[0][0] 0x53
dbox2:root> S00184E8000209421FFE87C0802A693E1001014
unrecognized command S00184E8000209421FFE87C0802A693E1001014, args[0][0] 0x53
dbox2:root> SD635B17FC802A69001002C801EFFF07CBF2B7814
unrecognized command SD635B17FC802A69001002C801EFFF07CBF2B7814, args[0][0] 0x53
dbox2:root> S781B782C1F00023F20018040A10018807C00083880000038A 000104BFF1C950B
unrecognized command S781B782C1F00023F20018040A10018807C00083880000038A 000104BFF1C950B, args[0][0] 0x53
dbox2:root> S030000408200A07C004A14540028347C80C2143B2000107C9 F23783B9805003B4000077F83E37878
unrecognized command S030000408200A07C004A14540028347C80C2143B2000107C9 F23783B9805003B4000077F83E37878, args[0][0] 0x53
dbox2:root> S53C20367C00B850541F203608
unrecognized command S53C20367C00B850541F203608, args[0][0] 0x53
dbox2:root> SS32500018E207D29C214554A183881690400800905007D2AC 02E556B103A38E90080812100243E
unrecognized command SS32500018E207D29C214554A183881690400800905007D2AC 02E556B103A38E90080812100243E, args[0][0] 0x53
dbox2:root> S0226C00000000000000000000220740000000000000000000 0000000000001000000005B
unrecognized command S0226C00000000000000000000220740000000000000000000 0000000000001000000005B, args[0][0] 0x53
dbox2:root> S000000000000000000224AC0000007961
unrecognized command S000000000000000000224AC0000007961, args[0][0] 0x53
dbox2:root> S

LraiZer · 28-02-2010, 05:30 PM

i just ran through the serial flash myself to check it and everything worked fine.

what command is that after? you shouldnt be getting any of that. once you've connected hyperterminal via com port, and then started your dbox holding UP key you should just get

Code:

debug: DDF: Calibrating delay loop... debug: DDF: 67.79 BogoMIPS
debug: BMon V1.0  mID 01
debug: feID 7a    gtxID 0b
debug: fpID 5a     dsID 01-29.b7.19.07.00.00-d2
debug: HWrev X5  SWrev 0.81
debug: B/Ex/Fl(MB) 32/00/08
WATCHDOG reset enabled
debug: &_text 0x10000, &_etext 0x26160, &_data 0x26160, &_edata 0x29c50
debug: &_end 0x347dc,  &__stack 0x400000
debug: Memory tests (0x400000 -- 0x2000000)
debug: NumberTest: debug: passed
debug: MarchTest: debug: passed
debug: PermTest:  debug: passed
dbox2:root>

after you've send text file u-boot.mot the screen stays as is, until a short time later you get

Code:

dl: start address 0x800000
dbox2:root >

id start again, step by step

renwich · 28-02-2010, 06:05 PM

the errors start as soon as I try to send the file over, I've tried multiple times, and get the same error,

LraiZer · 28-02-2010, 06:20 PM

and you did put the u-boot.mot in C:\ didnt you?

renwich · 28-02-2010, 06:24 PM

yes I followed the guide to the letter, I'll start again from scratch

renwich · 28-02-2010, 07:11 PM

same thing

issued the dl 800000 command it comes back with "S Record Load, offset: 800000"

click transfer text file , select u-boot.mot from the c: drive , it then comes back with

Quote:

S32000000000000000000000000000000000001A
unrecognized command SS32000000000000000000000000000000000001A, args[0][0] 0x53
dbox2:root> S0000000000000000000000000000000000000000000000000 00000000090550018903500007EA1AB789A400000000000000 00000000000000000000000000000000000000000000000000 080
unrecognized command S0000000000000000000000000000000000000000000000000 00000000090550018903500007EA1AB789A400000000000000 00000000000000000000000000000000000000000000000000 080, args[0][0] 0x53
dbox2:root> S1247C0004AC4C00012C8041009C800100A07C4903A63F
unrecognized command S1247C0004AC4C00012C8041009C800100A07C4903A63F, args[0][0] 0x53
dbox2:root> S880E1002C8101003081210034814100388161003C81810040 81A100441B
unrecognized command S880E1002C8101003081210034814100388161003C81810040 81A100441B, args[0][0] 0x53
dbox2:root> S07078E7
unrecognized command S07078E7, args[0][0] 0x53
dbox2:root> SE800020058E07C0903A67FE4FB7838A000044E8004212C030 000907C000C41A2FBDC3800000096
unrecognized command SE800020058E07C0903A67FE4FB7838A000044E8004212C030 000907C000C41A2FBDC3800000096, args[0][0] 0x53
dbox2:root> S2418100302C16000041A2FBC0B7
unrecognized command S2418100302C16000041A2FBC0B7, args[0][0] 0x53
dbox2:root> S0107C0803A6382100184E80002000017B98A0
unrecognized command S0107C0803A6382100184E80002000017B98A0, args[0][0] 0x53
dbox2:root> S0801EFFEC3860FFFD7FC0F21441820034880400013929FFD0 2C00003A2F8900041C
unrecognized command S0801EFFEC3860FFFD7FC0F21441820034880400013929FFD0 2C00003A2F8900041C, args[0][0] 0x53
dbox2:root> S00184E8000209421FFE87C0802A693E1001014
unrecognized command S00184E8000209421FFE87C0802A693E1001014, args[0][0] 0x53
dbox2:root> SD635B17FC802A69001002C801EFFF07CBF2B7814
unrecognized command SD635B17FC802A69001002C801EFFF07CBF2B7814, args[0][0] 0x53
dbox2:root> S781B782C1F00023F20018040A10018807C00083880000038A 000104BFF1C950B
unrecognized command S781B782C1F00023F20018040A10018807C00083880000038A 000104BFF1C950B, args[0][0] 0x53
dbox2:root> S030000408200A07C004A14540028347C80C2143B2000107C9 F23783B9805003B4000077F83E37878
unrecognized command S030000408200A07C004A14540028347C80C2143B2000107C9 F23783B9805003B4000077F83E37878, args[0][0] 0x53
dbox2:root> S53C20367C00B850541F203608
unrecognized command S53C20367C00B850541F203608, args[0][0] 0x53
dbox2:root> SS32500018E207D29C214554A183881690400800905007D2AC 02E556B103A38E90080812100243E
unrecognized command SS32500018E207D29C214554A183881690400800905007D2AC 02E556B103A38E90080812100243E, args[0][0] 0x53
dbox2:root> S0226C00000000000000000000220740000000000000000000 0000000000001000000005B
unrecognized command S0226C00000000000000000000220740000000000000000000 0000000000001000000005B, args[0][0] 0x53
dbox2:root> S000000000000000000224AC0000007961
unrecognized command S000000000000000000224AC0000007961, args[0][0] 0x53
dbox2:root> S

LraiZer · 28-02-2010, 09:15 PM

well as a last resort before throwing it in trash, maybe try to flash a new BMon from another sagem with the same BMon version onto it. i read if it goes wrong your chips will be cooked

not sure if it can be done on a sagem, never tried it myself!

maybe pt-1 is the guy you should be asking as he posted some stickies a while back on unlocker about "New UBoot 1.1.6 for BMon reflashing"

PaphosAL · 01-03-2010, 07:47 AM

Renny- just a thought, m8, but are you connecting to a pc with a genuine RS232 9 pin Serial port? Or a USB-Serial adaptor?

Also, I take it that a null-modem crossover serial cable is essential for this task?

AL

Tyke · 01-03-2010, 03:09 PM

Just a thought .......
I see from the boot-log that it's "Transmitting BOOTP request via broadcast".

Have you tried booting from the network ( YADD), or is that a dumb question?

If you can get it up and running that way, you should be able to flash an image via Neutrino/Enigma in the "normal way".

It worked for me once when I couldn't get IFA to work after mucking about with LCARS .

Cheers!

28-02-2010, 05:30 PM	#12 (permalink)
LraiZer Developer UkCvs Senior Member Join Date: Oct 2008 Posts: 971 iTrader: (0) Casino cash: $312140 Thanks: 346 Thanked 1,622 Times in 731 Posts Nominated 19 Times in 7 Posts TOTW/F/M Award(s): 7 Groans: 0 Groaned at 0 Times in 0 Posts	i just ran through the serial flash myself to check it and everything worked fine. what command is that after? you shouldnt be getting any of that. once you've connected hyperterminal via com port, and then started your dbox holding UP key you should just get Code: debug: DDF: Calibrating delay loop... debug: DDF: 67.79 BogoMIPS debug: BMon V1.0 mID 01 debug: feID 7a gtxID 0b debug: fpID 5a dsID 01-29.b7.19.07.00.00-d2 debug: HWrev X5 SWrev 0.81 debug: B/Ex/Fl(MB) 32/00/08 WATCHDOG reset enabled debug: &_text 0x10000, &_etext 0x26160, &_data 0x26160, &_edata 0x29c50 debug: &_end 0x347dc, &__stack 0x400000 debug: Memory tests (0x400000 -- 0x2000000) debug: NumberTest: debug: passed debug: MarchTest: debug: passed debug: PermTest: debug: passed dbox2:root> after you've send text file u-boot.mot the screen stays as is, until a short time later you get Code: dl: start address 0x800000 dbox2:root > id start again, step by step

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

28-02-2010, 06:05 PM	#13 (permalink)
renwich Northern Git Admin Team-UkCvs Senior Member Join Date: Aug 2008 Posts: 5,098 iTrader: (0) Casino cash: $326674 Thanks: 1,126 Thanked 1,271 Times in 538 Posts Nominated 8 Times in 6 Posts TOTW/F/M Award(s): 4 Groans: 1 Groaned at 0 Times in 0 Posts	the errors start as soon as I try to send the file over, I've tried multiple times, and get the same error,

28-02-2010, 06:20 PM	#14 (permalink)
LraiZer Developer UkCvs Senior Member Join Date: Oct 2008 Posts: 971 iTrader: (0) Casino cash: $312140 Thanks: 346 Thanked 1,622 Times in 731 Posts Nominated 19 Times in 7 Posts TOTW/F/M Award(s): 7 Groans: 0 Groaned at 0 Times in 0 Posts	and you did put the u-boot.mot in C:\ didnt you?

28-02-2010, 06:24 PM	#15 (permalink)
renwich Northern Git Admin Team-UkCvs Senior Member Join Date: Aug 2008 Posts: 5,098 iTrader: (0) Casino cash: $326674 Thanks: 1,126 Thanked 1,271 Times in 538 Posts Nominated 8 Times in 6 Posts TOTW/F/M Award(s): 4 Groans: 1 Groaned at 0 Times in 0 Posts	yes I followed the guide to the letter, I'll start again from scratch

28-02-2010, 09:15 PM	#17 (permalink)
LraiZer Developer UkCvs Senior Member Join Date: Oct 2008 Posts: 971 iTrader: (0) Casino cash: $312140 Thanks: 346 Thanked 1,622 Times in 731 Posts Nominated 19 Times in 7 Posts TOTW/F/M Award(s): 7 Groans: 0 Groaned at 0 Times in 0 Posts	well as a last resort before throwing it in trash, maybe try to flash a new BMon from another sagem with the same BMon version onto it. i read if it goes wrong your chips will be cooked not sure if it can be done on a sagem, never tried it myself! maybe pt-1 is the guy you should be asking as he posted some stickies a while back on unlocker about "New UBoot 1.1.6 for BMon reflashing"

01-03-2010, 07:47 AM	#18 (permalink)
PaphosAL Nagging Old Git Team-UkCvs Senior Member Join Date: Aug 2008 Location: A park bench, near you Age: 75 Posts: 3,108 iTrader: (0) Casino cash: $848260 Thanks: 2,645 Thanked 1,586 Times in 876 Posts Nominated 2 Times in 2 Posts TOTW/F/M Award(s): 2 Groans: 1 Groaned at 0 Times in 0 Posts	Renny- just a thought, m8, but are you connecting to a pc with a genuine RS232 9 pin Serial port? Or a USB-Serial adaptor? Also, I take it that a null-modem crossover serial cable is essential for this task? AL

01-03-2010, 03:09 PM	#19 (permalink)
Tyke Developer UkCvs Senior Member Join Date: Oct 2008 Location: Yorkshire Posts: 132 iTrader: (0) Casino cash: $77960 Thanks: 426 Thanked 133 Times in 66 Posts Nominated 0 Times in 0 Posts TOTW/F/M Award(s): 0 Groans: 0 Groaned at 0 Times in 0 Posts	Just a thought ....... I see from the boot-log that it's "Transmitting BOOTP request via broadcast". Have you tried booting from the network ( YADD), or is that a dumb question? If you can get it up and running that way, you should be able to flash an image via Neutrino/Enigma in the "normal way". It worked for me once when I couldn't get IFA to work after mucking about with LCARS . Cheers!

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)