none
NK.bin is not booting RRS feed

  • Question

  • Hi All,

    I want to use my USB OTG port for connecting it to GPRS as serial port.

    For the same I have reffed the following link,

    http://www.e-consystems.com/gprs.asp.

    After doing the changes as mentioned in above link I was getting a error like "Port is busy"

    To solve this I have checked the following link,

    http://us.generation-nt.com/answer/gsm-gprs-using-dial-up-help-39908542.html#r

    In which they are telling me to change a file which is in Private(Drive:\WINCE600\PRIVATE\WINCEOS\COMM\TAPI\UNIMODEM\dial.c)

    When I have see this path, the COMM was excluded from the Build.

    I have done the following,

    1.Included COMM it in the build.

    2.Made changes to INIT_WATCHDOG_TIMEOUT as 40000 from 4000.

    3.Build that dll(UNIMODEM.dll) by giving the command sysgen unimodem in build window.

    4.Done make run time image.

    5.The image which was booting initially now its not booting.

    Paltform.reg file entries are as follows------------->

    [HKEY_LOCAL_MACHINE\Drivers\BuiltIn\COM2]
       "DeviceArrayIndex"=dword:0
       "IoBase"=dword:73FC0000
       "IoLen"=dword:D4
       "Prefix"="COM"
       "Dll"="csp_serial.dll"
       "Index"=dword:2
       "Order"=dword:4
    [HKEY_LOCAL_MACHINE\Drivers\BuiltIn\COM2\Unimodem]
       "Tsp"="Unimodem.dll"
       "DeviceType"=dword:0
       "FriendlyName"="3-STACK COM2 UNIMODEM"
       "DevConfig"=hex: 10,00, 00,00, 05,00,00,00, 10,01,00,00, 00,4B,00,00, 00,00, 08, 00, 00, 00,00,00,00

    [HKEY_LOCAL_MACHINE\ExtModems\HayesCompat]
       "Port"="COM2:"
       "DeviceType"=dword:1
       "FriendlyName"="Hayes Compatible on COM2:"
      ; "Hayes Compatible on COM4:"
       ;"FriendlyName"="GSM/GPRS Driver"

    [HKEY_LOCAL_MACHINE\ExtModems\ExtModems\Init]
        "1"="AT<cr>"
        "2"="ATE0V1&C1&D2<cr>"

    [HKEY_LOCAL_MACHINE\Drivers\Unimodem\Init]
        "1"="AT<cr>"
        "2"="ATE0V1&C1&D2<cr>"

    [HKEY_LOCAL_MACHINE\Drivers\Unimodem\Settings]
        "Prefix"="AT"
        "Terminator"="<cr>"
        "DialPrefix"="D"
        "DialSuffix"=";"
        "Pulse"="P"
        ;"Tone"="T"
        ;"Tone"="T"
        "Tone"=""
        "Blind_Off"="X4"
        "Blind_On"="X3"
        "CmdSendDelay"="500"
        "CallSetupFailTimeout"="ATS7=<#><cr>"
        "Reset"="AT<cr>"
            "MdmLogFile" = dword:1
        
    [HKEY_LOCAL_MACHINE\Drivers\Unimodem\Config]
        "CallSetupFailTimer"=dword:B4

    ; Location Settings

    [HKEY_CURRENT_USER\ControlPanel\Dial]

    ; What is Location ID (value name) for the current location
        "CurrentLoc"=dword:0
    ; What is the next permanent location ID to be used when creating a new entry
        "HighLocID"=dword:2

    ;Default Location settings -- need to be localized

    [HKEY_CURRENT_USER\ControlPanel\Dial\Locations]

    ; Each MultiSz location (value name = PermLocationID" has :

    ; LocationName, LocalFmt, LdFmt, IntntlFmt, AreaCode, CwCode, CountryCode, &
    ;Options
        "0"=multi_sz: "Work",
        "G",
        "G",
        "G",
        "425",
        " ",
        "1",
        "0"
        "1"=multi_sz: "Home",
        "G",
        "1FG",
        "011,EFG",
        "425",
        " ",
        "1",
        "0"

    Let me know how I can solve this issue??

    Thanks in advance.

    With Thanks

    nadini

    Wednesday, March 20, 2013 11:45 AM

All replies

  • Remove all the changes and add one by one ... then it will be easy to know what is causing the problem ?

    --- Misbah


    Senior Design Engineer T.E.S Electroni Solutions (Bangalore-India) www.tes-dst.com email-misbah.khan@tes-dst.com

    Thursday, March 21, 2013 5:02 AM
  • Hi Misbha,

    Thanks for the reply.

    Please can you verify the platform.reg file changes.

    The image stared giving problem when I have changed the file which is in Private(Drive:\WINCE600\PRIVATE\WINCEOS\COMM\TAPI\UNIMODEM\dial.c)

    When I have seen this path, the COMM was excluded from the Build.

    I have done the following,

    1.Included COMM it in the build.

    2.Made changes to INIT_WATCHDOG_TIMEOUT as 40000 from 4000.

    3.Build that dll(UNIMODEM.dll) by giving the command sysgen unimodem in build window.

    4.Done make run time image.

    5.The image which was booting initially now its not booting.

    Then to cross verify I have reverted the above but still image in not booting.

    Please let me know what I can try.

    With Thanks

    nadini

    Thursday, March 21, 2013 5:47 AM
  • The changes in the .reg file looks ok ....

    You can comment just to be sure that it is not creating any issue ... ant try .

    Changing INIT_WATCHDOG_TIMEOUT as 40000 from 4000 is OK ...

    But "Included COMM it in the build " How and why ?

    When you reverted back the change did you saw unimodem dll is getting updated ?

    --- Misbah


    Senior Design Engineer T.E.S Electroni Solutions (Bangalore-India) www.tes-dst.com email-misbah.khan@tes-dst.com

    Thursday, March 21, 2013 6:09 AM
  • Ok.I will try by commenting the changes in Platform.reg file.

    When I have opened the file dial.c from following path,

    Drive:\WINCE600\PRIVATE\WINCEOS\COMM\TAPI\UNIMODEM\dial.c.

    I have seen that the COMM was excluded from BUILD I don't know Why is it so.

    I have included the same in the build and changed the timeout from 4000 to 40000.

    Yes.I have seen the dll is getting updated.

    I know that SYSGEN is not going to help me as the changed file is in PRIVATE.But Still I have tried this option as well.

    With Thanks

    nadini

    Thursday, March 21, 2013 6:56 AM