MfgTool doesn't find SABRESDB

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

MfgTool doesn't find SABRESDB

Jump to solution
2,269 Views
garythompson
Contributor I

 

I am trying to send an image to the SD card on an SABRE SDB.  When I start MfgTool2, it says there is no device connected.  Device manager shows some HIDs, but none are the SABRE. How do I make the system recognize the SABRE is there?

 

Original Attachment has been moved to: MfgTool.log.zip

Labels (1)
0 Kudos
Reply
1 Solution
1,704 Views
LeonardoSandova
Specialist I

You have to place your .img files on the 'android' folder (either the FSL demo ones or the ones you build), and make sure the xml fields are pointing to these ones. Also, there is a .ini on the root MFGtool, make sure you set there the correct profile. A SD with 4G is enough. The teraterm log does not show any error, so it is not quite useful this time. Also, take a look at the .log file, it is located also on the root folder, it may give you some hints about the problem. I am sorry not to help you to your specific problem, but at least you got more info for debugging.

View solution in original post

0 Kudos
Reply
6 Replies
1,704 Views
garythompson
Contributor I

I got windows to recognize the board by removing the SD card.  It then installed the driver and showed a new HID in device manager, but MfgTool2 still doesn't recognize it.  Is there a configuration file that needs to be modified to make this work?
When the board is booted with the SD card installed, it isn't recognized by windows.  Is there some preparation that needs to be performed on the SD card before it can be used?

0 Kudos
Reply
1,704 Views
garythompson
Contributor I

Editing the xml file has provided partial results.  MfgTool2 now attempts to transfer files to the board, but hangs at "Jumping to OS image".  Is there a xml file that works with this board?

0 Kudos
Reply
1,704 Views
garythompson
Contributor I

I have finally gotten MFGTool2 to write to the SABRESDB, but the result will not boot.

I deleted everything and started with a fresh install of "Mfgtools-Rel-1.1.0_121218_MX6Q_UPDATER.tar.gz".

The Android Quick Start Guide doesn't quite match the files in the distribution, so I am sure that some of the files used in my selection are wrong.

Can someone clarify which files should be used to load the SD card?

Since I can't see how full this card is, how big of a SD card is required to load the Android package?

0 Kudos
Reply
1,704 Views
LeonardoSandova
Specialist I

Hi garythompson

For Android, four files are needed: uImage, boot.img, system.img and recovery.img. I am not sure about the precise size of the SD card, for a 4G should be enough.

Could you please show the whole serial console log (the one produced while MFGTool)?

could you also show the xml profile?

Which Window version are you using? MFGTool has not been fully tested on 64 bits OS.

0 Kudos
Reply
1,704 Views
garythompson
Contributor I

I have four files with those names in the Android directory, but I am not sure they are the correct ones.

I am using a 4 Gb card, but the numbers in the terminal window look as if more is required.

I am using Win7 Ultimate.

I have attached the teraterm output.

0 Kudos
Reply
1,705 Views
LeonardoSandova
Specialist I

You have to place your .img files on the 'android' folder (either the FSL demo ones or the ones you build), and make sure the xml fields are pointing to these ones. Also, there is a .ini on the root MFGtool, make sure you set there the correct profile. A SD with 4G is enough. The teraterm log does not show any error, so it is not quite useful this time. Also, take a look at the .log file, it is located also on the root folder, it may give you some hints about the problem. I am sorry not to help you to your specific problem, but at least you got more info for debugging.

0 Kudos
Reply