skyline629
Member
Can I use the PCB 1.5 to flash the SB6120 modem?
BCUSB PCB 1.5 with SB6120
- Thread starter skyline629
- Start date
skyline629
Member
PCB 1.5 is able to do SPI on SB6120, but I can't get the SB6120 script to load. I was able to do it once but got mismatcs errors. Has anyone come accross this?
Here's my log:
Welcome to Blackcat interfacing software, USB version!
Running on: Microsoft Windows 7 Professional (64 bit)
Verify flash enabled
LibUsbDotNet version: 2.2.8.104
BlackcatUSB Script Engine running, build: 110
Device connected in SPI mode, firmware version: 1.09
Opening device in SPI Mode 0 (Fosc/2 MSB)
Flash detected: Spansion S25FL064 (8388608 bytes)
Programming mode: SPI (normal)
Device connected in SPI mode, firmware version: 1.09
Opening device in SPI Mode 0 (Fosc/2 MSB)
Flash detected: Spansion S25FL064 (8388608 bytes)
Programming mode: SPI (normal)
Loading script: SB6120.bcs
Button Hander::Calling Event: WriteFirmware
Address 0x43800: wrote 0xC5 and read 0xFF (19381 mismatches)
Address 0x42C00: wrote 0xE5 and read 0xFF (14541 mismatches)
Address 0x44100: wrote 0x8B and read 0xFF (12247 mismatches)
Address 0x50200: wrote 0xFA and read 0xFF (21911 mismatches)
Address 0x50100: wrote 0xC4 and read 0xFF (22556 mismatches)
Address 0x50000: wrote 0x1 and read 0xFF (22232 mismatches)
Address 0x60100: wrote 0xDE and read 0xFF (22681 mismatches)
Address 0x60100: wrote 0xDE and read 0xFF (20906 mismatches)
Address 0x60100: wrote 0xDE and read 0xFF (19372 mismatches)
Address 0x70200: wrote 0x90 and read 0xFF (21916 mismatches)
Address 0x70500: wrote 0xA5 and read 0xFF (16059 mismatches)
Address 0x70200: wrote 0x90 and read 0xFF (21742 mismatches)
Address 0x80100: wrote 0xF2 and read 0xFF (22502 mismatches)
Address 0x80100: wrote 0xF2 and read 0xFF (22677 mismatches)
Address 0x80200: wrote 0xC1 and read 0xFF (23444 mismatches)
Address 0x90600: wrote 0x89 and read 0xFF (23210 mismatches)
Address 0x90A00: wrote 0x84 and read 0xFF (23727 mismatches)
Address 0x90000: wrote 0x2 and read 0xFF (22181 mismatches)
Address 0xA0100: wrote 0x59 and read 0xFF (20848 mismatches)
Address 0xA0200: wrote 0x2A and read 0xFF (18360 mismatches)
Address 0xA0200: wrote 0x2A and read 0xFF (19111 mismatches)
Address 0xB0D00: wrote 0xE4 and read 0xFF (19529 mismatches)
Address 0xB0200: wrote 0xBB and read 0xFF (18641 mismatches)
Address 0xB0100: wrote 0xA6 and read 0xFF (20392 mismatches)
Address 0xC0000: wrote 0x1D and read 0xFF (23623 mismatches)
Address 0xC0000: wrote 0x1D and read 0xFF (24895 mismatches)
Address 0xC0000: wrote 0x1D and read 0xFF (24993 mismatches)
Address 0xD0100: wrote 0x89 and read 0xFF (26777 mismatches)
Address 0xD0100: wrote 0x89 and read 0xFF (25253 mismatches)
Address 0xD0000: wrote 0xF8 and read 0xFF (23208 mismatches)
Address 0xE0000: wrote 0x14 and read 0xFF (8925 mismatches)
Address 0xE0000: wrote 0x14 and read 0xFF (10459 mismatches)
Address 0xE0000: wrote 0x14 and read 0xFF (5870 mismatches)
Address 0xF0100: wrote 0x64 and read 0xFF (10059 mismatches)
Address 0xF0A00: wrote 0x88 and read 0xFF (11749 mismatches)
Address 0xF1000: wrote 0x87 and read 0xFF (6631 mismatches)
Address 0x100600: wrote 0xC2 and read 0xFF (4645 mismatches)
Address 0x103100: wrote 0x3 and read 0xFF (4076 mismatches)
Address 0x100D00: wrote 0xA1 and read 0xFF (4692 mismatches)
Address 0x111600: wrote 0x45 and read 0xFF (4397 mismatches)
Address 0x110600: wrote 0x55 and read 0xFF (4968 mismatches)
Address 0x110400: wrote 0x12 and read 0xFF (5020 mismatches)
Address 0x120800: wrote 0xDF and read 0xFF (3837 mismatches)
Address 0x120A00: wrote 0xD7 and read 0xFF (4326 mismatches)
Address 0x120800: wrote 0xDF and read 0xFF (2476 mismatches)
Address 0x132600: wrote 0xAD and read 0xFF (1330 mismatches)
Address 0x132600: wrote 0xAD and read 0xFF (2248 mismatches)
Address 0x130200: wrote 0xF0 and read 0xFF (1023 mismatches)
Address 0x140100: wrote 0x77 and read 0xFF (1438 mismatches)
Address 0x143100: wrote 0xD4 and read 0xFF (1277 mismatches)
Address 0x141300: wrote 0x10 and read 0xFF (1277 mismatches)
Address 0x150300: wrote 0xE1 and read 0xFF (2297 mismatches)
Address 0x151300: wrote 0x1E and read 0xFF (1275 mismatches)
Address 0x153200: wrote 0xA6 and read 0xFF (1532 mismatches)
Address 0x169E00: wrote 0xB7 and read 0xFF (1022 mismatches)
Address 0x166600: wrote 0x4A and read 0xFF (1277 mismatches)
Address 0x160400: wrote 0xB3 and read 0xFF (1278 mismatches)
Address 0x170600: wrote 0x6A and read 0xFF (1015 mismatches)
Address 0x179000: wrote 0xFE and read 0xFF (510 mismatches)
Address 0x171900: wrote 0xE4 and read 0xFF (1020 mismatches)
Address 0x183100: wrote 0x57 and read 0xFF (254 mismatches)
Address 0x183900: wrote 0x2 and read 0xFF (253 mismatches)
Address 0x19C000: wrote 0xCB and read 0xFF (511 mismatches)
Address 0x192500: wrote 0xDF and read 0xFF (511 mismatches)
Address 0x1A8200: wrote 0xC7 and read 0xFF (255 mismatches)
Address 0x1AF500: wrote 0xC and read 0xFF (256 mismatches)
Address 0x1A1500: wrote 0x2F and read 0xFF (1042 mismatches)
Address 0x1C2500: wrote 0x16 and read 0xFF (255 mismatches)
Address 0x1DFA00: wrote 0xBB and read 0xFF (255 mismatches)
Address 0x1D2500: wrote 0xAE and read 0xFF (510 mismatches)
Address 0x1D2C00: wrote 0x5 and read 0xFF (255 mismatches)
Address 0x200300: wrote 0x52 and read 0xFF (254 mismatches)
Sucessfully flashed 3670016 bytes
Here's my log:
Welcome to Blackcat interfacing software, USB version!
Running on: Microsoft Windows 7 Professional (64 bit)
Verify flash enabled
LibUsbDotNet version: 2.2.8.104
BlackcatUSB Script Engine running, build: 110
Device connected in SPI mode, firmware version: 1.09
Opening device in SPI Mode 0 (Fosc/2 MSB)
Flash detected: Spansion S25FL064 (8388608 bytes)
Programming mode: SPI (normal)
Device connected in SPI mode, firmware version: 1.09
Opening device in SPI Mode 0 (Fosc/2 MSB)
Flash detected: Spansion S25FL064 (8388608 bytes)
Programming mode: SPI (normal)
Loading script: SB6120.bcs
Button Hander::Calling Event: WriteFirmware
Address 0x43800: wrote 0xC5 and read 0xFF (19381 mismatches)
Address 0x42C00: wrote 0xE5 and read 0xFF (14541 mismatches)
Address 0x44100: wrote 0x8B and read 0xFF (12247 mismatches)
Address 0x50200: wrote 0xFA and read 0xFF (21911 mismatches)
Address 0x50100: wrote 0xC4 and read 0xFF (22556 mismatches)
Address 0x50000: wrote 0x1 and read 0xFF (22232 mismatches)
Address 0x60100: wrote 0xDE and read 0xFF (22681 mismatches)
Address 0x60100: wrote 0xDE and read 0xFF (20906 mismatches)
Address 0x60100: wrote 0xDE and read 0xFF (19372 mismatches)
Address 0x70200: wrote 0x90 and read 0xFF (21916 mismatches)
Address 0x70500: wrote 0xA5 and read 0xFF (16059 mismatches)
Address 0x70200: wrote 0x90 and read 0xFF (21742 mismatches)
Address 0x80100: wrote 0xF2 and read 0xFF (22502 mismatches)
Address 0x80100: wrote 0xF2 and read 0xFF (22677 mismatches)
Address 0x80200: wrote 0xC1 and read 0xFF (23444 mismatches)
Address 0x90600: wrote 0x89 and read 0xFF (23210 mismatches)
Address 0x90A00: wrote 0x84 and read 0xFF (23727 mismatches)
Address 0x90000: wrote 0x2 and read 0xFF (22181 mismatches)
Address 0xA0100: wrote 0x59 and read 0xFF (20848 mismatches)
Address 0xA0200: wrote 0x2A and read 0xFF (18360 mismatches)
Address 0xA0200: wrote 0x2A and read 0xFF (19111 mismatches)
Address 0xB0D00: wrote 0xE4 and read 0xFF (19529 mismatches)
Address 0xB0200: wrote 0xBB and read 0xFF (18641 mismatches)
Address 0xB0100: wrote 0xA6 and read 0xFF (20392 mismatches)
Address 0xC0000: wrote 0x1D and read 0xFF (23623 mismatches)
Address 0xC0000: wrote 0x1D and read 0xFF (24895 mismatches)
Address 0xC0000: wrote 0x1D and read 0xFF (24993 mismatches)
Address 0xD0100: wrote 0x89 and read 0xFF (26777 mismatches)
Address 0xD0100: wrote 0x89 and read 0xFF (25253 mismatches)
Address 0xD0000: wrote 0xF8 and read 0xFF (23208 mismatches)
Address 0xE0000: wrote 0x14 and read 0xFF (8925 mismatches)
Address 0xE0000: wrote 0x14 and read 0xFF (10459 mismatches)
Address 0xE0000: wrote 0x14 and read 0xFF (5870 mismatches)
Address 0xF0100: wrote 0x64 and read 0xFF (10059 mismatches)
Address 0xF0A00: wrote 0x88 and read 0xFF (11749 mismatches)
Address 0xF1000: wrote 0x87 and read 0xFF (6631 mismatches)
Address 0x100600: wrote 0xC2 and read 0xFF (4645 mismatches)
Address 0x103100: wrote 0x3 and read 0xFF (4076 mismatches)
Address 0x100D00: wrote 0xA1 and read 0xFF (4692 mismatches)
Address 0x111600: wrote 0x45 and read 0xFF (4397 mismatches)
Address 0x110600: wrote 0x55 and read 0xFF (4968 mismatches)
Address 0x110400: wrote 0x12 and read 0xFF (5020 mismatches)
Address 0x120800: wrote 0xDF and read 0xFF (3837 mismatches)
Address 0x120A00: wrote 0xD7 and read 0xFF (4326 mismatches)
Address 0x120800: wrote 0xDF and read 0xFF (2476 mismatches)
Address 0x132600: wrote 0xAD and read 0xFF (1330 mismatches)
Address 0x132600: wrote 0xAD and read 0xFF (2248 mismatches)
Address 0x130200: wrote 0xF0 and read 0xFF (1023 mismatches)
Address 0x140100: wrote 0x77 and read 0xFF (1438 mismatches)
Address 0x143100: wrote 0xD4 and read 0xFF (1277 mismatches)
Address 0x141300: wrote 0x10 and read 0xFF (1277 mismatches)
Address 0x150300: wrote 0xE1 and read 0xFF (2297 mismatches)
Address 0x151300: wrote 0x1E and read 0xFF (1275 mismatches)
Address 0x153200: wrote 0xA6 and read 0xFF (1532 mismatches)
Address 0x169E00: wrote 0xB7 and read 0xFF (1022 mismatches)
Address 0x166600: wrote 0x4A and read 0xFF (1277 mismatches)
Address 0x160400: wrote 0xB3 and read 0xFF (1278 mismatches)
Address 0x170600: wrote 0x6A and read 0xFF (1015 mismatches)
Address 0x179000: wrote 0xFE and read 0xFF (510 mismatches)
Address 0x171900: wrote 0xE4 and read 0xFF (1020 mismatches)
Address 0x183100: wrote 0x57 and read 0xFF (254 mismatches)
Address 0x183900: wrote 0x2 and read 0xFF (253 mismatches)
Address 0x19C000: wrote 0xCB and read 0xFF (511 mismatches)
Address 0x192500: wrote 0xDF and read 0xFF (511 mismatches)
Address 0x1A8200: wrote 0xC7 and read 0xFF (255 mismatches)
Address 0x1AF500: wrote 0xC and read 0xFF (256 mismatches)
Address 0x1A1500: wrote 0x2F and read 0xFF (1042 mismatches)
Address 0x1C2500: wrote 0x16 and read 0xFF (255 mismatches)
Address 0x1DFA00: wrote 0xBB and read 0xFF (255 mismatches)
Address 0x1D2500: wrote 0xAE and read 0xFF (510 mismatches)
Address 0x1D2C00: wrote 0x5 and read 0xFF (255 mismatches)
Address 0x200300: wrote 0x52 and read 0xFF (254 mismatches)
Sucessfully flashed 3670016 bytes
skyline629
Member
I am having another problem using PCB 1.5, SPI 1.09, lastest version 304. I've tried many times on different computers and getting same problem. The SB6120.bcs tab won't load. This is my fifth computer and no go. Here's my log.
LibUsbDotNet version: 2.2.8.104
BlackcatUSB Script Engine running, build: 200
Welcome to BlackcatUSB interfacing software, build: 304
Running on: Microsoft Windows XP Professional (32 bit)
Device connected in SPI mode, firmware version: 1.09
Opening device in SPI Mode 0 (Fosc/2 MSB)
Connected to Flash (JEDEC: 01 0216)
Flash detected: Spansion S25FL064 (8388608 bytes)
Programming mode: SPI (high-speed)
Loading script: SB6120_SPI.bcs
Flash data does not contain proper firmware format
LibUsbDotNet version: 2.2.8.104
BlackcatUSB Script Engine running, build: 200
Welcome to BlackcatUSB interfacing software, build: 304
Running on: Microsoft Windows XP Professional (32 bit)
Device connected in SPI mode, firmware version: 1.09
Opening device in SPI Mode 0 (Fosc/2 MSB)
Connected to Flash (JEDEC: 01 0216)
Flash detected: Spansion S25FL064 (8388608 bytes)
Programming mode: SPI (high-speed)
Loading script: SB6120_SPI.bcs
Flash data does not contain proper firmware format
The script will not load due to the fact that your firmware is corrupt
Flash data does not contain proper firmware format
Try using the SPI flash tab to reload your full 8MB or use the VMG300 script as it has the same layout as a 6120. One you have rectified your modem the 6120 script will load
Flash data does not contain proper firmware format
Try using the SPI flash tab to reload your full 8MB or use the VMG300 script as it has the same layout as a 6120. One you have rectified your modem the 6120 script will load
skyline629
Member
I have reloaded the full 8MB dump form SBH that I download. But still can't load the script. Same issue. Maybe the 8MB dump is corrupted. I will try to download another one.
skyline629
Member
How long does it take to load the 8mb dump. It's writting at 14kbs. Is this normal? I'm using another 8mb dump.
skyline629
Member
Okay. I'm still trying to flash the 8mb dump, but still having problems. If check the verify option when writting the flash. I get mismatches and fail message. If I uncheck the verify option, then it writes fine. After, I was able to load the Sb6120 script. When I got the tab there's read and write. So I began to write and select forceware. It wrote fine. when it was complete. I reboot modem, but the lights on modem are all on, but dim. I can't seem to get the modem back to factory. Here's my log. Thanks D3mOn for your support.
LibUsbDotNet version: 2.2.8.104
BlackcatUSB Script Engine running, build: 200
Welcome to BlackcatUSB interfacing software, build: 303
Running on: Microsoft Windows 7 Home Premium (32 bit)
Device connected in SPI mode, firmware version: 1.09
Opening device in SPI Mode 0 (Fosc/2 MSB)
Connected to Flash (JEDEC: 01 0216)
Flash detected: Spansion S25FL064 (8388608 bytes)
Programming mode: SPI (high-speed)
Loading script: VMG300_SPI.bcs
Flash data does not contain proper firmware format
Opened file for writing: mine fullback6120 002374f4b759.bin (binary format), total size: 8,388,608 bytes
Write Flash operation complete
8388608 bytes written in 32.348 seconds, 259,324 Bytes/s
Script file (VMG300_SPI.bcs) unloaded
Opening device in SPI Mode 0 (Fosc/2 MSB)
Connected to Flash (JEDEC: 01 0216)
Flash detected: Spansion S25FL064 (8388608 bytes)
Programming mode: SPI (high-speed)
Loading script: SB6120_SPI.bcs
Button Hander::Calling Event: WriteFirmware
Write Flash operation complete
3670016 bytes written in 16.596 seconds, 221,139 Bytes/s
Sucessfully programmed 3670016 bytes
Button Hander::Calling Event: Done
LibUsbDotNet version: 2.2.8.104
BlackcatUSB Script Engine running, build: 200
Welcome to BlackcatUSB interfacing software, build: 303
Running on: Microsoft Windows 7 Home Premium (32 bit)
Device connected in SPI mode, firmware version: 1.09
Opening device in SPI Mode 0 (Fosc/2 MSB)
Connected to Flash (JEDEC: 01 0216)
Flash detected: Spansion S25FL064 (8388608 bytes)
Programming mode: SPI (high-speed)
Loading script: VMG300_SPI.bcs
Flash data does not contain proper firmware format
Opened file for writing: mine fullback6120 002374f4b759.bin (binary format), total size: 8,388,608 bytes
Write Flash operation complete
8388608 bytes written in 32.348 seconds, 259,324 Bytes/s
Script file (VMG300_SPI.bcs) unloaded
Opening device in SPI Mode 0 (Fosc/2 MSB)
Connected to Flash (JEDEC: 01 0216)
Flash detected: Spansion S25FL064 (8388608 bytes)
Programming mode: SPI (high-speed)
Loading script: SB6120_SPI.bcs
Button Hander::Calling Event: WriteFirmware
Write Flash operation complete
3670016 bytes written in 16.596 seconds, 221,139 Bytes/s
Sucessfully programmed 3670016 bytes
Button Hander::Calling Event: Done
Attachments
skyline629
Member
The lights on the modem looks like a bad flash again. For some reason I can't seem to fix that problem. Everything I've done so far and still same problem with the modem. I think it's not writting correctly. If connection was not correct, then It won't be able to detech flash from modem, correct? I'm running out of options. Maybe I should just solder the pins and don't use the test clip.
Update: When not using the power supply and powering the chip from BCUSB. I'm able to read flash, but not correct one (listed below). When connecting BCUSB to modem R362 and using power supply. It detects flash chip. It needs power supply and R362 connected to read flash. Is this normal? Do I need external power on pin 2 also? Here's my log.
LibUsbDotNet version: 2.2.8.104
BlackcatUSB Script Engine running, build: 200
Welcome to BlackcatUSB interfacing software, build: 303
Running on: Microsoft Windows 7 Home Premium (32 bit)
Device connected in SPI mode, firmware version: 1.09
Opening device in SPI Mode 0 (Fosc/2 MSB)
Connected to Flash (JEDEC: 83 BFBF)
For read write support email contact@embeddedcomputers.net with JEDEC ID
Device connected in SPI mode, firmware version: 1.09
Opening device in SPI Mode 0 (Fosc/2 MSB)
Connected to Flash (JEDEC: BF BFBF)
For read write support email contact@embeddedcomputers.net with JEDEC ID
Device connected in SPI mode, firmware version: 1.09
Opening device in SPI Mode 0 (Fosc/2 MSB)
Connected to Flash (JEDEC: 89 BBBB)
For read write support email contact@embeddedcomputers.net with JEDEC ID
Device connected in SPI mode, firmware version: 1.09
Opening device in SPI Mode 0 (Fosc/2 MSB)
Connected to Flash (JEDEC: 8B BBBB)
For read write support email contact@embeddedcomputers.net with JEDEC ID
Device connected in SPI mode, firmware version: 1.09
Opening device in SPI Mode 0 (Fosc/2 MSB)
Connected to Flash (JEDEC: BF BFBF)
For read write support email contact@embeddedcomputers.net with JEDEC ID
Update: When not using the power supply and powering the chip from BCUSB. I'm able to read flash, but not correct one (listed below). When connecting BCUSB to modem R362 and using power supply. It detects flash chip. It needs power supply and R362 connected to read flash. Is this normal? Do I need external power on pin 2 also? Here's my log.
LibUsbDotNet version: 2.2.8.104
BlackcatUSB Script Engine running, build: 200
Welcome to BlackcatUSB interfacing software, build: 303
Running on: Microsoft Windows 7 Home Premium (32 bit)
Device connected in SPI mode, firmware version: 1.09
Opening device in SPI Mode 0 (Fosc/2 MSB)
Connected to Flash (JEDEC: 83 BFBF)
For read write support email contact@embeddedcomputers.net with JEDEC ID
Device connected in SPI mode, firmware version: 1.09
Opening device in SPI Mode 0 (Fosc/2 MSB)
Connected to Flash (JEDEC: BF BFBF)
For read write support email contact@embeddedcomputers.net with JEDEC ID
Device connected in SPI mode, firmware version: 1.09
Opening device in SPI Mode 0 (Fosc/2 MSB)
Connected to Flash (JEDEC: 89 BBBB)
For read write support email contact@embeddedcomputers.net with JEDEC ID
Device connected in SPI mode, firmware version: 1.09
Opening device in SPI Mode 0 (Fosc/2 MSB)
Connected to Flash (JEDEC: 8B BBBB)
For read write support email contact@embeddedcomputers.net with JEDEC ID
Device connected in SPI mode, firmware version: 1.09
Opening device in SPI Mode 0 (Fosc/2 MSB)
Connected to Flash (JEDEC: BF BFBF)
For read write support email contact@embeddedcomputers.net with JEDEC ID
skyline629
Member
Update: I know can load the SB6120 scritp and write. I flashed my chip with forceware. when I hook it up to my computer. my lights on modem is still the same and the 192.168.100.1 doesn't work either. I loaded another scritp on BCUSB VMG300. There are a few options here and I want to know which option I can choose to restore my 8mb dump back to the modem? Here's the screenshot. Thanks,
Attachments
To restore the full 8MB dump you do not use the script , you have to load it on the SPI Flash tab , using a clip is ok at times , but they do tend to be a pain in the ass .
Do this :
1. connect your modem using the ISP point.
2 Start everything up , so that modem has no LED's and the software detects your Flash
3 Do NOT load any script
4 goto the SPI Flash tab and write your 8MB dump
Let me know the results.
Do this :
1. connect your modem using the ISP point.
2 Start everything up , so that modem has no LED's and the software detects your Flash
3 Do NOT load any script
4 goto the SPI Flash tab and write your 8MB dump
Let me know the results.
skyline629
Member
Ok. I've loaded the 8MB dump and it's detecting my flash now. The only way it works by connecting VCC of BCUSB to back of modem R362 and an external usb 5V to power the chip. No power supply is needed. Also I can load the SB6120 script too.
skyline629
Member
I think something is wrong with my modem. I still have all the lights on when I plug the power supply. It's Dim and it doesn't go away. Is this normal or my flash chip is almost fired?
skyline629
Member
Ok. Here's is the dump.
skyline629
Member
Do you know where i can download a good copy. Most of my downloads are at SBH.