Re: [beagleboard] Re: detecting interrupt on GPIO in kernel module
Yes it does show in cat /proc/interrupts
It doesnot matter you use request_threaded_irq or request_irq
request_irq(unsigned int irq, irq_handler_t handler, unsigned long flags,
const char *name, void *dev)
Here the handler will be run in interrupt context
and
request_threaded_irq(unsigned int irq, irq_handler_t handler,
irq_handler_t thread_fn,
unsigned long flags, const char *name, void *dev);
In threaded IRQ
irq_handler_t handle - Interrupt context
irq_handler_t thread_fn- Process context
This is the only difference.
Thanks
Kavitha
On Wed, Sep 10, 2014 at 8:03 AM, neo prag.in...@gmail.com wrote:
Hi Kavita
A generic question regarding interrupts.
If i register an interrupt using request_threaded_irq() or request_irq()
will that be listed in /proc/interrupts ?
On Tuesday, September 9, 2014 11:17:19 AM UTC+5:30, kavitha wrote:
Does cat /proc/interrupts give show anything for 214.
Check whether It is going to architecture specific impelemtation of
gpio_to_irq
On Tue, Sep 9, 2014 at 8:26 AM, neo star prag@gmail.com wrote:
Hi
I see that some function definitions are missing in your code. Can you
share those as well, so that i too can try and figure out the problem.
Especially the functions like gpio_to_irq() ...
Thanks.
On Tuesday, August 26, 2014 7:38:01 PM UTC+5:30, Siddarth Sharma wrote:
I am toggling the input into a GPIO line on my BeagleBone from high to
low every 500 ms using an Atmel uC. I have registered a handler for this in
my Linux Kernel Module, but the handler is not being called for some
reason.
My module code is -
#define GPIO 54
#define GPIO_INT_NAME gpio_int
#define GPIO_HIGH gpio_get_value(GPIO)
#define GPIO_LOW (gpio_get_value(GPIO) == 0)
short int irq_any_gpio= 0;
int count =0;
enum { falling, rising } type;
static irqreturn_t r_irq_handler(int irq, void *dev_id)
{
count++;
printk(KERN_DEBUG interrupt received (irq: %d)\n, irq);
if (irq == gpio_to_irq(GPIO))
{
type = GPIO_LOW ? falling : rising;
if(type == falling)
{
printk(gpio pin is low\n);
}
else
printk(gpio pin is high\n);
}
return IRQ_HANDLED;
}
void r_int_config(void) {
if (gpio_request(GPIO, GPIO_INT_NAME ))
{
printk(GPIO request failure: %s\n, GPIO_INT_NAME );
return;
}
if ( (irq_any_gpio = gpio_to_irq(GPIO)) 0 ) {
printk(GPIO to IRQ mapping failure %s\n,GPIO_INT_NAME );
return;
}
printk(KERN_NOTICE Mapped int %d\n, irq_any_gpio);
if (request_irq(irq_any_gpio,(irq_handler_t ) r_irq_handler,
IRQF_TRIGGER_HIGH, GPIO_INT_NAME, NULL))
{
printk(Irq Request failure\n);
return;
}
return;
}
void r_int_release(void) {
free_irq(gpio_to_irq(GPIO), NULL);
gpio_free(GPIO);;
return;
}
int init_module(void)
{
printk(1Hello World\n);
r_int_config();
return 0;
}
On calling insmod interrupt_test.ko, i get the following message
[ 76.594543] Hello World
[ 76.597137] Mapped int 214
But now when I start toggling the input into this gpio pin, the
interrupt handler doesn't get called and the message - interrupt received
is not being displayed.
How do I solve this ? What's causing the problem?
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google
Groups BeagleBoard group.
To unsubscribe from this group and stop receiving emails from it, send
an email to beagleboard...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups
BeagleBoard group.
To unsubscribe from this group and stop receiving emails from it, send an
email to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups
BeagleBoard group.
To unsubscribe from this group and stop receiving emails from it, send an email
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Re: detecting interrupt on GPIO in kernel module
Does cat /proc/interrupts give show anything for 214.
Check whether It is going to architecture specific impelemtation of gpio_to_irq
On Tue, Sep 9, 2014 at 8:26 AM, neo star prag.in...@gmail.com wrote:
Hi
I see that some function definitions are missing in your code. Can you
share those as well, so that i too can try and figure out the problem.
Especially the functions like gpio_to_irq() ...
Thanks.
On Tuesday, August 26, 2014 7:38:01 PM UTC+5:30, Siddarth Sharma wrote:
I am toggling the input into a GPIO line on my BeagleBone from high to
low every 500 ms using an Atmel uC. I have registered a handler for this in
my Linux Kernel Module, but the handler is not being called for some reason.
My module code is -
#define GPIO 54
#define GPIO_INT_NAME gpio_int
#define GPIO_HIGH gpio_get_value(GPIO)
#define GPIO_LOW (gpio_get_value(GPIO) == 0)
short int irq_any_gpio= 0;
int count =0;
enum { falling, rising } type;
static irqreturn_t r_irq_handler(int irq, void *dev_id)
{
count++;
printk(KERN_DEBUG interrupt received (irq: %d)\n, irq);
if (irq == gpio_to_irq(GPIO))
{
type = GPIO_LOW ? falling : rising;
if(type == falling)
{
printk(gpio pin is low\n);
}
else
printk(gpio pin is high\n);
}
return IRQ_HANDLED;
}
void r_int_config(void) {
if (gpio_request(GPIO, GPIO_INT_NAME ))
{
printk(GPIO request failure: %s\n, GPIO_INT_NAME );
return;
}
if ( (irq_any_gpio = gpio_to_irq(GPIO)) 0 ) {
printk(GPIO to IRQ mapping failure %s\n,GPIO_INT_NAME );
return;
}
printk(KERN_NOTICE Mapped int %d\n, irq_any_gpio);
if (request_irq(irq_any_gpio,(irq_handler_t ) r_irq_handler,
IRQF_TRIGGER_HIGH, GPIO_INT_NAME, NULL))
{
printk(Irq Request failure\n);
return;
}
return;
}
void r_int_release(void) {
free_irq(gpio_to_irq(GPIO), NULL);
gpio_free(GPIO);;
return;
}
int init_module(void)
{
printk(1Hello World\n);
r_int_config();
return 0;
}
On calling insmod interrupt_test.ko, i get the following message
[ 76.594543] Hello World
[ 76.597137] Mapped int 214
But now when I start toggling the input into this gpio pin, the interrupt
handler doesn't get called and the message - interrupt received is not
being displayed.
How do I solve this ? What's causing the problem?
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups
BeagleBoard group.
To unsubscribe from this group and stop receiving emails from it, send an
email to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups
BeagleBoard group.
To unsubscribe from this group and stop receiving emails from it, send an email
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Re: registering asynchronous events on kernel thread in user space
May be you can use udev In the
err = request_threaded_irq(pdata-irq, NULL, receive_thread,
pdata-irqflags, interrupt, ir);
In reciever thread
static irqreturn_t receive_threar(int irq, void *context_data)
{
struct data *dh = context_data;
input_report_key(dh-input_dev, key, 1);
input_sync(dhinput_dev)
}
In userspace use evetest like application to wait on the event or simple
select on /dev/input should work
On Tue, Sep 9, 2014 at 8:10 AM, neo star prag.in...@gmail.com wrote:
Hi
I too have the same question, have you found any answer ? thanks
On Thursday, August 28, 2014 3:14:12 PM UTC+5:30, sid...@gmail.com wrote:
I have read online that we can't handle interrupts from user
space. Instead -
1) We can write a kernel thread and have that thread wait on an event.
2) Once the interrupt occurs, send one asynchronous event from the kernel
module/driver to user space where we will have one signal handler with
FASYNC to tackle this
I have written a kernel module that registers interrupts on the rising
edge on a GPIO pin and want to relay this message to user space. How do I
go about implementing the above?
Thanks!
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups
BeagleBoard group.
To unsubscribe from this group and stop receiving emails from it, send an
email to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups
BeagleBoard group.
To unsubscribe from this group and stop receiving emails from it, send an email
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Re: Booting off Micro SD Card
I dont think sd card permissions you can change using chmod mmcroot=/dev/mmcblk1p2 rw you can try On Tue, Sep 2, 2014 at 9:48 AM, Don deJuan donjuans...@gmail.com wrote: On 09/01/2014 08:15 PM, William Pretty Security wrote: You need to change the “permissions” chmod 777 /dev/sda1 or chmod 777 /media/mydiskname No one could make a greater mistake than he who did nothing because he could do only a little. All that is necessary for the triumph of evil is that good men do nothing Edmond Burke *(1729 - 1797)* http://www.packtpub.com/building-a-home-security-system-with-beaglebone/book *From:* beagleboard@googlegroups.com [mailto:beagleboard@googlegroups.com beagleboard@googlegroups.com] *On Behalf Of *Jose B Rivera *Sent:* Monday, September 01, 2014 10:17 PM *To:* beagleboard@googlegroups.com *Subject:* [beagleboard] Re: Booting off Micro SD Card I somehow figured out how to get my micro sd card to be 'sda1'. I added some text to it mmcdev=1 bootpart=1:2 mmcroot=/dev/mmcblk1p2 ro optargs=quiet And named it uEnv.txt (on the card itself) Now my BBB sees it as sda1. I was able to mount it to /media by making a directory under it and then mounted it. Question: How do I now use this mounted sda1? I tried ftp upload to it but I get permission denied. On Monday, September 1, 2014 8:02:47 PM UTC-4, Jose B Rivera wrote: Where can I obtain an image to put on a 32gb micro sd card to then insert into my BBB and have it boot off of the micro sd card? (And the instructions to go with it?). Having my BBB recognize the 32gb card as external storage has become such a big problem/issue, that at this point I just want to boot off the card in order to use the 32gb of file space it affords. All I find on the internet are confusing instructions which tend to mix files used to flash the emmc with instructions to boot off a micro-sd card. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. No virus found in this message. Checked by AVG - www.avg.com Version: 2014.0.4745 / Virus Database: 4015/8138 - Release Date: 09/01/14 -- No virus found in this message. Checked by AVG - www.avg.com Version: 2014.0.4745 / Virus Database: 4007/8033 - Release Date: 08/14/14 Internal Virus Database is out of date. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. chmod 777 is bad advice. Figure out the real issue and solve the problem. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Re: Is it easy to reduce the clock frequency on Beaglebone I2C?
Just change the speed in board file or in dts
i2c4 {
pinctrl-names = default;
clock-frequency = 40;
};
It is 400kHz you can change to 100kHz
or If you are using a board file
omap_register_i2c_bus(2, 400, drishti_i2c2_board_info,
ARRAY_SIZE(drishti_i2c2_board_info));
You can specify 100
I also dont see a point to reduce . You can also specify in u-boot as well
Kavitha
On Mon, Sep 1, 2014 at 12:17 PM, Martin H. mart...@innomar.com wrote:
You might like to have a look at the P82B96 data sheet.
Feature:
400kHz operation over at least 20 meters of wire
And you don't have to modifiy your I2C code!
Martin H.
Am Freitag, 29. August 2014 19:18:46 UTC+2 schrieb c...@isbd.net:
I want to stretch the I2C bus to a few metres, I will use screened
cable to minimise noise pick-up but this will increase the capacitive
load on the bus. So, I probably need to reduce the I2C clock
frequency, how easy is it to do this? I will probably use the
Adafruit libraries but don't have to.
--
Chris Green
·
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups
BeagleBoard group.
To unsubscribe from this group and stop receiving emails from it, send an
email to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups
BeagleBoard group.
To unsubscribe from this group and stop receiving emails from it, send an email
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] BeagleBone Black PWM lowest frequency ?
Are you talking about processor frequency or PWN frequency? On Sat, Aug 30, 2014 at 7:19 PM, xmen@gmail.com wrote: Can anyone tell me the lowest frequency beaglebone black can get ? I dont own it yet but if it can do what I need, I will buy. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] 3D Accelerator
hi
If an input device is created then /dev/input/event* should exist
Compile evtest.c which attached
and use command evtest /dev/input/event* should give you some events when
you turn up and down
On Wed, Aug 6, 2014 at 1:49 AM, mizubai...@gmail.com wrote:
Hi
How do we know whether the 3D accelerator is working or not in a BBB?
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups
BeagleBoard group.
To unsubscribe from this group and stop receiving emails from it, send an
email to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups
BeagleBoard group.
To unsubscribe from this group and stop receiving emails from it, send an email
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
/*
* $Id: evtest.c,v 1.23 2005/02/06 13:51:42 vojtech Exp $
*
* Copyright (c) 1999-2000 Vojtech Pavlik
*
* Event device test program
*/
/*
* This program is free software; you can redistribute it and/or modify
* it under the terms of the GNU General Public License as published by
* the Free Software Foundation; either version 2 of the License, or
* (at your option) any later version.
*
* This program is distributed in the hope that it will be useful,
* but WITHOUT ANY WARRANTY; without even the implied warranty of
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
* GNU General Public License for more details.
*
* You should have received a copy of the GNU General Public License
* along with this program; if not, write to the Free Software
* Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
*
* Should you need to contact me, the author, you can do so either by
* e-mail - mail your message to vojt...@ucw.cz, or by paper mail:
* Vojtech Pavlik, Simunkova 1594, Prague 8, 182 00 Czech Republic
*/
#include stdint.h
#include linux/input.h
#include string.h
#include fcntl.h
#include unistd.h
#include stdio.h
#ifndef EV_SYN
#define EV_SYN 0
#endif
char *events[EV_MAX + 1] = {
[0 ... EV_MAX] = NULL,
[EV_SYN] = Sync, [EV_KEY] = Key,
[EV_REL] = Relative, [EV_ABS] = Absolute,
[EV_MSC] = Misc, [EV_LED] = LED,
[EV_SND] = Sound, [EV_REP] = Repeat,
[EV_FF] = ForceFeedback, [EV_PWR] = Power,
[EV_FF_STATUS] = ForceFeedbackStatus,
};
char *keys[KEY_MAX + 1] = {
[0 ... KEY_MAX] = NULL,
[KEY_RESERVED] = Reserved, [KEY_ESC] = Esc,
[KEY_1] = 1,[KEY_2] = 2,
[KEY_3] = 3,[KEY_4] = 4,
[KEY_5] = 5,[KEY_6] = 6,
[KEY_7] = 7,[KEY_8] = 8,
[KEY_9] = 9,[KEY_0] = 0,
[KEY_MINUS] = Minus, [KEY_EQUAL] = Equal,
[KEY_BACKSPACE] = Backspace, [KEY_TAB] = Tab,
[KEY_Q] = Q,[KEY_W] = W,
[KEY_E] = E,[KEY_R] = R,
[KEY_T] = T,[KEY_Y] = Y,
[KEY_U] = U,[KEY_I] = I,
[KEY_O] = O,[KEY_P] = P,
[KEY_LEFTBRACE] = LeftBrace, [KEY_RIGHTBRACE] = RightBrace,
[KEY_ENTER] = Enter, [KEY_LEFTCTRL] = LeftControl,
[KEY_A] = A,[KEY_S] = S,
[KEY_D] = D,[KEY_F] = F,
[KEY_G] = G,[KEY_H] = H,
[KEY_J] = J,[KEY_K] = K,
[KEY_L] = L,[KEY_SEMICOLON] = Semicolon,
[KEY_APOSTROPHE] = Apostrophe, [KEY_GRAVE] = Grave,
[KEY_LEFTSHIFT] = LeftShift, [KEY_BACKSLASH] = BackSlash,
[KEY_Z] = Z,[KEY_X] = X,
[KEY_C] = C,[KEY_V] = V,
[KEY_B] = B,[KEY_N] = N,
[KEY_M] = M,[KEY_COMMA] = Comma,
[KEY_DOT] = Dot, [KEY_SLASH] = Slash,
[KEY_RIGHTSHIFT] = RightShift, [KEY_KPASTERISK] = KPAsterisk,
[KEY_LEFTALT] = LeftAlt, [KEY_SPACE] = Space,
[KEY_CAPSLOCK] = CapsLock, [KEY_F1] = F1,
[KEY_F2] = F2, [KEY_F3] = F3,
[KEY_F4] = F4, [KEY_F5] = F5,
[KEY_F6] = F6, [KEY_F7] = F7,
[KEY_F8] = F8, [KEY_F9] = F9,
[KEY_F10] = F10, [KEY_NUMLOCK] = NumLock,
[KEY_SCROLLLOCK] = ScrollLock, [KEY_KP7] = KP7,
[KEY_KP8] = KP8, [KEY_KP9] = KP9,
[KEY_KPMINUS] = KPMinus, [KEY_KP4] = KP4,
[KEY_KP5] = KP5, [KEY_KP6] = KP6,
[KEY_KPPLUS] = KPPlus, [KEY_KP1] = KP1,
[KEY_KP2] = KP2, [KEY_KP3] = KP3,
[KEY_KP0] = KP0, [KEY_KPDOT] = KPDot,
[KEY_ZENKAKUHANKAKU] = Zenkaku/Hankaku, [KEY_102ND] = 102nd,
[KEY_F11] = F11, [KEY_F12] = F12,
[KEY_RO] = RO, [KEY_KATAKANA] = Katakana,
[KEY_HIRAGANA] = HIRAGANA, [KEY_HENKAN] = Henkan,
[KEY_KATAKANAHIRAGANA] = Katakana/Hiragana, [KEY_MUHENKAN] = Muhenkan,
[KEY_KPJPCOMMA] = KPJpComma, [KEY_KPENTER] = KPEnter,
[KEY_RIGHTCTRL] = RightCtrl, [KEY_KPSLASH] = KPSlash,
[KEY_SYSRQ] = SysRq, [KEY_RIGHTALT] = RightAlt,
[KEY_LINEFEED] = LineFeed, [KEY_HOME] = Home,
[KEY_UP] = Up, [KEY_PAGEUP] = PageUp,
[KEY_LEFT] = Left, [KEY_RIGHT] = Right,
[KEY_END] = End, [KEY_DOWN] = Down,
[KEY_PAGEDOWN] = PageDown, [KEY_INSERT] = Insert,
[KEY_DELETE] = Delete, [KEY_MACRO] = Macro,
[KEY_MUTE] = Mute, [KEY_VOLUMEDOWN] = VolumeDown,
Re: [beagleboard] Re: CONFIG_WATCHDOG_NOWAYOUT = How ?
Yes I have alos enable config WATCHDOG_NOWAYOUT=y On Tue, Apr 8, 2014 at 1:26 PM, Yiling Cao yiling@gmail.com wrote: I have done this months ago, and very useful. this is under kernel config, .config file, so: make menuconfig ARCH=arm search for nowayout │ Symbol: WATCHDOG_NOWAYOUT [=n] │ │ Type : boolean │ │ Prompt: Disable watchdog shutdown on close │ │ Defined at drivers/watchdog/Kconfig:39 │ │ Depends on: WATCHDOG [=y] │ │ Location: │ │ - Device Drivers │ │ - Watchdog Timer Support (WATCHDOG [=y]) u need to change it to enable and recompile the kernel. good luck On Tue, Apr 8, 2014 at 2:43 PM, Micka mickamus...@gmail.com wrote: I just installed the package : insserv: warning: script 'K01script-initd-' missing LSB tags and overrides insserv: warning: script 'script-initd-' missing LSB tags and overrides insserv: warning: script 'K02script-initd-' missing LSB tags and overrides insserv: warning: script 'script-initd-' missing LSB tags and overrides insserv: warning: script 'K01script-initd-' missing LSB tags and overrides insserv: warning: script 'script-initd-' missing LSB tags and overrides insserv: warning: script 'K02script-initd-' missing LSB tags and overrides . I hope that it's ok On Mon, Apr 7, 2014 at 10:06 PM, AndrewTaneGlen andrewtaneg...@gmail.com wrote: To get the hardware watchdog working (on Debian) I just installed the watchdog package (sudo apt-get install watchdog), then set the correct device in the config file: in '/etc/watchdog.conf' set 'watchdog-device = /dev/watchdog' I'm fairly certain that's all I needed to do. On Tuesday, 8 April 2014 05:14:44 UTC+12, Mickae1 wrote: Hi, I would like to activate the watchdog in the beagle. I recompiled the beagle with the flag watchdog software. but how can i activate the flag CONFIG_WATCHDOG_NOWAYOUT ??? Thx, -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Writing EEPROM Using I2C Commands over U-Boot
Yes the eeprom write in U-boot wont work as they might be 16 bit adressses or 16 bit data Modify the i2c driver to make it work in U-boot or write a new Uboot command to access the eeprom Thanks Kavitha On Fri, Feb 7, 2014 at 3:24 PM, John Nash szrjustd...@gmail.com wrote: Hi Buğra AYDOĞAR, you said In case, the value which you wrote above is ASCII so you will see 31:32:33:34:35:36:37:38 in your EEPROM.,but how I can see it 在 2012年10月31日星期三UTC+8下午2时39分12秒，Buğra AYDOĞAR写道： Hi Gerald, No, it is not write protected. I wrote my EEPROM over Linux using Sysfs last night. I dont remember exactly (I dont have my development board right now) but it did sth like that cd sys/bus/i2c/devices/1-0050/ echo 12345678 eeprom In case, the value which you wrote above is ASCII so you will see 31:32:33:34:35:36:37:38 in your EEPROM. Here is converter .( http://www.dolcevie.com/js/converter.html) I think U-Boot I2C commands have some problems.It also doesnt always read BeagleBone's EEPROM correctly.(%50 sucessfully show BeagleBone's header and magic number.) . Maybe it is about U-Boot version. I also looked with scope, it really sent data to EEPROM but I dont know exactly. As a result my problem is solved but it is more logicial to write EEPROM over U-Boot. Regards, Buğra On Tuesday, October 30, 2012 10:19:57 PM UTC+2, Gerald wrote: Is your EEPROM write protected? Gerald On Tue, Oct 30, 2012 at 1:28 PM, Buğra AYDOĞAR bugraa...@gmail.comwrote: Hi folks, We have custom Am335x board with eeprom.We want to shape our eeprom like BeagleBone (I mean name,version,serial etc...). I tried with U-Boot using I2C commands.You can see my logs below. Firstly i read my eeprom, then i tried to write byte by btye.Then i read again but nth happened.Then i tried to fill with 0xAA again it didnt succeed. How do you do it? By the way,I ported and used U-Boot 2011.09 for this purpose.I used i2c-tool over Linux but it says UU which means driver is used by Linux and it doesnt let me dump or anything else. What do you suggest to move on? Regards, Buğra U-Boot# i2c probe Valid chip addresses: 24 48 4F 50 51 U-Boot# i2c dev 1 Setting bus to 1 U-Boot# i2c dev 0 Setting bus to 0 U-Boot# i2c md 0x50 0 0x10 : ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff U-Boot# i2c mm 0x50 0 : ff ? AA 0001: ff ? BB 0002: ff ? CC 0003: ff ? DD 0004: ff ? U-Boot# INTERRUPT U-Boot# INTERRUPT U-Boot# U-Boot# U-Boot# i2c md 0x50 0 0x10 : ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff U-Boot# U-Boot# i2c mw 0x50 0 0x10 0xAA U-Boot# i2c md 0x50 0 0x10 : ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff U-Boot# i2c md 0x50 0 0x10 : ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff -- -- Gerald ger...@beagleboard.org g-co...@ti.com http://beagleboard.org/ http://circuitco.com/support/ -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [beagleboard] Re: i2c-2 of expansion header is not detected
git am patch.patch On Wed, Jan 8, 2014 at 4:44 PM, HARSHIT SINHA battery...@gmail.com wrote: Thanks For the Prompt reply How to apply the patch. I am trying with the following command diff --git a/arch/arm/mach-omap2/board-omap3beagle.c b/arch/arm/mach-omap2/board-omap3beagle.c index 4a71cb7..2148f35 100644 --- a/arch/arm/mach-omap2/board-omap3beagle.c +++ b/arch/arm/mach-omap2/board-omap3beagle.c @@ -385,6 +385,7 @@ static int __init omap3_beagle_i2c_init(void) beagle_twldata.vpll2-constraints.name= VDVI; omap3_pmic_init(twl4030, beagle_twldata); + omap_register_i2c_bus(2, 400, NULL, 0); /* Bus 3 is attached to the DVI port where devices like the pico DLP * projector don't work reliably with 400kHz */ omap_register_i2c_bus(3, 100, beagle_i2c_eeprom, ARRAY_SIZE(beagle_i2c_eeprom)); *I also tried* the git diff commands but terminal shows error So, finally how to enable the I2c2 iam also thinking of recompiling the kernel from git clone. On Wednesday, 8 January 2014 01:51:46 UTC+5:30, HARSHIT SINHA wrote: when i do i2cdetect only i2c1, i2c3 recognizes but no i2c-2. how to enable i2c2 plz -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [beagleboard] Partitions/blocks of 2GB emmc at BBB Board
I want to know the Partitions/blocks of 2GB emmc at BBB Board ex, Spl Start AddressEnd Address Uboot Kernel rootfs I dont think there is any command to see . U can display the emmc contents and see which memory location it is written and see usually u-boot is flashed at multiple of 128 bytes and kernel at adsress 0x8200 On Sun, Nov 17, 2013 at 7:36 AM, jay0710.w...@gmail.com wrote: 1. I want to know the Partitions/blocks of 2GB emmc at BBB Board ex, Spl Start AddressEnd Address Uboot Kernel rootfs 2.how can i update these blocks use uboot?? ex, U-Boot# loadb 0x8200 Download MLO/Uboot to SDRAM U-Boot# nand erase 0x0 0x2 U-Boot# nand write 0x8200 0x0 0x2 -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [beagleboard] Re: [Issue] BeagleBone Black Random Reboot
Good you know the reason But It is always better if you print your PMIC last boot status during next boot or even the Processor last boot reason so that next boot you can see the reason for reboot https://android.googlesource.com/kernel/omap.git/+/android-omap-tuna-3.0-ics-mr1/arch/arm/mach-omap2/resetreason.c Kavitha On Tue, Oct 29, 2013 at 11:16 AM, Illutian Kade delvan...@gmail.com wrote: Ya, figured it was something wrong with the port. The AC Adapter works fine; 5.1v on a meter. The board works fine; when powered by USB using the Debug Port. I wonder if I can use a 5v,2a Fast Charger port or if it'll burn out the BBB's Debug Port On Monday, October 28, 2013 9:10:19 AM UTC-4, Gerald wrote: That would be a first! I suspect it may be a grounding issue. Gerald On Mon, Oct 28, 2013 at 7:45 AM, Illutian Kade delv...@gmail.com wrote: UPDATE Appears the DC port on the board failed. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard...@**googlegroups.com. For more options, visit https://groups.google.com/**groups/opt_outhttps://groups.google.com/groups/opt_out . -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
