Activity
From 04/13/2012 to 05/12/2012
05/11/2012
- 12:23 PM Software Development: RE: Connecting JTAG to Mityarm board
- Hi Mike,
Yes, I am connecting to MityARM-3359 and not on TI eval board.
So i want to know what .gel file i need... - 10:43 AM Software Development: RE: Connecting JTAG to Mityarm board
- Hi Raja,
Were you successful when you tried connecting the JTAG to the TI eval board?
I am assuming you are c... - Hi,
I have tried connecting JTAG XDS100V2 to the Mityarm evaluation board. Changed the boot options to give first ...
05/07/2012
- 12:01 PM PCB Development: RE: Power Management w/ MityARM
- Mike,
Thanks for your response, it is really helpful to know how the PMIC is connected. I posted a question about... - 11:06 AM PCB Development: RE: Reg. JTAG Reset and SD Card connection
- Hi Salam,
Thanks for the comments.
1. There is a 10K pull down on the JTAG Reset line so that the JTAG interfac...
Hi,
As per the Mity carrier board design
1, the NRST of JTAG connector is permanently low,that means it is always...
05/04/2012
- 03:50 PM Software Development: RE: Usage of I2C1 to connect external peripheral
- Hi Mike,
Thanks for the information.
I will check on the details provided by you.
Regards,
Raja. - 03:37 PM Software Development: RE: Usage of I2C1 to connect external peripheral
- Can you post your source code for the I2CTest (including the value of addr) and provide a specification to the device...
- 03:18 PM Software Development: RE: Usage of I2C1 to connect external peripheral
- Hi Mike,
Thanks for your response.
I am using I2C1 and using from application as /dev/i2C-2. This change of pin...
05/03/2012
- 04:22 PM Software Development: RE: Usage of I2C1 to connect external peripheral
- Hi Raja,
Can you please post the full command lines for your output?
There are actually 3 I2C buses in play.
... - 03:55 PM Software Development: RE: Usage of I2C1 to connect external peripheral
- Hi Tim,
Thanks for the reply.
Even my understanding is almost similar. But earlier I have tried with out connec... - 01:34 PM Software Development: RE: Usage of I2C1 to connect external peripheral
- Raja
You can use the i2c utilties to test the bus. The output below is from scanning both I2C buses.
@root@mityarm-... - 12:00 PM Software Development: RE: Usage of I2C1 to connect external peripheral
- Hi Tim,
Gentle reminder about the above response.
Could you please let me know how to go ahead.
Regards,
Raja.
05/02/2012
- 02:52 PM Software Development: RE: Usage of I2C1 to connect external peripheral
- Hi Tim,
In Mity arm board I2C1 is configured on mii1_crs. pin and in Am335x based board same I2c1 is on spi0_d1 pi... - 02:37 PM Software Development: RE: Usage of I2C1 to connect external peripheral
- Raja
The EREMOTEIO error comes from drivers/i2c/busses/i2c-omap.c and is because there is no Ack from
bus request.
... - 02:35 PM Software Development: RE: Usage of I2C1 to connect external peripheral
- Sorry i missed to mention file name details.
filename = /dev/i2c-2. - 02:27 PM Software Development: RE: Usage of I2C1 to connect external peripheral
- Hi,
Code i have used to access is mentioned below:
fd = open(filename, O_RDWR);
ioctl(fd, I2C_SLAVE, addr);
... - Hi,
I am trying to use the I2C1 to communicate to the slave.
To probe the signals on Mity board, i am planning ...
04/30/2012
- 07:48 AM PCB Development: RE: Power Management w/ MityARM
- Hi Ali,
Sorry for the delay in response, you have a lot of questions wrapped up in these two posts, and we haven't...
04/27/2012
- 11:57 AM PCB Development: RE: Power Management w/ MityARM
- Sure enough after posting this I found the User's Guide for using TPS65910 with AM335x:
http://www.ti.com/lit/pdf/sw...
04/26/2012
- 06:08 PM Software Development: RE: PIN mux details and modifications
- I have tested these pins too
can_pin_mux[] = {
{"uart1_rxd.gpio0_14", AM33XX_PIN_OUTPUT},
{"uart1_txd.gpio0_15... - 05:46 PM Software Development: RE: PIN mux details and modifications
- Hi.
In your log file, you show modification of gpio 100.
The gpio offset on the linux command line needs to be ... - 05:29 PM Software Development: RE: PIN mux details and modifications
- Hi,
But i have changed the can_pin_mux and LCD_Data0 pins aswell. but even those are also not working. I have atta... - 05:21 PM Software Development: RE: PIN mux details and modifications
- Hi. OK.
From your log file, there is an error:
[ 0.079700] _omap_mux_get_by_name: Could not find signal lcd... - 04:36 PM Software Development: RE: PIN mux details and modifications
- Log file.
- 04:25 PM Software Development: RE: PIN mux details and modifications
- Hi Raja,
Can you also post your boot up text (dmesg)? I just want to check for any boot / pinmux error messages i... - 04:08 PM Software Development: RE: PIN mux details and modifications
- Attached the baseboard file for your refence.
Wanted to configure LCD_DATA pin to be configured as GPIO.
Thanks. - 03:49 PM Software Development: RE: PIN mux details and modifications
- Not yet (kind of bandwidth constrained, sorry).
You might try posting to the E2E site on TI's support site:
... - 03:44 PM Software Development: RE: PIN mux details and modifications
- Hi,
Do you have any updates for me regarding my approach on pinmux?
Thanks. - Hey,
We're trying to figure out how to utilized MityARM's power management capabilities in our design and this is ...
04/25/2012
- 01:27 PM Software Development: RE: PIN mux details and modifications
- Hi,
Thanks for your quick response.
I have tried the same by configuring LCD_data0 pin to GPIO. as lcd_data11.g... - 01:08 PM Software Development: RE: PIN mux details and modifications
- Hi,
So there are 3 steps to configuring a GPIO.
1) modify the baseboard file and ensure your issuing a pin mux ... - 12:57 PM Software Development: RE: PIN mux details and modifications
- Hi Mike,
To change the mux details i have defined the basic pin details to GPIO and added GPIO pin details to mux3...
04/23/2012
- 04:40 PM Software Development: RE: PIN mux details and modifications
- Hi Mike,
Thanks for the information.
what are all the modifications we have to do if our board doesnot have any...
04/20/2012
- 10:44 AM Software Development: RE: Test application for drivers
- For a linux system, GPIOs can be driven using sysfs via command line to modify the pins via the "gpiolib":http://www....
- Hi,
Do you have any test application to test the drivers such as GPIO and UART? Could you please share them?
Re... - 10:38 AM Software Development: RE: PIN mux details and modifications
- Are you using linux as your target OS? If you, you will need to update the pinmux settings in your baseboard-XXXX.c ...
- Hi,
I have to use more GPIOs in our design. I am thinking of using the pins assigned for CAN0 and CAN1 in Mityarm ...
04/19/2012
- 03:50 PM Software Development: RE: Is RMII possible with the MityARM-3359?
- Yes,
It should be supported if you configure the pinmux accordingly. You will need to modify u-Boot in order to ... - (posted on behalf of a customer)
Is RMII possible with the MityARM-3359? I didn’t see some on the alternate funct... - 03:31 PM Software Development: RE: Is there a linux driver for RMII or just RGMII for the MityARM-3359
- We've only tried to use the RGMII port here. I'm fairly certain that RMII is supported, but you should contact TI on...
- Is there a linux driver for RMII or just RGMII?
- 02:54 PM PCB Development: RE: ADC reference voltage data required
- salam
The TI datasheet for the AM3359 [ http://www.ti.com/lit/ds/symlink/am3359.pdf ] recommends 1.8V for the ADC ci... - Hi,
`A 3.3 V and 1.8 V are connected to the ADC reference voltage in your carrier board reference design, Can i con...
04/18/2012
- 02:37 PM PCB Development: RE: Is a separate I2C EEPROM needed to ID our Carrier board?
- Yes,
You should be defining your own baseboard-***.c file if you are making a custom board using the baseboard-mit... - 11:46 AM PCB Development: RE: Is a separate I2C EEPROM needed to ID our Carrier board?
- Hey Mike, that helps a lot. One reason I was asking about the EEPROM because we plan to cable a 24-bit LCD/touchscre...
- 08:06 AM PCB Development: RE: Is a separate I2C EEPROM needed to ID our Carrier board?
- Hi.
The TI SDK works with the MityARM-3359, but you need to replace "u-Boot":http://support.criticallink.com/redmi... - 12:00 PM PCB Development: RE: SPI1 pin conflict:
- Michael Williamson wrote:
> The MityARM-335x module provides SPI1 SCLK, D0 and D1 on pins 193, 195, and 197 of the e... - 08:19 AM PCB Development: RE: SPI1 pin conflict:
- The MityARM-335x module provides SPI1 SCLK, D0 and D1 on pins 193, 195, and 197 of the edge connector.
On the modu...
04/17/2012
- (posted on behalf of a customer)
All the other AM3359 boards have this (ULCD, TI EVM, BeagleBone, etc.) and it loo... - (posted on behalf of a customer)
MityDSP has dedicated pins 193, 195 and 197 to SPI1 because they connected it to ...
04/16/2012
- 02:42 PM PCB Development: RE: Reg. ADC reference voltage
- a gentle reminder for the below question
regards
salam
04/15/2012
- 12:47 PM PCB Development: RE: Specification TPS power sully design inthe AM3359 carrier board
- Hi Salam,
If you are asking if you can use our reference DevKit 3.3V supply design to power other 3.3V devices, th...
04/13/2012
- 03:23 PM Software Development: RE: Problem in building of kernel and booting
- Hi Mike,
Thankyou very much. That worked...
But the only difference is the kernal iamge name provided default i... - 02:48 PM PCB Development: RE: Specification TPS power sully design inthe AM3359 carrier board
- gentile reminder for the above question
- 02:48 PM PCB Development: RE: Specification TPS power sully design inthe AM3359 carrier board
- gentile reminder for the above question
Also available in: Atom
Go to top
