PDA

View Full Version : Problem uploading .mod file on a Brew 1 phone


erpor
07-20-2005, 08:16 AM
I'm working on an application made for a brew 2 phone. It compiles and I can install it on the phone (Samsung A650)
With small modifications, I was able to make it compile in Brew 1. I know it works on the emulator and I even tried it on the A650. Except a display problem, it works.

The problem I have is when I try to upload the .mod file to the Brew 1 devices (A530 or A610) I always get a "could not write to the device EFS" error. This doesn't seem to be a USB driver problem since I can install other applications (I tried installing a benchmark tool and it worked correctly). I am relatively new with Brew so I was wondering if there is not something obvious I'm missing! Is there a different header on the .mod file between brew 1 and brew 2? Is there a verification made when the .mod is installed on the phone?

Also, I'm using brew apploader 3.0 and at the start it asks me if my device is brew 2 or 3 (not 1). I asked some people I work with and they said they used brew 2 eeven if it's a brew 1 phone and since I was able to upload the benchmark tool using this configuration, I concluded it was working by selecting brew 2.

I used the right signature file, I tried creating a new mif file for Brew 1. Is there an option when compiling with Arm compiler that could create this problem. I tried rebooting the phone multiple times, including restarting the Brew Apploader and nothin works!

Thx a lot for your help!

erpor
07-20-2005, 09:08 AM
ok... looks like there is a 12 caracter limit for the name of your files on brew 1 devices (mine was 13 caracters)...

Skavenger
07-21-2005, 02:38 AM
Its not just some brew 1 phones that have this limit. There are lots of Brew 2 phones with the old 8+3 dos limit too.

max
07-25-2005, 07:43 PM
The name limits in BREW are based on the entire file path length. This should be documented in the DDS.