ADK3.5 BlueFlash.exe Segmentation fault and can't found device.

[lorf]

ADK3.5 BlueFlash.exe Segmentation fault and can't found device.

[lorf]

Hi! Do You have permissions for FTDI device? It should be set up in udev config, like this:

cat <<_EOT_ | sudo tee -a /etc/udev/rules.d/99-ftdi.rules
# FT232RL
SUBSYSTEM=="usb", ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6001", MODE="0660", GROUP="plugdev"
_EOT_
sudo usermod -a -G plugdev `id -un`

You will need to relogin or run commands under "newgrp plugdev" for user change to take effect.

[lorf]

Can You also post output of lsusb and output of the following command?

env FTDI_LOG_LEVEL=debug wine /path/to/BlueFlashCmd.exe -chipver

[LuoZhongYao]

i' m sorry.I uninstalled this environment, the use of virtual machines to
run blueflsah.

2015-04-16 20:46 GMT+08:00 lorf [email protected]:

Can You also post output of lsusb and output of the following command?

env FTDI_LOG_LEVEL=debug wine /path/to/BlueFlashCmd.exe -chipver

—
Reply to this email directly or view it on GitHub
#3 (comment).

[LuoZhongYao]

This is one of my mistakes, I am using a USB <=> SPI device instead FTDI
device.

2015-04-17 8:46 GMT+08:00 一二 [email protected]:

i' m sorry.I uninstalled this environment, the use of virtual machines to
run blueflsah.

2015-04-16 20:46 GMT+08:00 lorf [email protected]:

Can You also post output of lsusb and output of the following command?

env FTDI_LOG_LEVEL=debug wine /path/to/BlueFlashCmd.exe -chipver

—
Reply to this email directly or view it on GitHub
#3 (comment).

[lorf]

OK. I'll investigate the segfault, thanks for reporting!

[Makcumus]

Sorry for offtop.
FTDI in new driver reset PID of non original (chinese) chips 232R to 0000, and i think it will be usefull add to lib this PID, or notes in manual. Of course it easy to return PID back by using FTDI`s MProg. Have a nice day.

[lorf]

Thanks, @Makcumus. I'll look into it.

[Makcumus]

Good day.

Also using Mprog 3.5 for FTDI232R you must set options:

1. bus powered current 500ma
2. I/o high current
   Else you get error -> cant stop processor 
   And Dll v1.4 is not working with BlueSuite 2.6.0 on WIN7 x64 - programm error.
   It looks like, that there is no enough current from some USB (for some PC it is 500ma only in some it more than 1Amp), may be it will be usefull to use external power (and\or self powered option in Mprog). In my case i use double USB cable.

Среда, 12 августа 2015, 9:38 -07:00 от lorf [email protected]:

Thanks, @Makcumus . I'll look into it.
—
Reply to this email directly or view it on GitHub .

С уважением,
m m
[email protected]

[DJ-URAN]

Confirm. 1.4v dll not work in bluesuite 2.6.0 (and 2.5.8 also).
I use this dll with BlueLab 4.1 with no connection problems.

[lorf]

@Makcumus @DJ-URAN Can you please show the debug output of the command producing error? Assuming it is run on Windows:
set FTDI_LOG_LEVEL=debug
blueflashcmd -dump test (or anything producing an error)

[lorf]

I tried but cannot reproduce error in BlueSuite 2.5.8 and 2.6.0 with api1.4 dll from csr-spi-ftdi-0.4.2, counterfeit FT232RL chip and HC05 module. Tried in Win7/x32 on a VM and in Win8/x64 on real HW.

@Makcumus @DJ-URAN - can You help me with this? Please try to reproduce the error with command like this:

blueflashcmd -trans "SPIDEBUG=ON SPIDEBUG_FILE=c:\temp\debug.log" -dump test

and send resulting log to [email protected]

[lorf]

Other things to try:

• Lower FTDI_BASE_CLOCK, e.g. set in environment:

  set FTDI_BASE_CLOCK=1000000

• Lower resistor values in SPI lines

• Switch to WinUSB driver in Zadig

[lorf]

@Makcumus WRT USB bus current, AFAIK most motherboards just ignore the MaxPower setting of USB device and supply as much current as they can. Simple setup with FT232RL and HC05 module should not draw more than 150mA, so it shouldn't be an issue.

Issue may arise if You power HC05 from FT232R internal 3.3V regulator. Current consumption will rise on flash write operations, and it may exceed FT232R 50mA limit.

[DJ-URAN]

lorf, to help you, should i install CSR drivers first (for DFU) and then try your command in cmd? Should i switch first my FTDI driver to WinUSB in Zadig?

[lorf]

No, please, don't install CSR USB drivers, and select LPT (not USB) transport at installation time, otherwise You'll need to specify "-LPT 1" option on command line.

You may try with libusbK driver first and if error occurs, try to switch to WinUSB.

[DJ-URAN]

lorf! I tried make dump in blueflashcmd, but it give me ERROR: not given for "-dump
maybe mistake in command?

[DJ-URAN]

PS: when i install bluesuite on my pc it said that LPT not supported for 64 bit systems (i have x64 windows)/

[lorf]

You need to supply a filename to the -dump option, like this:
blueflashcmd -dump somefilename
At the end You should get two files, somefilename.xpv and somefilename.xdv.

It's OK when BlueSuite complains about LPT on x64 systems, since we actually will not use LPT port nor LPT driver, but provide our own instead.

[DJ-URAN]

I try your command blueflashcmd -trans "SPIDEBUG=ON SPIDEBUG_FILE=c:\temp\debug.log" -dump test. It contains -dump TEST at the end. But nothing changed.

[lorf]

It looks like filename "TEST" is magic and doesn't work!

[lorf]

After debugging @DJ-URAN issue over email, we found the following:

1. Support for BlueCore 2 chips (BC212015 in particular) was dropped in BlueSuite 2.4. So the newest BlueSuite supporting BC2 is BlueSuite 2.3 (use spilpt.dll from csr-spi-ftdi-*/spilpt-*-api1.3 with it).

2. Communicating with BC2 over SPI requires lower SPI speeds. You may try:

   blueflashcmd -trans "SPITRANS=LPT SPIPORT=1 FTDI_BASE_CLOCK=400000" -identify
   

   and play with FTDI_BASE_CLOCK. Default for FTDI_BASE_CLOCK in csr-spi-ftdi-0.4.2 is 4000000. For @DJ-URAN the following command from BlueSuite 2.3 with csr-spi-ftdi-0.4.2/spilpt-win32-api1.3/spilpt.dll worked:

   blueflashcmd -trans "SPITRANS=LPT SPIPORT=1 FTDI_BASE_CLOCK=400000" -dump test1
   

[lorf]

Looks like all problems were addressed so I'm closing it