libftdi Archives

Subject: Issues porting libftdi-based application to MIPS platform

From: Victor Cionca <victor.cionca@xxxxxxxxxx>
To: "libftdi@xxxxxxxxxxxxxxxxxxxxxxx" <libftdi@xxxxxxxxxxxxxxxxxxxxxxx>
Date: Thu, 1 Aug 2013 08:20:51 +0000
Hi all,

I'm new here so please bear with me if I'm breaking any posting rules.

I ran into some problems running an FTDI application on a MIPS platform.

I have an embedded device using an Atmel microcontroller. The uC is 
programmed over SPI via an FTDI chip, using bit-banging.

I have an application that does the programming and it works well on my 
Linux machine (Kernel 3.2.0-0.bpo.4-686-pae, libftdi 1-1.0, libusb-1.0.16).

I cross-compiled the application (and the libftdi, confuse and libusb 
libraries) for a MIPS CPU, Atheros AR9330 (it's the TPLink MR3020 
router, running OpenWrt). Used the same libraries and the kernel is 3.3.8.

While the application runs fine (so it cross compiled well), it seems 
unable to communicate properly with the board. I send data and either 
get all zeroes or all FFs. I enabled usb debugging but the output is 
identical between the two machines - the only difference being in the 
usbi_handle_transfer_completion, with different addresses, but I guess 
that's normal.

I tried to lower the baudrate to 9600 but it still didn't work.
I did some analysis on the scope of the SPI clock and there is a 
difference between the Linux machine and the router.

Did anyone run into this kind of problem before? Is there any type of 
debugging that I could perform to help identify the issue?

Thanks and regards,
Victor
--
libftdi - see http://www.intra2net.com/en/developer/libftdi for details.
To unsubscribe send a mail to libftdi+unsubscribe@xxxxxxxxxxxxxxxxxxxxxxx

Current Thread