Re: [beagleboard] Re: ODBC & SQL SERVER

[Micka]

Thanks,

But again it give the link to the microsoft page for the ODBC driver:

https://docs.microsoft.com/en-us/sql/connect/odbc/linux-mac/installing-the-microsoft-odbc-driver-for-sql-server

:(

On Fri, Jul 30, 2021 at 4:24 PM amf  wrote:
>
> Is this the source your looking at, it does indicate it supports 32 bit. (I 
> have not used it)
> https://github.com/microsoft/msphpsql
>
> On Friday, July 30, 2021 at 9:14:23 AM UTC-5 Micka wrote:
>>
>> Hi,
>>
>> I would like to know if anyone has succeeded to install the driver
>> msodbcsql on the beaglebone black ?
>>
>> Looks like that it's only available for 64 bit machine :(
>>
>>
>> Michael,
>
> --
> 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.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/beagleboard/0c4630b6-311a-4d82-ac6c-6c4f72af9bcen%40googlegroups.com.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAF%2BMRtmzw8Sj168jxJ5xAvmGgJ4e8HHi%3DFp-xHinGOKB%2BAkirA%40mail.gmail.com.

[beagleboard] ODBC & SQL SERVER

[Micka]

Hi,

I would like to know if anyone has succeeded to install the driver
msodbcsql on the beaglebone black ?

Looks like that it's only available for 64 bit machine :(


Michael,

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAF%2BMRtkPNAiKZrfuE6O8kCN5DBJDHa-4VJx1MvRWDXN_j3xqNA%40mail.gmail.com.

[beagleboard] Micron MT41K256M16HA-125:E

[Micka]

Hi, We have to change the component: Micron MT41K256M16HA-125:E

This list:

Micron MT41K256M16TW-107:P
Kingston D2516EC4BXGGB
Kingston D2516EC4BXGGB-U

are all compatible ? without any change in the configuration?



Michael,

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAF%2BMRt%3DSJRTMD%3D44Mddqw59Z5UBB6HFmYXvNwL1yexkSEDMSgA%40mail.gmail.com.

[beagleboard] Re: problem of SD and cache

[Micka]

I found some anwer on the internet about setting :

 "vm.min_free_kbytes = 8192" to  /etc/sysctl.conf?

How do you calculate this value ?

Thanks,

On Fri, Jan 8, 2021 at 5:09 PM Micka  wrote:
>
> Hi,
>
> I've a program that is writing a big file in the SD periodically.
>
> After a long time, I got this error:
>
> why ? How can i fix this problem? Is it the cache ?
>
> [24032.356007] edma 4900.edma: edma_prep_slave_sg: Failed to
> allocate a descriptor
> [24032.364121] omap_hsmmc 4806.mmc: prep_slave_sg() failed
> [24032.368114] omap_hsmmc 4806.mmc: MMC start dma failure
> [24032.392355] mmcblk0: unknown error -1 sending read/write command,
> card status 0x900
> [24032.478884] mmc0: tried to reset card
> [24032.479662] mmcqd/0: page allocation failure: order:2, mode:0x2204020
> [24032.479678] CPU: 0 PID: 73 Comm: mmcqd/0 Not tainted 4.4.13-bone11 #153
> [24032.479686] Hardware name: Generic AM33XX (Flattened Device Tree)
> [24032.479738] [] (unwind_backtrace) from []
> (show_stack+0x11/0x14)
> [24032.479762] [] (show_stack) from []
> (warn_alloc_failed+0xb5/0xf0)
> [24032.479780] [] (warn_alloc_failed) from []
> (__alloc_pages_nodemask+0x5d1/0x704)
> [24032.479801] [] (__alloc_pages_nodemask) from []
> (cache_alloc_refill+0x1eb/0x3ac)
> [24032.479815] [] (cache_alloc_refill) from []
> (__kmalloc+0x101/0x120)
> [24032.479840] [] (__kmalloc) from []
> (edma_prep_slave_sg+0x77/0x224)
> [24032.479864] [] (edma_prep_slave_sg) from []
> (omap_hsmmc_request+0x33d/0x3f4)
> [24032.479888] [] (omap_hsmmc_request) from []
> (mmc_start_request+0xcb/0x1ac)
> [24032.479904] [] (mmc_start_request) from []
> (mmc_start_req+0x1f3/0x2c4)
> [24032.479919] [] (mmc_start_req) from []
> (mmc_blk_issue_rw_rq+0x273/0x7ac)
> [24032.479932] [] (mmc_blk_issue_rw_rq) from []
> (mmc_blk_issue_rq+0x1a3/0x368)
> [24032.479943] [] (mmc_blk_issue_rq) from []
> (mmc_queue_thread+0x77/0x114)
> [24032.479966] [] (mmc_queue_thread) from []
> (kthread+0xa3/0xb8)
> [24032.479982] [] (kthread) from []
> (ret_from_fork+0x11/0x1c)
> [24032.479989] Mem-Info:
> [24032.480009] active_anon:35548 inactive_anon:7471 isolated_anon:0
>  active_file:32682 inactive_file:35639 isolated_file:0
>  unevictable:0 dirty:9070 writeback:4648 unstable:0
>  slab_reclaimable:4384 slab_unreclaimable:1977
>  mapped:19167 shmem:24293 pagetables:345 bounce:0
>  free:1490 free_pcp:125 free_cma:0
> [24032.480049] Normal free:5960kB min:2752kB low:3440kB high:4128kB
> active_anon:142192kB inactive_anon:29884kB active_file:130728kB
> inactive_file:142556kB unevictable:0kB isolated(anon):0kB
> isolated(file):0kB present:524288kB managed:506492kB mlocked:0kB
> dirty:36280kB writeback:18592kB mapped:76668kB shmem:97172kB
> slab_reclaimable:17536kB slab_unreclaimable:7908kB kernel_stack:1104kB
> pagetables:1380kB unstable:0kB bounce:0kB free_pcp:500kB
> local_pcp:500kB free_cma:0kB writeback_tmp:0kB pages_scanned:0
> all_unreclaimable? no
> [24032.480058] lowmem_reserve[]: 0 0 0
> [24032.480069] Normal: 576*4kB (UME) 457*8kB (U) 0*16kB 0*32kB 0*64kB
> 0*128kB 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB 0*8192kB = 5960kB
> [24032.480101] 92614 total pagecache pages
> [24032.480113] 0 pages in swap cache
> [24032.480119] Swap cache stats: add 0, delete 0, find 0/0
> [24032.480124] Free swap  = 0kB
> [24032.480129] Total swap = 0kB
> [24032.480134] 131072 pages RAM
> [24032.480138] 0 pages HighMem/MovableOnly
> [24032.480144] 4449 pages reserved
> [24032.480148] 6144 pages cma reserved
> [24032.480165] edma 4900.edma: edma_prep_slave_sg: Failed to
> allocate a descriptor
> [24032.488265] omap_hsmmc 4806.mmc: prep_slave_sg() failed
> [24032.492250] omap_hsmmc 4806.mmc: MMC start dma failure
> [24032.533988] mmcblk0: unknown error -1 sending read/write command,
> card status 0x900
> [24032.544849] EXT4-fs warning (device mmcblk0p1): ext4_end_bio:329:
> I/O error -5 writing to inode 3696 (offset 8388608 size 8388608
> starting block 2369280)
> [24032.556785] mmcqd/0: page allocation failure: order:2, mode:0x2204020
> [24032.556814] CPU: 0 PID: 73 Comm: mmcqd/0 Not tainted 4.4.13-bone11 #153
> [24032.556821] Hardware name: Generic AM33XX (Flattened Device Tree)
> [24032.556874] [] (unwind_backtrace) from []
> (show_stack+0x11/0x14)
> [24032.556898] [] (show_stack) from []
> (warn_alloc_failed+0xb5/0xf0)
> [24032.556917] [] (warn_alloc_failed) from []
> (__alloc_pages_nodemask+0x5d1/0x704)
> [24032.556938] [] (__alloc_pages_nodemask) from []
> (cache_alloc_refill+0x1eb/0x3ac)
> [24032.556952] [] (cache_alloc_refill) from []
> (__kmalloc+0x101/0x120)
> [24032.556978] [] (__kmalloc) from []
> (edma_prep_slave_sg+0x77/0x224)
> [24032.557002] [] (edma_pre

[beagleboard] problem of SD and cache

[Micka]

Hi,

I've a program that is writing a big file in the SD periodically.

After a long time, I got this error:

why ? How can i fix this problem? Is it the cache ?

[24032.356007] edma 4900.edma: edma_prep_slave_sg: Failed to
allocate a descriptor
[24032.364121] omap_hsmmc 4806.mmc: prep_slave_sg() failed
[24032.368114] omap_hsmmc 4806.mmc: MMC start dma failure
[24032.392355] mmcblk0: unknown error -1 sending read/write command,
card status 0x900
[24032.478884] mmc0: tried to reset card
[24032.479662] mmcqd/0: page allocation failure: order:2, mode:0x2204020
[24032.479678] CPU: 0 PID: 73 Comm: mmcqd/0 Not tainted 4.4.13-bone11 #153
[24032.479686] Hardware name: Generic AM33XX (Flattened Device Tree)
[24032.479738] [] (unwind_backtrace) from []
(show_stack+0x11/0x14)
[24032.479762] [] (show_stack) from []
(warn_alloc_failed+0xb5/0xf0)
[24032.479780] [] (warn_alloc_failed) from []
(__alloc_pages_nodemask+0x5d1/0x704)
[24032.479801] [] (__alloc_pages_nodemask) from []
(cache_alloc_refill+0x1eb/0x3ac)
[24032.479815] [] (cache_alloc_refill) from []
(__kmalloc+0x101/0x120)
[24032.479840] [] (__kmalloc) from []
(edma_prep_slave_sg+0x77/0x224)
[24032.479864] [] (edma_prep_slave_sg) from []
(omap_hsmmc_request+0x33d/0x3f4)
[24032.479888] [] (omap_hsmmc_request) from []
(mmc_start_request+0xcb/0x1ac)
[24032.479904] [] (mmc_start_request) from []
(mmc_start_req+0x1f3/0x2c4)
[24032.479919] [] (mmc_start_req) from []
(mmc_blk_issue_rw_rq+0x273/0x7ac)
[24032.479932] [] (mmc_blk_issue_rw_rq) from []
(mmc_blk_issue_rq+0x1a3/0x368)
[24032.479943] [] (mmc_blk_issue_rq) from []
(mmc_queue_thread+0x77/0x114)
[24032.479966] [] (mmc_queue_thread) from []
(kthread+0xa3/0xb8)
[24032.479982] [] (kthread) from []
(ret_from_fork+0x11/0x1c)
[24032.479989] Mem-Info:
[24032.480009] active_anon:35548 inactive_anon:7471 isolated_anon:0
 active_file:32682 inactive_file:35639 isolated_file:0
 unevictable:0 dirty:9070 writeback:4648 unstable:0
 slab_reclaimable:4384 slab_unreclaimable:1977
 mapped:19167 shmem:24293 pagetables:345 bounce:0
 free:1490 free_pcp:125 free_cma:0
[24032.480049] Normal free:5960kB min:2752kB low:3440kB high:4128kB
active_anon:142192kB inactive_anon:29884kB active_file:130728kB
inactive_file:142556kB unevictable:0kB isolated(anon):0kB
isolated(file):0kB present:524288kB managed:506492kB mlocked:0kB
dirty:36280kB writeback:18592kB mapped:76668kB shmem:97172kB
slab_reclaimable:17536kB slab_unreclaimable:7908kB kernel_stack:1104kB
pagetables:1380kB unstable:0kB bounce:0kB free_pcp:500kB
local_pcp:500kB free_cma:0kB writeback_tmp:0kB pages_scanned:0
all_unreclaimable? no
[24032.480058] lowmem_reserve[]: 0 0 0
[24032.480069] Normal: 576*4kB (UME) 457*8kB (U) 0*16kB 0*32kB 0*64kB
0*128kB 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB 0*8192kB = 5960kB
[24032.480101] 92614 total pagecache pages
[24032.480113] 0 pages in swap cache
[24032.480119] Swap cache stats: add 0, delete 0, find 0/0
[24032.480124] Free swap  = 0kB
[24032.480129] Total swap = 0kB
[24032.480134] 131072 pages RAM
[24032.480138] 0 pages HighMem/MovableOnly
[24032.480144] 4449 pages reserved
[24032.480148] 6144 pages cma reserved
[24032.480165] edma 4900.edma: edma_prep_slave_sg: Failed to
allocate a descriptor
[24032.488265] omap_hsmmc 4806.mmc: prep_slave_sg() failed
[24032.492250] omap_hsmmc 4806.mmc: MMC start dma failure
[24032.533988] mmcblk0: unknown error -1 sending read/write command,
card status 0x900
[24032.544849] EXT4-fs warning (device mmcblk0p1): ext4_end_bio:329:
I/O error -5 writing to inode 3696 (offset 8388608 size 8388608
starting block 2369280)
[24032.556785] mmcqd/0: page allocation failure: order:2, mode:0x2204020
[24032.556814] CPU: 0 PID: 73 Comm: mmcqd/0 Not tainted 4.4.13-bone11 #153
[24032.556821] Hardware name: Generic AM33XX (Flattened Device Tree)
[24032.556874] [] (unwind_backtrace) from []
(show_stack+0x11/0x14)
[24032.556898] [] (show_stack) from []
(warn_alloc_failed+0xb5/0xf0)
[24032.556917] [] (warn_alloc_failed) from []
(__alloc_pages_nodemask+0x5d1/0x704)
[24032.556938] [] (__alloc_pages_nodemask) from []
(cache_alloc_refill+0x1eb/0x3ac)
[24032.556952] [] (cache_alloc_refill) from []
(__kmalloc+0x101/0x120)
[24032.556978] [] (__kmalloc) from []
(edma_prep_slave_sg+0x77/0x224)
[24032.557002] [] (edma_prep_slave_sg) from []
(omap_hsmmc_request+0x33d/0x3f4)
[24032.557028] [] (omap_hsmmc_request) from []
(mmc_start_request+0xcb/0x1ac)
[24032.557043] [] (mmc_start_request) from []
(mmc_start_req+0x1f3/0x2c4)
[24032.557057] [] (mmc_start_req) from []
(mmc_blk_issue_rw_rq+0x1b5/0x7ac)
[24032.557070] [] (mmc_blk_issue_rw_rq) from []
(mmc_blk_issue_rq+0x1a3/0x368)
[24032.557081] [] (mmc_blk_issue_rq) from []
(mmc_queue_thread+0x77/0x114)
[24032.557105] [] (mmc_queue_thread) from []
(kthread+0xa3/0xb8)
[24032.557121] [] (kthread) from []
(ret_from_fork+0x11/0x1c)
[24032.557129] Mem-Info:
[24032.557148] active_anon:35548 inactive_anon:7471 isolated_anon:0
 active_file:32685 inactive_file:35730 

Re: [beagleboard] Beaglebone Black WVGA

[Micka]

Achète le livre.
Buy the book. And Enjoy!

http://exploringbeaglebone.com/

Le ven. 6 nov. 2020 à 14:05, seb.pi...@sfr.fr  a
écrit :

>
> Hello,
>
> I will want to use a WVGA 800x480 touchscreen with beaglebone black,
> I have QT Designer for menu and source code compile (CCS),
> will someone have some sample code to get started?
> Best regards
> Sébastien
> seb.pi...@sfr.fr
>
> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/07d82754-9e14-48c6-b4ba-3de7ba4f5237o%40googlegroups.com
> 
> .
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAF%2BMRtn%3D%2BdACS%2BJOiDLqLEZztf5BzJMC1on2zbnT_nk4AYzNEw%40mail.gmail.com.

Re: [beagleboard] Re: Optimization of pthread_mutex_lock in the application code

[Micka]

Usleep function Google! Best place to find your answer!

Le jeu. 3 sept. 2020 à 09:52, Niresh  a écrit :

> Thank you, Like you said sleep(1/2) won't work, then how to give a sleep
> of 500ms.
>
> Regards,
> NK
>
> On Thu, Sep 3, 2020 at 1:19 PM Micka  wrote:
>
>> It's not the best place to discuss this topic here .
>>
>> have a look here:
>>
>>
>> https://stackoverflow.com/questions/6460542/performance-of-pthread-mutex-lock-unlock
>>
>>
>> On Thu, Sep 3, 2020 at 9:46 AM Niresh  wrote:
>>
>>>
>>> Sorry I did not finish the thing and got posted accidentally
>>> For example, I have two thread sharing a global shared memory variable
>>> as below. The variable shmPtr->status is protected with mutex lock in both
>>> the function. Though there is a sleep(1/2) between mutex lock inside "for
>>> loop" in the task1 function , I could not access the shmPtr->status in
>>> task2 when required and have to wait until "for loop" exit in the task1
>>> function, this takes around 50 seconds to take control of shmPtr->status by
>>> the task2 function.
>>>
>>> I am wondering why the task1 function is not releasing the mutex lock
>>> even with an sleep(1/2).
>>>
>>> thr_id1 = pthread_create ( _thread1, NULL, (void *)execution_task1,
>>> NULL );
>>> thr_id2 = pthread_create ( _thread2, NULL, (void *)execution_task2,
>>> NULL );
>>>
>>> void execution_task1()
>>> {
>>>  for(int i = 0;i < 100;i++)
>>>  {
>>>   //100 lines of application code running here
>>>   pthread_mutex_lock();
>>> shmPtr->status = 1;  //shared memory variable
>>>  pthread_mutex_unlock();
>>>  sleep(1/2);
>>>  }
>>> }
>>>
>>> void execution_task2()
>>> {
>>>//100 lines of application code running here
>>>   pthread_mutex_lock();
>>> shmPtr->status = 0;  //shared memory variable
>>>  pthread_mutex_unlock();
>>>  sleep(1/2);
>>> }
>>>
>>> Regards,
>>> NK
>>> On Thursday, September 3, 2020 at 12:55:48 PM UTC+5:30 Niresh wrote:
>>>
>>>> Hi,
>>>>
>>>> I am using beagle Bone Black with debian image. Could any please
>>>> suggest how to optimize the application code using pthread_mutex_lock. Let
>>>> me describe the solution I am looking at.
>>>>
>>>> For example, I have two thread sharing a global shared memory variable
>>>> as below
>>>>
>>>> thr_id1 = pthread_create ( _thread1, NULL, (void *)execution_task1,
>>>> NULL );
>>>> thr_id2 = pthread_create ( _thread2, NULL, (void *)execution_task2,
>>>> NULL );
>>>>
>>>> void execution_task1()
>>>> {
>>>>
>>>>  for(int i = 0;i < 100;i++)
>>>>  {
>>>>   pthread_mutex_lock();
>>>> shmPtr->status = 1;
>>>> pthread_mutex_unlock();
>>>> sleep(1/2);
>>>>  }
>>>> }
>>>>
>>> --
>>> 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.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/beagleboard/1d7fc600-e5da-4fbc-b26a-fa1f0c3a3514n%40googlegroups.com
>>> <https://groups.google.com/d/msgid/beagleboard/1d7fc600-e5da-4fbc-b26a-fa1f0c3a3514n%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>>
>> --
>> For more options, visit http://beagleboard.org/discuss
>> ---
>> You received this message because you are subscribed to a topic in the
>> Google Groups "BeagleBoard" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/beagleboard/-9GlXf8Y9ns/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> beagleboard+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/beagleboard/CAF%2BMRt%3DAQktRK_NgTmxFCvR3NVyudd9NBgwWTt7h-5Ub7ftk7w%40mail.gmail.com
>> <http

Re: [beagleboard] Re: Optimization of pthread_mutex_lock in the application code

[Micka]

It's not the best place to discuss this topic here .

have a look here:

https://stackoverflow.com/questions/6460542/performance-of-pthread-mutex-lock-unlock


On Thu, Sep 3, 2020 at 9:46 AM Niresh  wrote:

>
> Sorry I did not finish the thing and got posted accidentally
> For example, I have two thread sharing a global shared memory variable as
> below. The variable shmPtr->status is protected with mutex lock in both the
> function. Though there is a sleep(1/2) between mutex lock inside "for loop"
> in the task1 function , I could not access the shmPtr->status in task2 when
> required and have to wait until "for loop" exit in the task1 function, this
> takes around 50 seconds to take control of shmPtr->status by the task2
> function.
>
> I am wondering why the task1 function is not releasing the mutex lock even
> with an sleep(1/2).
>
> thr_id1 = pthread_create ( _thread1, NULL, (void *)execution_task1, NULL
> );
> thr_id2 = pthread_create ( _thread2, NULL, (void *)execution_task2, NULL
> );
>
> void execution_task1()
> {
>  for(int i = 0;i < 100;i++)
>  {
>   //100 lines of application code running here
>   pthread_mutex_lock();
> shmPtr->status = 1;  //shared memory variable
>  pthread_mutex_unlock();
>  sleep(1/2);
>  }
> }
>
> void execution_task2()
> {
>//100 lines of application code running here
>   pthread_mutex_lock();
> shmPtr->status = 0;  //shared memory variable
>  pthread_mutex_unlock();
>  sleep(1/2);
> }
>
> Regards,
> NK
> On Thursday, September 3, 2020 at 12:55:48 PM UTC+5:30 Niresh wrote:
>
>> Hi,
>>
>> I am using beagle Bone Black with debian image. Could any please suggest
>> how to optimize the application code using pthread_mutex_lock. Let me
>> describe the solution I am looking at.
>>
>> For example, I have two thread sharing a global shared memory variable as
>> below
>>
>> thr_id1 = pthread_create ( _thread1, NULL, (void *)execution_task1,
>> NULL );
>> thr_id2 = pthread_create ( _thread2, NULL, (void *)execution_task2,
>> NULL );
>>
>> void execution_task1()
>> {
>>
>>  for(int i = 0;i < 100;i++)
>>  {
>>   pthread_mutex_lock();
>> shmPtr->status = 1;
>> pthread_mutex_unlock();
>> sleep(1/2);
>>  }
>> }
>>
> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/1d7fc600-e5da-4fbc-b26a-fa1f0c3a3514n%40googlegroups.com
> 
> .
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAF%2BMRt%3DAQktRK_NgTmxFCvR3NVyudd9NBgwWTt7h-5Ub7ftk7w%40mail.gmail.com.

Re: [beagleboard] Optimization of pthread_mutex_lock in the application code

[Micka]

Why would you optimize the mutex ?

sleep(1/2); ==> doesn't work , because 1/2 is cast to 0.

On Thu, Sep 3, 2020 at 9:25 AM Niresh  wrote:

> Hi,
>
> I am using beagle Bone Black with debian image. Could any please suggest
> how to optimize the application code using pthread_mutex_lock. Let me
> describe the solution I am looking at.
>
> For example, I have two thread sharing a global shared memory variable as
> below
>
> thr_id1 = pthread_create ( _thread1, NULL, (void *)execution_task1, NULL
> );
> thr_id2 = pthread_create ( _thread2, NULL, (void *)execution_task2, NULL
> );
>
> void execution_task1()
> {
>
>  for(int i = 0;i < 100;i++)
>  {
>   pthread_mutex_lock();
> shmPtr->status = 1;
> pthread_mutex_unlock();
> sleep(1/2);
>  }
> }
>
> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/fe4074cd-ff97-4e7c-8d68-02ba9a0d5678n%40googlegroups.com
> 
> .
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAF%2BMRtk95cuAO3NteqTaVBp9Drd%2B5waKT9BjGEYYdnD9Oz-E3A%40mail.gmail.com.

Re: [beagleboard] RS485 with CBB-Serial-r02

[Micka]

Can someone explain me why we can't use the rts signal for the rs485 ?

Le mer. 17 juin 2020 à 00:24, Bekir Bahadir  a
écrit :

> Also Im trying to get rs485 work over gpio with active high when
> transmitting. Can anyone help? Ive creqtet a net dts with the gpios for
> enabling the transmitter. Fo i need to patch the kernel for rs485 or is it
> alreqdy included in the omap driver?
>
> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/ce353b99-82d0-4b35-b310-fc4d756d391co%40googlegroups.com
> .
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAF%2BMRtm%3DppGWXAmjp74EjTFgzPrmPJGE4i07KkGtmvRXR-4NMw%40mail.gmail.com.

[beagleboard] beaglebone black am335X new version ?

[Micka]

Hi,

I would like to know when TI is expecting to end the production of the
am335X that the beaglebone black used ? And when the beaglebone black is
expected to have a new processor ? 2 years ?


Michael Musset,

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAF%2BMRtkiemn%2BAzK0JAMrTtyCLc9gX7WwKwkKn2QG24G%2BQkhGrw%40mail.gmail.com.

[beagleboard] Re: platformIO IDE & beaglebone black

[Micka]

I found this:

https://github.com/platformio/platform-linux_arm

On Wed, Nov 6, 2019 at 8:57 AM Micka  wrote:
>
> Hi,
>
> I would like to know if someone know how to use the new IDE platformIO :
>
> https://community.platformio.org/t/platformio-for-beaglebone/3713
>
>
> Micka,

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAF%2BMRt%3DNYVLEvpGx7azOTmSSc-M7ZPmqST%2BJQd%2B_KGcdw2GqyA%40mail.gmail.com.

[beagleboard] platformIO IDE & beaglebone black

[Micka]

Hi,

I would like to know if someone know how to use the new IDE platformIO :

https://community.platformio.org/t/platformio-for-beaglebone/3713


Micka,

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAF%2BMRtnP9WZupJkBzrK7zh%2Bj2awe-0yi%2BNNPhEPi_O7x3aAhzg%40mail.gmail.com.

Re: [beagleboard] Re: which kernel source for bbb ?

[Micka]

I would like that someone tell us which source is more reliable, more
up to date for the beagleboneblack :

https://github.com/RobertCNelson/bb-kernel
https://github.com/beagleboard/linux

On Thu, Sep 12, 2019 at 8:14 PM Mark A. Yoder  wrote:
>
> Good idea.  I've just put in a pull request with a more helpful README.md
>
> --Mark
>
> On Thursday, September 12, 2019 at 11:00:13 AM UTC-4, Dennis Lee Bieber wrote:
>>
>> On Wed, 11 Sep 2019 14:06:07 -0700 (PDT), "Mark A. Yoder"
>>  declaimed the
>> following:
>>
>> >Recheck https://github.com/RobertCNelson/bb-kernel
>> >.
>> >If you change the branch you'll find it was updated a couple of days ago.
>> >
>>
>> Okay -- so I normally don't use GIT, and never used branches in it...
>>
>>
>> Maybe the readme for master could add some clause about "current
>> development is found under branches" 
>>
>>
>> --
>> Wulfraed Dennis Lee Bieber AF6VN
>> wlf...@ix.netcom.comhttp://wlfraed.microdiversity.freeddns.org/
>>
> --
> 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.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/beagleboard/621a9540-f5cc-43e7-b396-26e95e292313%40googlegroups.com.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAF%2BMRt%3D3QypZcgNkz3be8CZ0htGBC3Jhf_wSf2JGQZwBuwWZ2g%40mail.gmail.com.

Re: [beagleboard] Re: which kernel source for bbb ?

[Micka]

 I prefer also https://github.com/RobertCNelson/bb-kernel
there is everything to compile easily and deploy the kernel.

But I would like to know the difference with

https://github.com/beagleboard/linux ?

which one is more up to date ?

which one is the best ?

On Wed, Sep 11, 2019 at 11:06 PM Mark A. Yoder  wrote:
>
> Recheck https://github.com/RobertCNelson/bb-kernel.  If you change the branch 
> you'll find it was updated a couple of days ago.
>
> In fact, that's the one I point my students to 
> (https://elinux.org/EBC_Exercise_08_Installing_Development_Tools_4.4)  Once 
> the desired branch is selected, it has scripts to load the correct cross 
> compiler and the kernel and compile everything.
>
> --Mark
>
> On Wednesday, September 11, 2019 at 2:44:43 PM UTC-4, Dennis Lee Bieber wrote:
>>
>> On Wed, 11 Sep 2019 09:04:15 +0200, Micka
>>  declaimed the
>> following:
>>
>> >Hi, which one do you advise ?
>> >
>>
>> Did you examine what each of those contains?
>>
>>
>> >https://github.com/RobertCNelson/ti-linux-kernel-dev
>>
>> Per the readme, that is just a bunch of scripts for building the
>> kernel, but the source is elsewhere...
>>
>>
>> >https://github.com/RobertCNelson/bb-kernel
>>
>> Last updated in 2014 -- I'd consider that quite dead
>>
>>
>> >https://github.com/beagleboard/linux
>>
>> Readme implies four kernel versions in both normal and RT variants, 
>> and
>> updated last week...
>>
>>
>> --
>> Wulfraed Dennis Lee Bieber AF6VN
>> wlf...@ix.netcom.comhttp://wlfraed.microdiversity.freeddns.org/
>>
> --
> 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.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/beagleboard/4f56ec54-ff33-4e11-8219-ce0b40a8b3bd%40googlegroups.com.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAF%2BMRtkr17RKJjC_NftSRZ%3DmspmKPHBv17E-wvtwd4AhAb74PQ%40mail.gmail.com.

[beagleboard] which kernel source for bbb ?

[Micka]

Hi, which one do you advise ?

https://github.com/RobertCNelson/ti-linux-kernel-dev
https://github.com/RobertCNelson/bb-kernel
https://github.com/beagleboard/linux


what is the difference ?


Micka,

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAF%2BMRt%3D%3DOpxOsMYaRZWM55V3DS4oYaZBJqLZzBEnmaW6U%3DOvQA%40mail.gmail.com.

[beagleboard] Re: beaglebone black & service systemd-fsck

[Micka]

Looks like it's working, I don't have to enable it. Sorry.

 systemctl status systemd-fsck-root.service
● systemd-fsck-root.service - File System Check on Root Device
   Loaded: loaded (/lib/systemd/system/systemd-fsck-root.service;
static; vendor preset: enabled)

On Fri, Jul 5, 2019 at 10:40 AM Micka  wrote:
>
> Hi,
>
> I woud like to activate the service :
> systemd-fsck
>
> I tried:
>
> systemctl enable systemd-fsck@dev-mmcblk0p1.service
>
> but it's not working.
>
>
> I have those files:
> ls /lib/systemd/system/systemd-fsck*
> /lib/systemd/system/systemd-fsck-root.service
> /lib/systemd/system/systemd-fsck@.service
> /lib/systemd/system/systemd-fsckd.service
> /lib/systemd/system/systemd-fsckd.socket
>
>
> Does someone know how to activate the service ?

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAF%2BMRtmSfAicf8vfrf1su12QV89C4xw6D1_Meqp_SfU0%3DYuhdQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] beaglebone black & service systemd-fsck

[Micka]

Hi,

I woud like to activate the service :
systemd-fsck

I tried:

systemctl enable systemd-fsck@dev-mmcblk0p1.service

but it's not working.


I have those files:
ls /lib/systemd/system/systemd-fsck*
/lib/systemd/system/systemd-fsck-root.service
/lib/systemd/system/systemd-fsck@.service
/lib/systemd/system/systemd-fsckd.service
/lib/systemd/system/systemd-fsckd.socket


Does someone know how to activate the service ?

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAF%2BMRtnKOZteK2Lm3R9onoAm5iZ0nMKdNdOTrVLvcVYuwOF_XQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] beaglebone black Ethernet via SPI

[Micka]

Hi,

I would like to know if someone know an ethernet component that works well
with the SPI interface.

If this component is supported, do you know if the driver is available ?


Michael,

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAF%2BMRt%3De318rr218MqfNsZzccFhiRBRpNr9%2BwUaB9RbaE3gJ5Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Android Go & BBB

[Micka]

Hi,

I wanted to know if anyone have tried to use Android Go on the Beaglebone
black.

How much space is left ? Does it consume a lot ?


Michael,

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAF%2BMRtnP1rzOe4pTZV%2BMBzdqkUsLa8J0i_PH9bE4RTjE967j4w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] uboot fdtfile and fdtbase env

[Micka]

Hi, I know what fdtfile is used to, but I don't know what fdtbase is used
to ?

Micka,

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAF%2BMRtkkRCr8uo%3DA4AqqLijmqNnUc5tTMehfv3QBaAoyQwKMiw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Beaglebone black : Uboot & SPI driver

[Micka]

I saw it, but I thought that was for beagleboard or x15.

Le mar. 13 févr. 2018 à 15:40, Robert Nelson <robertcnel...@gmail.com> a
écrit :

> On Tue, Feb 13, 2018 at 7:05 AM, Micka <mickamus...@gmail.com> wrote:
> > Hi,
> >
> > I don't see any SPI driver for the AM335X. I guess that I need to port
> the
> > spi driver from the kernel.
> >
> > If someone know where I can find one, I' m interesting !
>
> https://github.com/u-boot/u-boot/blob/master/drivers/spi/omap3_spi.c
>
> Regards,
>
> --
> Robert Nelson
> https://rcn-ee.com/
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAF%2BMRtmAsmgkbmS96Z7k8w0thqibrFUGOYM9JjWiaR9EtaHsTA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Beaglebone black : Uboot & SPI driver

[Micka]

Hi,

I don't see any SPI driver for the AM335X. I guess that I need to port the
spi driver from the kernel.

If someone know where I can find one, I' m interesting !

Micka,

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAF%2BMRt%3D3B8OO3hsrHrDoTHSMFDzqsxRdPWxb9A8hxxxuFYbqcg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] x15 expansion connectors

[Micka]

Gerald any news on a future beagleboard x15 cape ?

Thanks,

Le dim. 11 sept. 2016 à 20:07, Gerald Coley  a
écrit :

> It is in the System Reference manual.
> The connector for the X15  is also listed in the BOM, but you need the
> mating connector for the one in the BOM.
>
> Gerald
>
> On Sun, Sep 11, 2016 at 10:06 AM, Andrew Goh  wrote:
>
>> https://groups.google.com/forum/#!topic/beagleboard-x15/Pdp12O1TRnI
>>
>>>
>>> Hi -
>>>
>>> Is the part number/spec for the expansion connector available somewhere
>>> or still waiting for public release? Was unable to find anything with
>>> go-ogle
>>>
>>  Gerald Coley
>>
>> [image: Auto Generated Inline Image 1]
>> Feb 19
>> Mating connector is Hirose FX18-60S-0.8SV15
>>
>> 
>> it'd seem a little unfortunate that a 'custom' connector needs to be
>> used, but i'd guess it can't really be helped given the high density
>> developing capes for it could be tough for a home hobbyist and i'd guess
>> it could be rather expensive for commercial capes
>>
>> --
>> 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.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/beagleboard/607b20dc-dbcf-47dd-8379-10f7946bcb6b%40googlegroups.com
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> Gerald
>
> ger...@beagleboard.org
> http://beagleboard.org/
> gcol...@emprodesign.com
>
> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/CAHK_S%2BcjAnSchcuz7geprzX%3DcNdP8FmCKvHpx2SzO16H3790AA%40mail.gmail.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAF%2BMRt%3DrwAK5zsfL8siEQP5nKTKqMA7zAKkcO6WxDzP0Z9_XXw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Process accounting resumed

[Micka]

Hi,

periodically I've this message in my kernel. Does someone know what is it ?


I found that:

/* * Check the amount of free space and suspend/resume accordingly.
*/static int check_free_space
(struct
bsd_acct_struct

*acct ){
struct kstatfs
 sbuf;

if (time_is_before_jiffies
(acct
->needcheck))
goto out;

/* May block */
if (vfs_statfs
(
->file->f_path,
))
goto out;

if (acct 
->active
) {
u64 suspend 

= sbuf.f_blocks * SUSPEND
;
do_div 
(suspend
, 100);
if (sbuf.f_bavail <= suspend
) {
acct 
->active
 = 0;
pr_info 
("Process
accounting paused\n");
}
} else {
u64 resume 

= sbuf.f_blocks * RESUME
;
do_div 
(resume
, 100);
if (sbuf.f_bavail >= resume
) {
acct 
->active
 = 1;
pr_info 
("Process
accounting resumed\n");
}
}

acct 
->needcheck
= jiffies 
+ ACCT_TIMEOUT 
*HZ
;out:
return acct 
->active
;}


does it mean I don't have anymore space available in my linux ?

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAF%2BMRtnFfuZKzMkzqa%3DmXobW_QYgmBsyrEvWPBKXuqy16XBQPA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

RE: [beagleboard] pcie expansion?

[Micka]

The x15 is already out? What do you mean by "X15 ramped"? 

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/4e8fa922-4e1b-4e25-a508-34bbacb268d4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] pcie expansion?

[Micka]

Gerald any news on the expansion board? 

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/0ccfb9a2-128b-405c-9558-95e4a561db32%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] smartctl and sdcard

[Micka]

I'm able with the PC to use the command smartctl to get info on my SDCard
with the protocol SMART.

I found a lot of subject on this topic, and I'm working on this piece of
code for the moment:

int ret = 0;
struct mmc_ioc_cmd idata;
memset(, 0, sizeof(idata));
memset(ext_csd, 0, sizeof(__u8) * 512);
idata.write_flag = 0;
idata.opcode = MMC_SEND_EXT_CSD;
idata.arg = 0;
idata.flags = MMC_RSP_SPI_R1 | MMC_RSP_R1 | MMC_CMD_ADTC;
idata.blksz = 512;
idata.blocks = 1;
mmc_ioc_cmd_set_data(idata, ext_csd);

But no result for the moment!


Le mar. 30 mai 2017 à 15:49, Przemek Klosowski <przemek.klosow...@gmail.com>
a écrit :

> SMART protocol is defined for ATA interface, and it is translated over USB
> interface by most but not all USB-ATA bridges. I have never seen it
> implemented for SD cards. Historically, it makes sense: SD card firmware is
> just a tiny block management layer, although of course there's no
> fundamental reason why it  couldn't be expanded to provide some of the
> internal information via SMART---but it has never been done AFAIK.
>
> On Tue, May 30, 2017 at 8:17 AM, Micka <mickamus...@gmail.com> wrote:
>
>> Hi,
>>
>> I wanted to know if someone successfully used the command smartctl with
>> the sd card ?
>>
>>
>> It could be so usefull to know the state of the sdcard, the remaining
>> life, etc !
>>
>> --
>> 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.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/beagleboard/CAF%2BMRtnD2qk7RHc6rxzuX9DRT0kNE30-kO1vKRBAzw%3D%2B-FZ6yw%40mail.gmail.com
>> <https://groups.google.com/d/msgid/beagleboard/CAF%2BMRtnD2qk7RHc6rxzuX9DRT0kNE30-kO1vKRBAzw%3D%2B-FZ6yw%40mail.gmail.com?utm_medium=email_source=footer>
>> .
>> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/CAC%3D1GgHV050he1CYE2mJ%3D3KHgyPpLez8-Z%3Dn_TFgD8xVR4KK6w%40mail.gmail.com
> <https://groups.google.com/d/msgid/beagleboard/CAC%3D1GgHV050he1CYE2mJ%3D3KHgyPpLez8-Z%3Dn_TFgD8xVR4KK6w%40mail.gmail.com?utm_medium=email_source=footer>
> .
> 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAF%2BMRtm7eBZTajzhdFcT_32h7r%2Bq9kEYKehk23gcCs8HB5PsEg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] smartctl and sdcard

[Micka]

Hi,

I wanted to know if someone successfully used the command smartctl with the
sd card ?


It could be so usefull to know the state of the sdcard, the remaining life,
etc !

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAF%2BMRtnD2qk7RHc6rxzuX9DRT0kNE30-kO1vKRBAzw%3D%2B-FZ6yw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] update the beagle kernel with ftp when it's running

[Micka]

Well, I don't mind to reboot the beagle after. I was just wondering if it's
possible to untar all the file while the beagle is running ? I'm worried
about some file open by the kernel/linux !

Micka,

Le mar. 25 avr. 2017 à 17:03, Robert Nelson <robertcnel...@gmail.com> a
écrit :

> On Tue, Apr 25, 2017 at 9:59 AM, Micka <mickamus...@gmail.com> wrote:
> > Hi,
> >
> > I would like to know if someone has tried to update the kernel while the
> > beagle is running ? Is it possible ?
> >
> > Robert Nelson, when you compile the kernel, you put files in the
> > bb-kernel/deploy folder. Can I copy those files to the beagle and untar
> > during the boot ?
>
> kexec is enabled, try it ;)
>
> Regards,
>
>
> --
> Robert Nelson
> https://rcn-ee.com/
>
> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/CAOCHtYhKsv%3D_hqyKR5fJBrCoa%3DNdbbzw5rQrP1ONM95crgWa3g%40mail.gmail.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAF%2BMRtmOAa7%3DtzdtYpUgQQKXYcf88ND7Gq0zXv6Ms%3DGcj%2B%2BVog%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] update the beagle kernel with ftp when it's running

[Micka]

Hi,

I would like to know if someone has tried to update the kernel while the
beagle is running ? Is it possible ?

Robert Nelson, when you compile the kernel, you put files in the
bb-kernel/deploy folder. Can I copy those files to the beagle and untar
during the boot ?

Micka,

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAF%2BMRtk9xvTQqcJAeQRqDZaYh8%2BAc7UJr-tY6oE03kJvduo0Kw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Detecting state of GPIO pins during boot up

[Micka]

create a systemd service that will launch a bash code that check the gpio .
If the gpio is is at value 1, switch a led on to tell the user to remove
his finger. After detecting the factory reset, do what you want in your
system.

Le mar. 28 mars 2017 à 21:29, Rao Gobburu  a écrit :

> Hi folks
> I hope that I am posting to the correct group apologies if this is the
> wrong place.
> We are creating a system based on the beagleboard black. We would like to
> implement a "Factory Reset". i.e. if I hold down a switch for a long period
> of time, say around 10 seconds, then we want to completely reset the
> system.
> Essentially the Reset pin is tied to one of the GPIO pins. So the GPIO
> follows the Reset pin.
> We would like to detect if the GPIO pin is still low about 10 seconds
> after the Reset has been asserted.
> The issue is that this is the time when the system is still booting up. I
> am not sure how one could check on the status of the pin during the boot up.
> Any ideas?
> Thanks a lot
> Rao
>
>
>
> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/8dac92bb-1d9e-462b-8955-11bfc00f7706%40googlegroups.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAF%2BMRt%3D93mnAnSSebhAjJnO5kL8857%2BfHatqiweKGdUVvziZkg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: BBB UART4 RTS for RS-485

[Micka]

There is no problem with the kernel 4.4 and rs485. Just use the omap driver
and not the 8250 driver. It works well for me since 4 years.

Le ven. 24 mars 2017 11:24,  a écrit :

> Hi,
>
> We are having allot of problems getting RS485 with RTS working on Debian:
> Linux 4.4
> CAn someone help?
>
>
> On Thursday, March 23, 2017 at 9:13:23 PM UTC+2, bmel...@gmail.com wrote:
>
> Hi Alexander,
>
> The link you provided does not work:
>
>
> http://inspire.logicsupply.com/2014/09/beaglebone-rs-485-communication.html
>
>
> Do you mind sending me the tutorial? I am currently designing my own cape
> which will support two RS485 half duplex channels and your tutorial would
> be very helpful to get me started. My questions are:
>
> 1) Am I limited to UART4 or can I use any of the available UARTs on the
> Beaglebone Black?
>
> 2) Just to be 100% sure, I can use any of the GPIO pins for controlling DE
> & /RE pins on the RS485 transceiver (I'm using TI's ISO15MDW)?
>
> Thank you,
>
> Bolek
>
> On Wednesday, September 3, 2014 at 10:07:26 AM UTC-7, Alexander Hiam wrote:
>
> I actually just put up a tutorial for doing this in Python:
> http://inspire.logicsupply.com/2014/09/beaglebone-rs-485-communication.html
>
> It uses GPIO1_16, but of course you can use any GPIO pin, including the
> one that's shared with UART4 RTS.
>
>
> When I tried to use:
> struct serial_rs485 rs485conf;
> rs485conf.flags |= SER_RS485_USE_GPIO;
> rs485conf.gpio_pin = GPIO0_9;
>
> I got error from gcc that it does not know those macros:
> ‘SER_RS485_USE_GPIO’ was not declared in this scope
>  rs485conf.flags |= SER_RS485_USE_GPIO;
> ‘struct serial_rs485’ has no member named ‘gpio_pin’
>   rs485conf.gpio_pin = GPIO0_9;
> ‘GPIO0_9’ was not declared in this scope
>   rs485conf.gpio_pin = GPIO0_9;
>
>
> That's because you're compiling with the standard libc headers, which
> don't include the modified serial_rs485 struct that uses the GPIO pin. The
> tutorial I linked above uses Python and just defines the same values
> locally, which you could do in C as well. You could also grab the Kernel
> source and include 'include/uapi/linux/serial.h', which has the patched
> serial_rs485 struct (
> https://github.com/RobertCNelson/bb-kernel/blob/am33x-v3.8/patches/fixes/0007-omap-RS485-support-by-Michael-Musset.patch#L201
> ).
>
> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/128d1fae-46ac-4e2d-a759-1cb1568f443c%40googlegroups.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAF%2BMRtnVGeQN9qVW7Msi4u3C1YfErKUf8E0Ve1S9%2BGX2nq-1KA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Ssh server

[Micka]

Jaja,

ssh server stop working ? are you sure ? can you ping the beagle ? Most of
the time it's a network problem !

Le mer. 22 mars 2017 à 16:07, William Hermans  a écrit :

>
> On Wed, Mar 22, 2017 at 7:07 AM,  wrote:
>
> Hello everyone,
>
> The beagle bone black board ssh server suddenly stopped working! Please
> can you help me.
>
>
> My mind reading apparatus stopped working ! can you please help me ?
>
> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/CALHSORrhpyhRrbaTrL5jXmw5U__mTcsL6%2B0OKKNcy3ZHELpBxw%40mail.gmail.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAF%2BMRt%3Dm%3DkaaRkK-B0%2BkcnckTKEzT8FS9%3D3f5WXs8fexy%2BQmGg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] What is the reasoning behind the inclusion of connman in the BBB images?

[Micka]

I have no problem to use /etc/network/interfaces . 4 years that I'm using
this without connman.

Micka,

Le mer. 22 mars 2017 à 09:11, 'Luther Goh Lu Feng' via BeagleBoard <
beagleboard@googlegroups.com> a écrit :

> I seek to understand why connman is included in the BBB image?
>
> Without going into details, generally it doesn't seem to be without
> issues. It seems that there are other users[1] uninstalling and using the
> /etc/network/interfaces.
>
> Any issues that could possibly arise with connman uninstallation? Thanks
>
> [1] https://groups.google.com/d/msg/beagleboard/x-QrPydd1Rk/Ldkdnd12CQAJ
>
> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/a23984fc-cc55-4b2c-9dc8-c3b61cf56cfa%40googlegroups.com
> <https://groups.google.com/d/msgid/beagleboard/a23984fc-cc55-4b2c-9dc8-c3b61cf56cfa%40googlegroups.com?utm_medium=email_source=footer>
> .
> 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAF%2BMRt%3D6FrJCB3b-gGxLH2Yd88y9FPmwyLrSgRKb1b%2Bq-oQZLQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Problems using BeagleBone Black's UART

[Micka]

I'm using the Omap driver for RS485, it works well !

Micka,

Le jeu. 9 févr. 2017 à 13:30, <patrick.oet...@gmail.com> a écrit :

> Hello!
>
> I'm trying to use the BeagleBone Black to communicate to RS485 and
> CAN-Devices.
> For testing I ordered the Waveshare RS485-CAN Cape
> <http://www.waveshare.com/rs485-can-cape.htm>. Later on the MAX13487
> should be used for RS485 at UART2. CAN works fine using the BB-CAN1 overlay
> with uEnv.txt (UART1).
>
> But first I tried to communicate from UART1 to UART2, to check if the
> UARTs are working. I added BB-UART1, BB-UART2 and BB-UART4 to uEnv.txt and
> connected UART1 RX to UART2 TX and UART1 TX to UART2 RX (Pins 22 and 24/ 26
> and 21).
>
> After Reboot, the UARTs are activated:
>
> root@beaglebone:/# ls -l /dev/ttyO*
> lrwxrwxrwx 1 root root 5 Feb  7 13:55 /dev/ttyO0 -> ttyS0
> lrwxrwxrwx 1 root root 5 Feb  7 13:55 /dev/ttyO1 -> ttyS1
> lrwxrwxrwx 1 root root 5 Feb  7 13:55 /dev/ttyO2 -> ttyS2
> lrwxrwxrwx 1 root root 5 Feb  7 13:55 /dev/ttyO4 -> ttyS4
>
> root@beaglebone:/# dmesg | grep tty
> [0.00] Kernel command line: console=tty0 console=ttyO0,115200n8
> capemgr.enable_partno=BB-UART1,BB-UART2,BB-UART4, BB-UART5 root=/dev/mmcblk0p1
> rootfstype=ext4 rootwait coherent_pool=1M quiet cape_universal=enable
> [0.001090] console [tty0] enabled
> [0.001109] WARNING: Your 'console=ttyO0' has been replaced by 'ttyS0'
> [3.929029] 44e09000.serial: ttyS0 at MMIO 0x44e09000 (irq = 158,
> base_baud = 300) is a 8250
> [3.941849] console [ttyS0] enabled
> [   22.142299] 48022000.serial: ttyS1 at MMIO 0x48022000 (irq = 189,
> base_baud = 300) is a 8250
> [   22.154538] 48024000.serial: ttyS2 at MMIO 0x48024000 (irq = 190,
> base_baud = 300) is a 8250
> [   22.165780] 481a8000.serial: ttyS4 at MMIO 0x481a8000 (irq = 191,
> base_baud = 300) is a 8250
>
> Most tutorials using an older Debian version are using ttyOx to access the
> serial ports (old OMAP-driver?), but based on this output I have to use
> ttySx with the newer 8250 driver for my commands instead?
>
> I tried to send/receive messages between the UARTs using minicom, screen
> and python scripts, but i can't see any messages at the receiving
> interface. Measuring the sending UARTs TX with an oscilloscope I also can't
> see any signals.
>
> At the moment I am running Debian Image 2016-05-13 with Kernel
> 4.9.8-bone-rt-r4, I also tried everything with the original Kernel of this
> Image (4.4.9?) and a fresh Debian IoT Image 2016-12-09 and also with
> UART2+UART4.
>
> Is there any missing configuration I have to do to get it working?
>
> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/1ce0353f-713c-4fda-afd8-55ac2ca506c7%40googlegroups.com
> <https://groups.google.com/d/msgid/beagleboard/1ce0353f-713c-4fda-afd8-55ac2ca506c7%40googlegroups.com?utm_medium=email_source=footer>
> .
> 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAF%2BMRt%3DcZPzRm9JJMFtc6EeuQZ2CzHfHR2Kk8pQ6ugcsyEVtOw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] InitRamFs

[Micka]

Thx for all, I understand better what is it now.

Micka,

Le jeu. 5 janv. 2017 à 13:01, William Hermans <yyrk...@gmail.com> a écrit :

> My last worklog working with the initrd, which by the way is not required
> _just_to_add_ overlays. Robert has a script that can do this automatically
> for you. Just keep in mind that I tend to make small mistakes once in a
> while so my work logs can be superfluous . . .
>
> http://pastebin.com/naKbbRWd
>
>
> On Thu, Jan 5, 2017 at 4:39 AM, William Hermans <yyrk...@gmail.com> wrote:
>
>
>
> On Thu, Jan 5, 2017 at 4:28 AM, Micka <mickamus...@gmail.com> wrote:
>
> I saw that. But was not sure. The idea is to save the state of your ram?
>
>
> I don't understand your question. But an initial ram disk is a very
> minimalist Linux file system that is loaded at boot. Used for loading
> various drivers, early. So for instance if you wanted to boot from say an
> iSCSI type disk, You'd very likely have to initialize it through an initrd.
>
> Anyway, my definition is rather crude, like I said I'm going form pure
> memory, and my memory is not always accurate. Better that you google for
> your answers.
>
>
> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/CALHSORrT3prnJdFFfRy3TkvPE%3D_SAeUnLq7SsRE7uFt%2BZ%3DTSbA%40mail.gmail.com
> <https://groups.google.com/d/msgid/beagleboard/CALHSORrT3prnJdFFfRy3TkvPE%3D_SAeUnLq7SsRE7uFt%2BZ%3DTSbA%40mail.gmail.com?utm_medium=email_source=footer>
> .
> 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAF%2BMRtn0jQgwawvo9vZzS87K-RnpywPsV1aTMNLS6wVWfCX9vA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] InitRamFs

[Micka]

I saw that. But was not sure. The idea is to save the state of your ram?


Thx,

On Thu, Jan 5, 2017, 12:14 William Hermans <yyrk...@gmail.com> wrote:

> You should really google this Micka,
>
> But initrd == initial ram disk, and initramfs is a cpio archived initial
> ram disk.
>
> On Thu, Jan 5, 2017 at 3:50 AM, Micka <mickamus...@gmail.com> wrote:
>
> Hi, I would like how is it initialized in the beaglebone black ?
>
> What is initrd.img for ?
>
>
> Micka,
>
> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/CAF%2BMRt%3DX6FeAf6T_5zB-XgQeovcdMp3wh-z2Mgz3f%2BqAxmqPHA%40mail.gmail.com
> <https://groups.google.com/d/msgid/beagleboard/CAF%2BMRt%3DX6FeAf6T_5zB-XgQeovcdMp3wh-z2Mgz3f%2BqAxmqPHA%40mail.gmail.com?utm_medium=email_source=footer>
> .
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/CALHSORq7inYkWZCMRY2r_XZnuRdn_WOL-WHR2pdvaWDVknK3Eg%40mail.gmail.com
> <https://groups.google.com/d/msgid/beagleboard/CALHSORq7inYkWZCMRY2r_XZnuRdn_WOL-WHR2pdvaWDVknK3Eg%40mail.gmail.com?utm_medium=email_source=footer>
> .
> 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAF%2BMRtm_uqwjvB2Rnf%3DRLxO%3DULOR76fZ60jvd2G5Y9ZunMTnUQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] InitRamFs

[Micka]

Hi, I would like how is it initialized in the beaglebone black ?

What is initrd.img for ?


Micka,

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAF%2BMRt%3DX6FeAf6T_5zB-XgQeovcdMp3wh-z2Mgz3f%2BqAxmqPHA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] How to change default hwclock on BBB Debian to always be /dev/rtc1?

[Micka]

The problem have been discussed there :

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785445


Le lun. 10 oct. 2016 à 03:54, William Hermans  a écrit :

> The best way I found for myself. Was to simply install ntpdate, run it,
> then update the external real clock from system time. Then, if you
> *absolutely* need rtc0 updated. You update it from the system time. Or
> rtc1. No need to recompile the kernel.
>
> Sure, it's a couple of extra steps, but steps that can be done at boot
> with a simple script / service. Then if you need, or want to update the
> real time clock. Since time on computer can drift. You run a cron job every
> X time frame to run a script that pulls in system time from an atomic
> clock, then re-apply to rtc1.
>
> On Sun, Oct 9, 2016 at 3:21 PM, maxmike  wrote:
>
>
> I don~t think Robert recompiled the kernel. I am using 3.8.13 Debian.
>
> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/4e6fdc99-4137-4c04-8c1d-72fa9de5a6a4%40googlegroups.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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/CALHSORqDsbBWiO%2BJOUPuaeAsG1O%2B4dxiP6G3PqUkOxE1GeVhgA%40mail.gmail.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAF%2BMRt%3Dgm_wZzgJjZYvF2PVdXwWZzj8bVgEWK-LBWYJOwDqeig%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Do not power BBB/BBG via USB?

[Micka]

For my use case it's perfect:

the board is powered by a cape. we disabled power from USB, because the
cape is not made to be powered by the beagle.

and yes you are right, the PPATH is hard reset to 1.

Le mar. 3 janv. 2017 à 10:53, Heinz Hummel <heinz.humme...@gmail.com> a
écrit :

> Hello Micka,
>
> is this permanent? Means does the PMIC know even after a power cycle to
> not to use USB power any more? As far as I understood the description of
> USB_EN in the PPATH register, this is reset to default values after power
> was turned off...
>
> Thanks :-)
>
>
> 2017-01-03 10:48 GMT+01:00 Micka <mickamus...@gmail.com>:
>
> The proper way is to modify the driver tps65217.c :
>
> diff --git a/drivers/mfd/tps65217.c b/drivers/mfd/tps65217.c
> index ca19130..a7ae900 100644
> --- a/drivers/mfd/tps65217.c
> +++ b/drivers/mfd/tps65217.c
> @@ -253,6 +253,7 @@ static int tps65217_probe(struct i2c_client *client,
>   bool status_off = false;
>   int irq = -1, irq_gpio = -1;
>   int ret;
> + bool usb_off = false;
>
>   node = client->dev.of_node;
>   if (node) {
> @@ -265,7 +266,8 @@ static int tps65217_probe(struct i2c_client *client,
>   chip_id = (unsigned long)match->data;
>   status_off = of_property_read_bool(node,
>   "ti,pmic-shutdown-controller");
> -
> + usb_off = of_property_read_bool(node,
> +"ti,pmic-usb-off");
>   /* at first try to get irq via OF method */
>   irq = irq_of_parse_and_map(node, 0);
>   if (irq <= 0) {
> @@ -346,6 +348,16 @@ static int tps65217_probe(struct i2c_client *client,
>   dev_warn(tps->dev, "unable to set the status OFF\n");
>   }
>
> + if(usb_off){
> + ret = tps65217_set_bits(tps, TPS65217_REG_PPATH,
> +TPS65217_PPATH_USB_PW_ENABLE, 0,
> +TPS65217_PROTECT_NONE);
> +if (ret)
> +dev_warn(tps->dev, "unable to set the USB power
> OFF\n");
> + else
> + dev_info(tps->dev, "set the USB power OFF\n");
> + }
> +
>   dev_info(tps->dev, "TPS65217 ID %#x version 1.%d\n",
>   (version & TPS65217_CHIPID_CHIP_MASK) >> 4,
>   version & TPS65217_CHIPID_REV_MASK);
>
>
>
> It worked for me. ( the source is not committed yet because I didn't clean
> the code )
>
>
> Le lun. 2 janv. 2017 à 08:29, Heinz Hummel <heinz.humme...@gmail.com> a
> écrit :
>
> Great - thanks! So there is no way to do that programmatically via PMIC?
>
> 2016-12-29 8:59 GMT+01:00 Alex Hayman <a...@markforged.com>:
>
> If you cut that trace on a BBB, then the BBB won't power itself up via USB.
>
> On Friday, December 23, 2016 at 4:25:08 AM UTC-5, Heinz Hummel wrote:
>
> Hello,
>
> I have a BBB which is currently powered via USB and external power supply
> (and a similar BBG which is powered via USB and via external supply feed
> into VDD from connected cape).
>
> Now when a user wants to do a full power cycle, all possible power sources
> have to be disconnected which can be somewhat complicated.
>
> So my question: is there a possibility to disable power supply via USB?
> E.g. a soldering jumper which has to be opened? Or in case not - is there a
> possibility to permanently program the PMIC to not to power the board from
> USB?
>
> Thanks!
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
>
> You received this message because you are subscribed to a topic in the
> Google Groups "BeagleBoard" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/beagleboard/dR_GhlwG0eM/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> beagleboard+unsubscr...@googlegroups.com.
>
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/5d9e2fb6-14be-4223-9375-2882df001000%40googlegroups.com
> <https://groups.google.com/d/msgid/beagleboard/5d9e2fb6-14be-4223-9375-2882df001000%40googlegroups.com?utm_medium=email_source=footer>
> .
>
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/CAHptrU72B91wEm10m1A1GhP0w8Zug-snhgJiKd1z9aCgeg504w%40mail.gmail.com
> <https://groups.google.com/d/msgid/beagleboard/CAHptrU7

Re: [beagleboard] Re: Do not power BBB/BBG via USB?

[Micka]

The proper way is to modify the driver tps65217.c :

diff --git a/drivers/mfd/tps65217.c b/drivers/mfd/tps65217.c
index ca19130..a7ae900 100644
--- a/drivers/mfd/tps65217.c
+++ b/drivers/mfd/tps65217.c
@@ -253,6 +253,7 @@ static int tps65217_probe(struct i2c_client *client,
  bool status_off = false;
  int irq = -1, irq_gpio = -1;
  int ret;
+ bool usb_off = false;

  node = client->dev.of_node;
  if (node) {
@@ -265,7 +266,8 @@ static int tps65217_probe(struct i2c_client *client,
  chip_id = (unsigned long)match->data;
  status_off = of_property_read_bool(node,
  "ti,pmic-shutdown-controller");
-
+ usb_off = of_property_read_bool(node,
+"ti,pmic-usb-off");
  /* at first try to get irq via OF method */
  irq = irq_of_parse_and_map(node, 0);
  if (irq <= 0) {
@@ -346,6 +348,16 @@ static int tps65217_probe(struct i2c_client *client,
  dev_warn(tps->dev, "unable to set the status OFF\n");
  }

+ if(usb_off){
+ ret = tps65217_set_bits(tps, TPS65217_REG_PPATH,
+TPS65217_PPATH_USB_PW_ENABLE, 0,
+TPS65217_PROTECT_NONE);
+if (ret)
+dev_warn(tps->dev, "unable to set the USB power
OFF\n");
+ else
+ dev_info(tps->dev, "set the USB power OFF\n");
+ }
+
  dev_info(tps->dev, "TPS65217 ID %#x version 1.%d\n",
  (version & TPS65217_CHIPID_CHIP_MASK) >> 4,
  version & TPS65217_CHIPID_REV_MASK);



It worked for me. ( the source is not committed yet because I didn't clean
the code )


Le lun. 2 janv. 2017 à 08:29, Heinz Hummel  a
écrit :

Great - thanks! So there is no way to do that programmatically via PMIC?

2016-12-29 8:59 GMT+01:00 Alex Hayman :

If you cut that trace on a BBB, then the BBB won't power itself up via USB.

On Friday, December 23, 2016 at 4:25:08 AM UTC-5, Heinz Hummel wrote:

Hello,

I have a BBB which is currently powered via USB and external power supply
(and a similar BBG which is powered via USB and via external supply feed
into VDD from connected cape).

Now when a user wants to do a full power cycle, all possible power sources
have to be disconnected which can be somewhat complicated.

So my question: is there a possibility to disable power supply via USB?
E.g. a soldering jumper which has to be opened? Or in case not - is there a
possibility to permanently program the PMIC to not to power the board from
USB?

Thanks!

-- 
For more options, visit http://beagleboard.org/discuss
---

You received this message because you are subscribed to a topic in the
Google Groups "BeagleBoard" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/beagleboard/dR_GhlwG0eM/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
beagleboard+unsubscr...@googlegroups.com.

To view this discussion on the web visit
https://groups.google.com/d/msgid/beagleboard/5d9e2fb6-14be-4223-9375-2882df001000%40googlegroups.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.
To view this discussion on the web visit
https://groups.google.com/d/msgid/beagleboard/CAHptrU72B91wEm10m1A1GhP0w8Zug-snhgJiKd1z9aCgeg504w%40mail.gmail.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAF%2BMRtkXjZqMm9WKaXetSTgM4zeMRtOzq53nKLXir310sp6wmg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] console configuration (ttyO0 or ttyS0)

[Micka]

If I'm not wrong, ttyO0 is for omap driver and ttys0 is for 8250 driver.
That what I understood.

On Wed, Dec 21, 2016, 13:04 Madhu K  wrote:

> Hi All,
>
> I have built kernel and device tree images using beaglebone_defconfig.
>
> After tftp of uImage and dtb, u-boot is getting stuck with "Starting
> Kernel" message( There are no other messages on console). I am doubting on
> my serial configuration, because somebody is using ttyO0 and ttyS0 in
> bootargs.
>
> I am really confused what to use.
>
> I am copying my serial drivers below( this i have taken from .config file
> ). please help me to choose correct tty.
>
>
> #
> # Serial drivers
> #
> CONFIG_SERIAL_8250=y
> CONFIG_SERIAL_8250_DEPRECATED_OPTIONS=y
> CONFIG_SERIAL_8250_CONSOLE=y
> CONFIG_SERIAL_8250_DMA=y
> CONFIG_SERIAL_8250_NR_UARTS=4
> CONFIG_SERIAL_8250_RUNTIME_UARTS=4
> # CONFIG_SERIAL_8250_EXTENDED is n
>
>
> Thanks and regards,
> Madhu
>
> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/b6e8a509-88cb-4405-aaee-3834dcc320d7%40googlegroups.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAF%2BMRtm3%3DKxzx3LCZQmHrDUg-MvvHoj1SrrvTvp7ioES0qdf2A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: possible workaround for BeagleBone Ethernet PHY problems

[Micka]

You should switch to kernel 4.4. Robert Nelson said that the ethernet is
working better. I have a modified hardware so I can't tell.

Micka,

On Tue, Dec 13, 2016, 09:54 Grzegorz G <grzegorz...@gmail.com> wrote:

> current kernel version: Linux beaglebone 3.8.13-bone79 #1 SMP Tue Oct 13
> 20:44:55 UTC 2015 armv7l GNU/Linux
> so it's above bone60 and problem exsist
>
> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/6caaca8f-b893-460b-80c8-2988fd690621%40googlegroups.com
> <https://groups.google.com/d/msgid/beagleboard/6caaca8f-b893-460b-80c8-2988fd690621%40googlegroups.com?utm_medium=email_source=footer>
> .
> 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAF%2BMRtmBrSgPWO-%2BgvH21ttkxhj%3D%2BPX1Aar4hrQjR0PYoeATdQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] PRU UART Debian 8.6

[Micka]

I agree with you William Hermans ! That how it works here !

Le mer. 7 déc. 2016 à 06:14, William Hermans  a écrit :

> Anyway, sorry if that "stings" but hey, it's pretty much the truth. People
> have lives of their own and contribute what they can, when they can. But I
> would assume most people are pretty busy doing stuff for people who
> actually pay them. A lot of the time.
>
> On Tue, Dec 6, 2016 at 10:10 PM, William Hermans 
> wrote:
>
> Did you expect someone to do all the work for you ? But yes, I've
> experienced the same thing. So "free" as in beer, open sourced software.
> You get what you pay for. If you need something more, then it's up to you
> to do that for yourself. Or pay someone else to do it for you.
>
> On Tue, Dec 6, 2016 at 3:42 AM,  wrote:
>
> Hi,  I have found setting the pru uart pins P9_17 and P9_18 to mode 5 does
> not work using config-pins with the latest release Debian 8.6.
> The overlays I used in Debian 7.9 no longer work.  I have found that the
> overlay used to disable the hdmi, univ-emmc-00A0.dtbo does
> not include the pru_uart option for P9_17 and P9_18, whereas
> cape-universal does.  So I copied the entries for P9-17 & -18 over to
> univ-emmc, recompiled and copied to /lib/firmware which seems to solve the
> problem.  Has anyone else had a similar experience?
>
> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/37fbdce6-2cca-4fc1-9a9e-8cde0dce505c%40googlegroups.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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/CALHSORofRhH6CimzB-M%3DGntck82HDfABgWJuesYyzQ8Mf7gc0Q%40mail.gmail.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAF%2BMRtkXEVn3TiSvbckZWMi-18Av8PLTuoJ8NQQCL_hsGFLz%2Bw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Xorg & xf86OpenConsole : setpg Operation not permitted & FBIOPUTCMAP: Invalid argument

[Micka]

I fixed the problem xf86OpenConsole: setpgid failed: Operation not permitted by 
starting serverX with root privilege.

But I can't find a solution for : 

[327741.772] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
[327741.772] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument


Le mardi 6 décembre 2016 10:13:20 UTC+1, Micka a écrit :
>
> Hi, 
>
> I would like to know if someone had already this problem ? Or does someone 
> know how to solve it ?
>
>
> [327741.539] X Protocol Version 11, Revision 0
> [327741.540] Build Operating System: Linux 3.16.0-0.bpo.4-armmp-lpae 
> armv7l Debian
> [327741.540] Current Operating System: Linux alex 4.4.13-bone11 #88 Tue 
> Nov 8 17:53:55 CET 2016 armv7l
> [327741.540] Kernel command line: console=ttyUSB0,115200n8 
> root=/dev/mmcblk0p1 rootfstype=ext4 rootwait coherent_pool=1M quiet splash 
> video=HDMI-A-1:1024x600MR@60e fbcon=rotate:1
> [327741.540] Build Date: 11 February 2015 01:18:06AM
> [327741.540] xorg-server 2:1.16.4-1 (http://www.debian.org/support)
> [327741.540] Current version of pixman: 0.32.6
> [327741.540] Before reporting problems, check http://wiki.x.org
> to make sure that you have the latest version.
> [327741.540] Markers: (--) probed, (**) from config file, (==) default 
> setting,
> (++) from command line, (!!) notice, (II) informational,
> (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
> [327741.543] (==) Log file: "/var/log/Xorg.0.log", Time: Tue Dec 6 
> 09:41:59 2016
> [327741.545] (==) Using config file: "/etc/X11/xorg.conf"
> [327741.546] (==) Using system config directory 
> "/usr/share/X11/xorg.conf.d"
> [327741.549] (==) ServerLayout "Builtin Default Layout"
> [327741.550] (**) |-->Screen "Builtin Default fbdev Screen 0" (0)
> [327741.550] (**) | |-->Monitor "Builtin Default Monitor"
> [327741.551] (**) | |-->Device "Builtin Default fbdev Device 0"
> [327741.551] (**) Option "BlankTime" "0"
> [327741.551] (**) Option "StandbyTime" "0"
> [327741.551] (**) Option "SuspendTime" "0"
> [327741.551] (**) Option "OffTime" "0"
> [327741.551] (==) Automatically adding devices
> [327741.551] (==) Automatically enabling devices
> [327741.551] (==) Automatically adding GPU devices
> [327741.551] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not 
> exist.
> [327741.551] Entry deleted from font path.
> [327741.552] (==) FontPath set to:
> /usr/share/fonts/X11/misc,
> /usr/share/fonts/X11/100dpi/:unscaled,
> /usr/share/fonts/X11/75dpi/:unscaled,
> /usr/share/fonts/X11/Type1,
> /usr/share/fonts/X11/100dpi,
> /usr/share/fonts/X11/75dpi,
> built-ins
> [327741.552] (==) ModulePath set to "/usr/lib/xorg/modules"
> [327741.552] (II) The server relies on udev to provide the list of input 
> devices.
> If no devices become available, reconfigure udev or disable AutoAddDevices.
> [327741.552] (II) Loader magic: 0x7f7a0f18
> [327741.552] (II) Module ABI versions:
> [327741.552] X.Org ANSI C Emulation: 0.4
> [327741.552] X.Org Video Driver: 18.0
> [327741.552] X.Org XInput driver : 21.0
> [327741.552] X.Org Server Extension : 8.0
> [327741.553] (II) xfree86: Adding drm device (/dev/dri/card0)
> [327741.554] (II) no primary bus or device found
> [327741.554] falling back to 
> /sys/devices/platform/ocp/4830e000.lcdc/drm/card0
> [327741.554] (II) LoadModule: "glx"
> [327741.555] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
> [327741.639] (II) Module glx: vendor="X.Org Foundation"
> [327741.639] compiled for 1.16.4, module version = 1.0.0
> [327741.639] ABI class: X.Org Server Extension, version 8.0
> [327741.639] (==) AIGLX enabled
> [327741.639] (II) LoadModule: "fbdev"
> [327741.642] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
> [327741.644] (II) Module fbdev: vendor="X.Org Foundation"
> [327741.644] compiled for 1.15.99.904, module version = 0.4.4
> [327741.645] Module class: X.Org Video Driver
> [327741.645] ABI class: X.Org Video Driver, version 18.0
> [327741.648] (II) FBDEV: driver for framebuffer: fbdev
> [327741.648] (--) using VT number 2
>
> [327741.648] (WW) xf86OpenConsole: setpgid failed: Operation not permitted
> [327741.649] (WW) xf86OpenConsole: setsid failed: Operation not permitted
> [327741.656] (WW) Falling back to old probe method for fbdev
> [327741.657] (II) Loading sub module "fbdevhw"
> [327741.657] (II) LoadModule: "fbdevhw"
> [327741.657] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
> [327741.658] (II) Module fbdevhw: vendor="X.Org Foundation"
> [327741.658] compiled for 1.16.4

[beagleboard] Xorg & xf86OpenConsole : setpg Operation not permitted & FBIOPUTCMAP: Invalid argument

[Micka]

Hi, 

I would like to know if someone had already this problem ? Or does someone 
know how to solve it ?


[327741.539] X Protocol Version 11, Revision 0
[327741.540] Build Operating System: Linux 3.16.0-0.bpo.4-armmp-lpae armv7l 
Debian
[327741.540] Current Operating System: Linux alex 4.4.13-bone11 #88 Tue Nov 
8 17:53:55 CET 2016 armv7l
[327741.540] Kernel command line: console=ttyUSB0,115200n8 
root=/dev/mmcblk0p1 rootfstype=ext4 rootwait coherent_pool=1M quiet splash 
video=HDMI-A-1:1024x600MR@60e fbcon=rotate:1
[327741.540] Build Date: 11 February 2015 01:18:06AM
[327741.540] xorg-server 2:1.16.4-1 (http://www.debian.org/support)
[327741.540] Current version of pixman: 0.32.6
[327741.540] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[327741.540] Markers: (--) probed, (**) from config file, (==) default 
setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[327741.543] (==) Log file: "/var/log/Xorg.0.log", Time: Tue Dec 6 09:41:59 
2016
[327741.545] (==) Using config file: "/etc/X11/xorg.conf"
[327741.546] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[327741.549] (==) ServerLayout "Builtin Default Layout"
[327741.550] (**) |-->Screen "Builtin Default fbdev Screen 0" (0)
[327741.550] (**) | |-->Monitor "Builtin Default Monitor"
[327741.551] (**) | |-->Device "Builtin Default fbdev Device 0"
[327741.551] (**) Option "BlankTime" "0"
[327741.551] (**) Option "StandbyTime" "0"
[327741.551] (**) Option "SuspendTime" "0"
[327741.551] (**) Option "OffTime" "0"
[327741.551] (==) Automatically adding devices
[327741.551] (==) Automatically enabling devices
[327741.551] (==) Automatically adding GPU devices
[327741.551] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not 
exist.
[327741.551] Entry deleted from font path.
[327741.552] (==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/100dpi/:unscaled,
/usr/share/fonts/X11/75dpi/:unscaled,
/usr/share/fonts/X11/Type1,
/usr/share/fonts/X11/100dpi,
/usr/share/fonts/X11/75dpi,
built-ins
[327741.552] (==) ModulePath set to "/usr/lib/xorg/modules"
[327741.552] (II) The server relies on udev to provide the list of input 
devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[327741.552] (II) Loader magic: 0x7f7a0f18
[327741.552] (II) Module ABI versions:
[327741.552] X.Org ANSI C Emulation: 0.4
[327741.552] X.Org Video Driver: 18.0
[327741.552] X.Org XInput driver : 21.0
[327741.552] X.Org Server Extension : 8.0
[327741.553] (II) xfree86: Adding drm device (/dev/dri/card0)
[327741.554] (II) no primary bus or device found
[327741.554] falling back to 
/sys/devices/platform/ocp/4830e000.lcdc/drm/card0
[327741.554] (II) LoadModule: "glx"
[327741.555] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[327741.639] (II) Module glx: vendor="X.Org Foundation"
[327741.639] compiled for 1.16.4, module version = 1.0.0
[327741.639] ABI class: X.Org Server Extension, version 8.0
[327741.639] (==) AIGLX enabled
[327741.639] (II) LoadModule: "fbdev"
[327741.642] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
[327741.644] (II) Module fbdev: vendor="X.Org Foundation"
[327741.644] compiled for 1.15.99.904, module version = 0.4.4
[327741.645] Module class: X.Org Video Driver
[327741.645] ABI class: X.Org Video Driver, version 18.0
[327741.648] (II) FBDEV: driver for framebuffer: fbdev
[327741.648] (--) using VT number 2

[327741.648] (WW) xf86OpenConsole: setpgid failed: Operation not permitted
[327741.649] (WW) xf86OpenConsole: setsid failed: Operation not permitted
[327741.656] (WW) Falling back to old probe method for fbdev
[327741.657] (II) Loading sub module "fbdevhw"
[327741.657] (II) LoadModule: "fbdevhw"
[327741.657] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[327741.658] (II) Module fbdevhw: vendor="X.Org Foundation"
[327741.658] compiled for 1.16.4, module version = 0.0.2
[327741.658] ABI class: X.Org Video Driver, version 18.0
[327741.659] (II) FBDEV(0): using default device
[327741.659] (II) FBDEV(0): Creating default Display subsection in Screen 
section
"Builtin Default fbdev Screen 0" for depth/fbbpp 16/16
[327741.659] (**) FBDEV(0): Depth 16, (--) framebuffer bpp 16
[327741.659] (==) FBDEV(0): RGB weight 565
[327741.659] (==) FBDEV(0): Default visual is TrueColor
[327741.659] (==) FBDEV(0): Using gamma correction (1.0, 1.0, 1.0)
[327741.659] (II) FBDEV(0): hardware: (video memory: 3600kB)
[327741.659] (II) FBDEV(0): checking modes against framebuffer device...
[327741.669] (II) FBDEV(0): checking modes against monitor...
[327741.669] (--) FBDEV(0): Virtual size is 1024x600 (pitch 1024)
[327741.669] (**) FBDEV(0): Built-in mode "current"
[327741.669] (==) FBDEV(0): DPI set to (96, 96)
[327741.669] (II) Loading sub module "fb"
[327741.669] (II) LoadModule: "fb"
[327741.672] (II) Loading /usr/lib/xorg/modules/libfb.so
[327741.673] (II) Module fb: 

[beagleboard] Re: main difference between 4.4.13-bone11 & 4.4.13-bone14

[Micka]

I wanted to say the difference between 4.4.13 bone 11 and 4.4.34 bone 14 ?

https://github.com/RobertCNelson/bb-kernel/commits/am33x-v4.4


Le jeu. 24 nov. 2016 à 10:09, Micka <mickamus...@gmail.com> a écrit :

> Hi,
>
> I'm working on the kernel 4.4.13-bone11 and I would like to know the
> change that you have made since ?
>
> Did you fix some bug ? Did you improve the performance ?
>
>
> I'm asking those questions, because I would like to know if I should
> upgrade the kernel ?
>
>
> Thank you,
>
> Micka,
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAF%2BMRtkoJv%3DR%3D%2B7hE7pW%3D5iL0n6psfcnWZiq2d1Qc16%3DtrG9iA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] main difference between 4.4.13-bone11 & 4.4.13-bone14

[Micka]

Hi,

I'm working on the kernel 4.4.13-bone11 and I would like to know the change
that you have made since ?

Did you fix some bug ? Did you improve the performance ?


I'm asking those questions, because I would like to know if I should
upgrade the kernel ?


Thank you,

Micka,

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAF%2BMRtnHhWs2q44JuweG-LhqRoypDiHGKGP3yasoc8tXOCk53g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Compare kernel versions? (re: Adafruit_BBIO ADC bug)

[Micka]

Robert,

Do you have also something like
https://github.com/RobertCNelson/linux-dev/commits

for the kernel 4.4.13-bone11 ?

Le jeu. 24 nov. 2016 à 06:36, Robert Nelson  a
écrit :

> On Wed, Nov 23, 2016 at 10:57 PM, Drew Fustini  wrote:
> > What's the best way to compare the difference between 4.4.30-ti-r66
> > and 4.4.30-ti-r65?
> >
> > A person on the Adafruit forum reported an ADC issue with
> > Adafruit_BBIO in the latest Debian image:
> >
> > "Adafruit_BBIO ADC latest image"
> > https://forums.adafruit.com/viewtopic.php?f=49=105847
> >
> > There seems to be a bug where ADC.setup() fails upon the first
> > execution but works OK after that.  I've installed different kernels
> > via apt-get and determined that 4.4.30-ti-r65 works OK:
> >
> > 4.4.32-ti-r68: FAIL
> > 4.4.31-ti-r67: FAIL
> > 4.4.30-ti-r66: FAIL
> > 4.4.30-ti-r65: OK
>
> https://github.com/RobertCNelson/ti-linux-kernel-dev/commits/ti-linux-4.4.y
>
> r65 -> r66 there's 4 commits:
>
> 1st commit: (ti tree merge (rt merge))
>
>
> https://github.com/RobertCNelson/ti-linux-kernel-dev/commit/7826d21813db6352830dd42b5a020048d0e24ec5
>
>
> contents of ti merge:
>
>
> https://github.com/RobertCNelson/ti-linux-kernel/compare/d5ab51a974f9dc5eb924e0745160669bb42956b6...4b3fde8208319595e894780a95736917b40d6417
>
>
> 2nd commit: (no-pie, gcc6/stretch fix, gcc6 in stretch now has pie
> enabled by default, that doesn't work with the kernel... should be no
> change with jessie's gcc)
>
>
> https://github.com/RobertCNelson/ti-linux-kernel-dev/commit/16f1c12086c15b5171886c713f18fa34600123d9
>
> 3rd commit:  added support for broadcom: 43430
>
>
> https://github.com/RobertCNelson/ti-linux-kernel-dev/commit/d6fa558f0d929736429da70e5afdc00fe33139fb
>
>
> 4th commit: 4.4.30-ti-r66
>
>
> https://github.com/RobertCNelson/ti-linux-kernel-dev/commit/66eecadbd6d2458dee35aab23e932b9c680cc01e
>
> Compare patches for verification:
>
> wget
> https://rcn-ee.net/deb/jessie-armhf/v4.4.30-ti-r65/patch-4.4.30-ti-r65.diff.gz
> gunzip patch-4.4.30-ti-r65.diff.gz
>
> wget
> https://rcn-ee.net/deb/jessie-armhf/v4.4.30-ti-r66/patch-4.4.30-ti-r66.diff.gz
> gunzip patch-4.4.30-ti-r66.diff.gz
>
> diff -u patch-4.4.30-ti-r65.diff patch-4.4.30-ti-r66.diff
>
> https://paste.debian.net/898309/
>
> might be the rt change???
>
> Regards,
>
> --
> Robert Nelson
> https://rcn-ee.com/
>
> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/CAOCHtYidM5m_YhZ%2Bh%2BbiRiJHfsSSZPPreB4YRmNWNy7jHzvxKw%40mail.gmail.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAF%2BMRt%3Dc0VLt6q6cpEo9yCU7AHzWieUhcB-_gwnsfxM6CKgQ4Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Server X & USB Keyboard

[Micka]

Hi,

I'm trying to use xterm with the server X.

THe mouse work without problem. But the I'm having an issue with the
keyboard.

The keyboard is detecting :

[229689.444] (**) Option "config_info"
"udev:/sys/devices/platform/ocp/4740.usb/47401c00.usb/musb-hdrc.1.auto/usb1/1-1/1-1:1.0/0003:413C:2107.0008/input/input12/event1"
[229689.445] (II) XINPUT: Adding extended input device "Dell Dell USB Entry
Keyboard" (type: KEYBOARD, id 6)
[229689.445] (**) Option "xkb_rules" "evdev"
[229689.445] (**) Option "xkb_model" "pc105"
[229689.445] (**) Option "xkb_layout" "fr"


but it's not working in the xterm windows .

I've tested the keyboard:

xinput test "Dell Dell USB Entry Keyboard"
key press   31
key press   30
key release 30
key release 31
key press   30
key release 30
key press   37
key press   54
key release 54
key release 37

the properties of the keyboard :
xinput --list-props "Dell Dell USB Entry Keyboard"
Device 'Dell Dell USB Entry Keyboard':
  *  Device Enabled (115):   1*
Coordinate Transformation Matrix (116): 1.00, 0.00,
0.00, 0.00, 1.00, 0.00, 0.00, 0.00, 1.00
Device Product ID (236):16700, 8455
Device Node (237):  "/dev/input/event1"

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAF%2BMRtnELV-SYG38baN-OyfNqATnUvVUKefk%2BRw0Laf_Lvst%3DA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] kernel tools/iio

[Micka]

I would like to be that simple !

But it looks like that all the header that I need are in this folder
: /usr/src/linux-headers-4.4.13-bone11/include/linux/iio/

It's working now !

Le mer. 19 oct. 2016 à 12:00, William Hermans <yyrk...@gmail.com> a écrit :

> https://kernelnewbies.org/IIO_tasks
>
> These tasks are for you to get familiar with the IIO subsystem. You do not
> need to claim these via the Outreachy tasks page. *For IIO related
> questions you can join #linux-iio IRC channel (server irc.oftc.net
> <http://irc.oftc.net>). *
> Please email your solutions to amsfield22 at gmail dot com and
> daniel.baluta at gmail dot com. Your email should have the subject Task XX:
> Short task description
>
>
> They would probably be able to help you better there ( the IRC channel )
> Micka.
>
> On Wed, Oct 19, 2016 at 2:53 AM, Micka <mickamus...@gmail.com> wrote:
>
> Hi,
>
> I would like to know how to compile this tools for the beaglebone black ?
>
> I Tried, but I didn't succeed yet !
>
> Any idea ?
>
> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/CAF%2BMRtnC%2B-AhuuOaWjemz8xiio6MJQM-vH3ZfKdU_h2q%2BN%2BJiA%40mail.gmail.com
> <https://groups.google.com/d/msgid/beagleboard/CAF%2BMRtnC%2B-AhuuOaWjemz8xiio6MJQM-vH3ZfKdU_h2q%2BN%2BJiA%40mail.gmail.com?utm_medium=email_source=footer>
> .
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/CALHSORrksJkO2XM52AxUFQ5KDhasMjKEqab0r1bLEN4%2B-BFXbA%40mail.gmail.com
> <https://groups.google.com/d/msgid/beagleboard/CALHSORrksJkO2XM52AxUFQ5KDhasMjKEqab0r1bLEN4%2B-BFXbA%40mail.gmail.com?utm_medium=email_source=footer>
> .
> 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAF%2BMRt%3DWTumEbf8djQFZeVkZ-xzmhcEi%3D_KJBajL%3DDP0Ngqtyg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] kernel tools/iio

[Micka]

Hi,

I would like to know how to compile this tools for the beaglebone black ?

I Tried, but I didn't succeed yet !

Any idea ?

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAF%2BMRtnC%2B-AhuuOaWjemz8xiio6MJQM-vH3ZfKdU_h2q%2BN%2BJiA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] How to change default hwclock on BBB Debian to always be /dev/rtc1?

[Micka]

I also had to change the default rtc... I managed it by recompiling the
kernel. In the menu config you can specify the default rtc

Le dim. 9 oct. 2016 21:39, maxmike  a écrit :

>
> Robert, when using rtc0, did you also use .../i2c-adapter/i2c-0... ?
>
> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/03a7b32a-3e38-44f1-8f1e-9725ed24f05a%40googlegroups.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAF%2BMRtm48VR7m6yQW2mCYhc0ULviuk7JEB9vhVADimWPF1isfw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] sometime the sd is not detected

[Micka]

Hi,

Sometime on the beaglebone black, I've to remove the SD and reinsert it to
be detected. Does someone know what is the cause ?

Micka,

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAF%2BMRtk2uPmS_Lvj0-27p3yqE9whkkYp9cj1n4pk2EzoipvH4Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] BBB TPS65217 RTC

[Micka]

Rtc0 is already used by default...

Le sam. 20 août 2016 06:30, William Hermans  a écrit :

> By the way, you can use /dev/rtc0 just like any other real-time clock.
> Search the internet for "linux how to use real-time clock"
>
> On Fri, Aug 19, 2016 at 9:29 PM, William Hermans 
> wrote:
>
>> $ ls /sys/devices/platform/ocp/44e3e000.rtc/rtc
>> rtc0
>>
>>
>> On Fri, Aug 19, 2016 at 1:25 PM,  wrote:
>>
>>> On Friday, August 19, 2016 at 3:55:34 PM UTC-4, Wulf Man wrote:

 That part is a power management IC not a RTC there is a built in RTC in
 the processor that will not keep
 time when powered down.

>>>
>>>  Oh, my mistake. I was under the impression that part had a RTC, but
>>> lost time when powered down. See here:
>>> https://groups.google.com/forum/#!category-topic/beagleboard/vnu8sC9fgYo
>>>
>>> In any case, if the RTC is in the processor, is there any way to enable
>>> it as I described? I'm interested in using it to keep more accurate time
>>> when power is ON; I have another means of setting the initial time
>>> correctly.
>>>
>>> --
>>> 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.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/beagleboard/3f316b0c-ef92-480a-9ee5-04b37fbbc0dc%40googlegroups.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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/CALHSORo6OZBr-d2HX7%2B1BFK_wmuLNGT%2B3XLxPvb%2Bs7t8NzY37w%40mail.gmail.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAF%2BMRtnY-zp2O%3Ds69UCYvbJbPXopGQDPfhaSvx7q8007h14c%3Dg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] UARTS in kernel 4.4: no /dev/ttO* ?

[Micka]

ttyO* is for the omap driver. If i'm not wrong the kernel 4.4 use the
driver 8250.

You can switch back to the omap driver i' the config of the kernel.

Le ven. 19 août 2016 01:49, William Hermans  a écrit :

> http://bfy.tw/7Hr5
>
> Anyhow, consider this horse beaten to death.
>
> On Thu, Aug 18, 2016 at 4:42 PM, William Hermans 
> wrote:
>
>> william@beaglebone:~$ apt-cache search setserial
>> setserial - controls configuration of serial ports
>> william@beaglebone:~$ sudo apt-get install setserial
>> . . .
>> The following NEW packages will be installed:
>>   setserial
>> 0 upgraded, 1 newly installed, 0 to remove and 13 not upgraded.
>> Need to get 49.9 kB of archives.
>> After this operation, 139 kB of additional disk space will be used.
>>
>> william@beaglebone:~$ setserial -g /dev/ttyS[0-5]
>> /dev/ttyS0, UART: 8250, Port: 0x, IRQ: 158
>> /dev/ttyS1, UART: unknown, Port: 0x, IRQ: 0
>> /dev/ttyS2, UART: 8250, Port: 0x, IRQ: 198
>> /dev/ttyS3, UART: unknown, Port: 0x, IRQ: 0
>> /dev/ttyS4, UART: unknown, Port: 0x, IRQ: 0
>> /dev/ttyS5, UART: unknown, Port: 0x, IRQ: 0
>>
>>
>> On Thu, Aug 18, 2016 at 4:34 PM, William Hermans 
>> wrote:
>>
>>> william@beaglebone:~$ ls /sys/devices/platform/ocp/
>>> 4030.ocmcram  4803.spi4806.mmc
>>> 4831.rng   5350.aes
>>> 40302000.ocmcram_nocache  48038000.mcasp  480c8000.mailbox
>>> 4900.edma  5600.sgx
>>> 44e07000.gpio 4803c000.mcasp  480ca000.spinlock
>>> 4980.tptc  driver_override
>>> 44e09000.serial   48042000.timer  4819c000.i2c
>>> 4990.tptc  modalias
>>> 44e0b000.i2c  48044000.timer  481a.spi
>>> 49a0.tptc  ocp:l4_wkup@44c0
>>> 44e35000.wdt  48046000.timer  481ac000.gpio
>>> 4a10.ethernet  of_node
>>> 44e3e000.rtc  48048000.timer  481ae000.gpio
>>> 4a30.pruss power
>>> 4740.usb  4804a000.timer  481d8000.mmc
>>> 4c00.emif  subsystem
>>> 48024000.serial   4804c000.gpio   4820.interrupt-controller
>>> 5310.sham  uevent
>>> william@beaglebone:~$ ls /sys/devices/platform/ocp/48024000.serial
>>> driver  driver_override  modalias  of_node  power  subsystem  tty  uevent
>>> william@beaglebone:~$ ls /sys/devices/platform/ocp/48024000.serial/tty
>>> ttyS2
>>>
>>>
>>> On Thu, Aug 18, 2016 at 4:32 PM, William Hermans 
>>> wrote:
>>>
 william@beaglebone:~$ dmesg |grep tty
 [0.00] Kernel command line: console=tty0 console=ttyO0,115200n8
 root=/dev/mmcblk0p1 rootfstype=ext4 rootwait ipv6.disable=1
 [0.002187] console [tty0] enabled
 [0.002223] WARNING: Your 'console=ttyO0' has been replaced by
 'ttyS0'
 [1.998154] 44e09000.serial: ttyS0 at MMIO 0x44e09000 (irq = 158,
 base_baud = 300) is a 8250
 [2.884801] console [ttyS0] enabled
 william@beaglebone:~$ clear
 william@beaglebone:~$ ls /sys/devices/
 armv7_cortex_a8  breakpoint  platform  soc0  software  system
 tracepoint  virtual
 william@beaglebone:~$ ls /sys/devices/platform/
 alarmtimercpufreq-dtleds  omap-pcm-audio  pm33xx.0
 power  serial8250  ti-cpufreq.0
 bone_capemgr  fixedregulator@0  ocp   opp_table0  pmu
 reg-dummy  soc uevent
 william@beaglebone:~$ cat /sys/devices/platform/bone_capemgr/slots
  0: PF  -1
  1: PF  -1
  2: PF  -1
  3: PF  -1
 william@beaglebone:~$ ls /lib/firmware/ |grep UART
 BB-UART1-00A0.dtbo
 BB-UART2-00A0.dtbo
 BB-UART2-RTSCTS-00A0.dtbo
 BB-UART3-00A0.dtbo
 BB-UART4-00A0.dtbo
 BB-UART4-RS485-00A0.dtbo
 BB-UART5-00A0.dtbo
 william@beaglebone:~$ sudo sh -c"echo 'BB-UART2' >
 /sys/devices/platform/bone_capemgr/slots"
 [sudo] password for william:
 sh: 0: Illegal option -h
 william@beaglebone:~$ sudo sh -c "echo 'BB-UART2' >
 /sys/devices/platform/bone_capemgr/slots"
 william@beaglebone:~$ cat /sys/devices/platform/bone_capemgr/slots
  0: PF  -1
  1: PF  -1
  2: PF  -1
  3: PF  -1
  4: P-O-L-   0 Override Board Name,00A0,Override Manuf,BB-UART2
 william@beaglebone:~$ dmesg |grep tty
 [0.00] Kernel command line: console=tty0 console=ttyO0,115200n8
 root=/dev/mmcblk0p1 rootfstype=ext4 rootwait ipv6.disable=1
 [0.002187] console [tty0] enabled
 [0.002223] WARNING: Your 'console=ttyO0' has been replaced by
 'ttyS0'
 [1.998154] 44e09000.serial: ttyS0 at MMIO 0x44e09000 (irq = 158,
 base_baud = 300) is a 8250
 [2.884801] console [ttyS0] enabled
 [778201.669492] 48024000.serial: ttyS2 at MMIO 0x48024000 (irq = 198,
 base_baud = 300) is a 8250


 On Thu, Aug 18, 2016 at 4:17 PM, Matt 
 wrote:

> Don't think the ttyS's are 

Re: [beagleboard] Re: UART4 read in pthread not working

[Micka]

My application on the beaglebone black are multithread and for the
reception there is a thread. And I don't have any problem receiving data on
this thread. Don't forget to use mutex and semaphore.

Le mer. 27 juil. 2016 12:11, William Hermans  a écrit :

> If I recall correctly, typically anything that is related to interrupts,
> and blocking file reads( things of this nature - where you're waiting ) are
> not thread safe as these types of calls can be preempted by another thread.
> So, what I'd do to test if my assumption is correct.  Is to write a test
> app without threading. Or perhaps write a callback, but again, callbacks
> are definitely not thread safe.
>
> I'm not seeing all the posts in this discussion for some reason. But is
> there a specific reason why you need threads ? Because if you need this
> sort of process segregation, it may be best to run entirely different
> processes( multiple executables ), and then use some form of IPC mechanism
> such as shared memory. Which POSIX shared memory really is fairly simple
> once you become familiar with it. I had to do this with an application I
> wrote several months back ,myself. Since a library I was using used
> callbacks extensively and was not playing nicely on the stack ( preempting
> my own code routinely ).
>
> On Wed, Jul 27, 2016 at 2:49 AM, Regina Choi 
> wrote:
>
>>
>> I'm not aware of library functions that are not thread safe, can you give
>> some example library function that is not thread safe?  So if the library
>> function is not thread safe, what would be the effect if we accidentally
>> use it in our program?
>>
>> Does that means we cannot use the library function completely in pthread
>> if it is not thread safe and resort to polling mechanism?
>>
>>
>>
>> On Wednesday, July 27, 2016 at 1:00:10 PM UTC+8, William Hermans wrote:
>>>
>>> Are you sure everything you're using code wise is thread safe ? There
>>> are a lot of library functions that are not thread safe.
>>>
>>> On Mon, Jul 25, 2016 at 8:31 PM, Regina Choi 
>>> wrote:
>>>
 Thanks for reply.

 I'm not sure why, but I don't get timeout error messages from the read
 thread (though I have set it to 1 sec) !? It just freeze there waiting for
 UART input, even though there are UART input coming in.

 Yes, I got the Byte sent message printf from TX thread. Please see the
 attachement.









 On Tue, Jul 26, 2016 at 2:30 AM, Wally Bkg  wrote:

> I'm stumped.  Are you now getting timeout error messages from the read
> thread?
>
> Are you getting the Byte sent: message printf from the TX thread?
>
>
> On Sunday, July 24, 2016 at 10:11:57 PM UTC-5, Regina Choi wrote:
>>
>>
>> Apology for late reply.
>>
>> I've tried with options.c_cc[VMIN]  = 0; it's still the same issue.
>>
>> From the datasheet of AM335x, uart rx/tx buffers are 64 bytes.
>>
>> I've also tried putting tx command in tx thread that activated later
>> than rx thread. Nothing changed as well.
>>
>> void* uartTxWait(void *param){
>>
>> int count;
>> usleep(100);
>> unsigned char cmd[] = {0x10, 0x00, 0x32};//"Tx From
>> Beaglebone ";
>>
>> if ((count = write(file, (char*)cmd, 3))<0){
>>   perror("Failed to write to the output\n");
>>   //tcsetattr(file, TCSAFLUSH, ); //before
>> exit, undo raw setting
>>   //return -1;
>>  }else{
>>  printf("Byte sent: %d \n", count);
>>  }
>>
>>
>> pthread_exit(0);
>> }
>>
>>
>>
>>
>> On Friday, July 22, 2016 at 10:50:52 PM UTC+8, Wally Bkg wrote:
>>>
>>> I noticed you have options.c_cc[VMIN]  = 2;  If for some reason only
>>> one character comes in, it'll block forever.  Try using 
>>> options.c_cc[VMIN]
>>>  = 0; so that each char can timeout if its not received.
>>>
>>> How big are the Beaglebone uart buffers?
>>>
>>> You may still have a race between your write of the data and
>>> starting your RX thread.  Try putting the write into your TX thread and
>>> launch it after you've launched the RX thread.
>>>
>>>
>>>
>>> On Thursday, July 21, 2016 at 10:10:11 PM UTC-5, Regina Choi wrote:


 Hi Wally,

 I have tried adding fflush(stdout and fflush(stderr) in the while
 loop, however, in the UartRxWait thread, the read( ) function is in 
 block
 waiting for incoming data. Which doesn't output anything. In the case,
 after start and shut down minicom, the UartRxWait thread running as 
 usual,
 there is no output from the fflush(stdout) and fflush(stderr) either.

 yes, at the moment I have to kill 

Re: [beagleboard] Getting Bootchart setup on Debian 8.3

[Micka]

allow-hotplug lo
allow-hotplug eth0



Le mer. 29 juin 2016 à 17:52, Micka <mickamus...@gmail.com> a écrit :

> Did you put allow-hotplug everywhere ?
>
> Le mer. 29 juin 2016 à 17:51, William Hermans <yyrk...@gmail.com> a
> écrit :
>
>> I found the answer here :
>>>
>>>
>>> http://unix.stackexchange.com/questions/204753/systemd-waiting-too-long-for-network-at-debian-8-0-jessies-boot
>>>
>>> The solution is fairly easy, just replace auto to allow-hotplug.
>>>
>>> now it takes:  networking.service (4.113s)
>>>
>>
>> I tried that about a week ago. It did not work for me. But I only tried
>> with systemd not sysv.
>>
>> On Wed, Jun 29, 2016 at 8:49 AM, Micka <mickamus...@gmail.com> wrote:
>>
>>> I found the answer here :
>>>
>>>
>>> http://unix.stackexchange.com/questions/204753/systemd-waiting-too-long-for-network-at-debian-8-0-jessies-boot
>>>
>>> The solution is fairly easy, just replace auto to allow-hotplug.
>>>
>>> now it takes:  networking.service (4.113s)
>>>
>>> Le mer. 29 juin 2016 à 17:38, William Hermans <yyrk...@gmail.com> a
>>> écrit :
>>>
>>>> Robert,
>>>>
>>>> Any idea where I should start looking to resolve this problem ? I would
>>>> not mind hunting the problem down myself, and then giving the group the
>>>> information.
>>>>
>>>> On Wed, Jun 29, 2016 at 8:23 AM, Micka <mickamus...@gmail.com> wrote:
>>>>
>>>>> The ethernet is connected.
>>>>>
>>>>> I've put some log in the file /etc/init.d/networking . And this file
>>>>> work very quickly. Weird ... Looks like that systemd takes time to detect
>>>>> that the service finished.
>>>>>
>>>>>
>>>>> [   11.213262] net eth0: initializing cpsw version 1.12 (0)
>>>>> [   11.215589] net eth0: phy found : id is : 0x7c0f1
>>>>> [   11.231729] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
>>>>>
>>>>> [  117.675769] cpsw 4a10.ethernet eth0: Link is Up - 100Mbps/Full
>>>>> - flow control rx/tx
>>>>>
>>>>> but for some reason, it takes too much time !
>>>>>
>>>>> Le mer. 29 juin 2016 à 17:00, Robert Nelson <robertcnel...@gmail.com>
>>>>> a écrit :
>>>>>
>>>>>> On Wed, Jun 29, 2016 at 5:44 AM, Micka <mickamus...@gmail.com> wrote:
>>>>>> > Robert Nelson,
>>>>>> >
>>>>>> > About the service  /etc/init.d/networking
>>>>>> >
>>>>>> > did you modify it for the beaglebone black ?
>>>>>> >
>>>>>> > Because we know that the BBB have problem with ethernet. But where
>>>>>> did you
>>>>>> > try to correct the problem ? In the networking service ? Did you
>>>>>> put a sleep
>>>>>> > ?
>>>>>> >
>>>>>> > Where can I reduce the time of the execution of this service ?
>>>>>>
>>>>>> I didn't make any changes to that script...
>>>>>>
>>>>>> it's slow, specially if your eth0 isn't connected..
>>>>>>
>>>>>> thus we use connman ;)
>>>>>>
>>>>>> Regards,
>>>>>>
>>>>>> --
>>>>>> Robert Nelson
>>>>>> https://rcn-ee.com/
>>>>>>
>>>>>> --
>>>>>> 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.
>>>>>> To view this discussion on the web visit
>>>>>> https://groups.google.com/d/msgid/beagleboard/CAOCHtYhAE%2B%2BCV8ThBkr%2BZMpqxMCEsoH%3DUuxqtN-MKnsRsPFSUA%40mail.gmail.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 

Re: [beagleboard] Getting Bootchart setup on Debian 8.3

[Micka]

I found the answer here :

http://unix.stackexchange.com/questions/204753/systemd-waiting-too-long-for-network-at-debian-8-0-jessies-boot

The solution is fairly easy, just replace auto to allow-hotplug.

now it takes:  networking.service (4.113s)

Le mer. 29 juin 2016 à 17:38, William Hermans <yyrk...@gmail.com> a écrit :

> Robert,
>
> Any idea where I should start looking to resolve this problem ? I would
> not mind hunting the problem down myself, and then giving the group the
> information.
>
> On Wed, Jun 29, 2016 at 8:23 AM, Micka <mickamus...@gmail.com> wrote:
>
>> The ethernet is connected.
>>
>> I've put some log in the file /etc/init.d/networking . And this file work
>> very quickly. Weird ... Looks like that systemd takes time to detect that
>> the service finished.
>>
>>
>> [   11.213262] net eth0: initializing cpsw version 1.12 (0)
>> [   11.215589] net eth0: phy found : id is : 0x7c0f1
>> [   11.231729] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
>>
>> [  117.675769] cpsw 4a10.ethernet eth0: Link is Up - 100Mbps/Full -
>> flow control rx/tx
>>
>> but for some reason, it takes too much time !
>>
>> Le mer. 29 juin 2016 à 17:00, Robert Nelson <robertcnel...@gmail.com> a
>> écrit :
>>
>>> On Wed, Jun 29, 2016 at 5:44 AM, Micka <mickamus...@gmail.com> wrote:
>>> > Robert Nelson,
>>> >
>>> > About the service  /etc/init.d/networking
>>> >
>>> > did you modify it for the beaglebone black ?
>>> >
>>> > Because we know that the BBB have problem with ethernet. But where did
>>> you
>>> > try to correct the problem ? In the networking service ? Did you put a
>>> sleep
>>> > ?
>>> >
>>> > Where can I reduce the time of the execution of this service ?
>>>
>>> I didn't make any changes to that script...
>>>
>>> it's slow, specially if your eth0 isn't connected..
>>>
>>> thus we use connman ;)
>>>
>>> Regards,
>>>
>>> --
>>> Robert Nelson
>>> https://rcn-ee.com/
>>>
>>> --
>>> 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.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/beagleboard/CAOCHtYhAE%2B%2BCV8ThBkr%2BZMpqxMCEsoH%3DUuxqtN-MKnsRsPFSUA%40mail.gmail.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.
>>
> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/beagleboard/CAF%2BMRt%3Dx%3Ddmkz%2Bf7odpR16d8b5TNueJyjJ9ipXGUEOcEAMvw-w%40mail.gmail.com
>> <https://groups.google.com/d/msgid/beagleboard/CAF%2BMRt%3Dx%3Ddmkz%2Bf7odpR16d8b5TNueJyjJ9ipXGUEOcEAMvw-w%40mail.gmail.com?utm_medium=email_source=footer>
>> .
>
>
>> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/CALHSORryjtiRH4hj9yzMOrbPzMwy1wW%2ByYJqTNkFiJPwOEfuzQ%40mail.gmail.com
> <https://groups.google.com/d/msgid/beagleboard/CALHSORryjtiRH4hj9yzMOrbPzMwy1wW%2ByYJqTNkFiJPwOEfuzQ%40mail.gmail.com?utm_medium=email_source=footer>
> .
> 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAF%2BMRtkO45aHQDPp_db%2BOWPScnMxxE4reXo3V58q81gpyV46AQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Getting Bootchart setup on Debian 8.3

[Micka]

Did you put allow-hotplug everywhere ?

Le mer. 29 juin 2016 à 17:51, William Hermans <yyrk...@gmail.com> a écrit :

> I found the answer here :
>>
>>
>> http://unix.stackexchange.com/questions/204753/systemd-waiting-too-long-for-network-at-debian-8-0-jessies-boot
>>
>> The solution is fairly easy, just replace auto to allow-hotplug.
>>
>> now it takes:  networking.service (4.113s)
>>
>
> I tried that about a week ago. It did not work for me. But I only tried
> with systemd not sysv.
>
> On Wed, Jun 29, 2016 at 8:49 AM, Micka <mickamus...@gmail.com> wrote:
>
>> I found the answer here :
>>
>>
>> http://unix.stackexchange.com/questions/204753/systemd-waiting-too-long-for-network-at-debian-8-0-jessies-boot
>>
>> The solution is fairly easy, just replace auto to allow-hotplug.
>>
>> now it takes:  networking.service (4.113s)
>>
>> Le mer. 29 juin 2016 à 17:38, William Hermans <yyrk...@gmail.com> a
>> écrit :
>>
>>> Robert,
>>>
>>> Any idea where I should start looking to resolve this problem ? I would
>>> not mind hunting the problem down myself, and then giving the group the
>>> information.
>>>
>>> On Wed, Jun 29, 2016 at 8:23 AM, Micka <mickamus...@gmail.com> wrote:
>>>
>>>> The ethernet is connected.
>>>>
>>>> I've put some log in the file /etc/init.d/networking . And this file
>>>> work very quickly. Weird ... Looks like that systemd takes time to detect
>>>> that the service finished.
>>>>
>>>>
>>>> [   11.213262] net eth0: initializing cpsw version 1.12 (0)
>>>> [   11.215589] net eth0: phy found : id is : 0x7c0f1
>>>> [   11.231729] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
>>>>
>>>> [  117.675769] cpsw 4a10.ethernet eth0: Link is Up - 100Mbps/Full -
>>>> flow control rx/tx
>>>>
>>>> but for some reason, it takes too much time !
>>>>
>>>> Le mer. 29 juin 2016 à 17:00, Robert Nelson <robertcnel...@gmail.com>
>>>> a écrit :
>>>>
>>>>> On Wed, Jun 29, 2016 at 5:44 AM, Micka <mickamus...@gmail.com> wrote:
>>>>> > Robert Nelson,
>>>>> >
>>>>> > About the service  /etc/init.d/networking
>>>>> >
>>>>> > did you modify it for the beaglebone black ?
>>>>> >
>>>>> > Because we know that the BBB have problem with ethernet. But where
>>>>> did you
>>>>> > try to correct the problem ? In the networking service ? Did you put
>>>>> a sleep
>>>>> > ?
>>>>> >
>>>>> > Where can I reduce the time of the execution of this service ?
>>>>>
>>>>> I didn't make any changes to that script...
>>>>>
>>>>> it's slow, specially if your eth0 isn't connected..
>>>>>
>>>>> thus we use connman ;)
>>>>>
>>>>> Regards,
>>>>>
>>>>> --
>>>>> Robert Nelson
>>>>> https://rcn-ee.com/
>>>>>
>>>>> --
>>>>> 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.
>>>>> To view this discussion on the web visit
>>>>> https://groups.google.com/d/msgid/beagleboard/CAOCHtYhAE%2B%2BCV8ThBkr%2BZMpqxMCEsoH%3DUuxqtN-MKnsRsPFSUA%40mail.gmail.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.
>>>>
>>> To view this discussion on the web visit
>>>> https://groups.google.com/d/msgid/beagleboard/CAF%2BMRt%3Dx%3Ddmkz%2Bf7odpR16d8b5TNueJyjJ9ipXGUEOcEAMvw-w%40mail.gmail.com
>>>> <https://groups.google.com/d/msgid/beagleboard/CAF%2BMR

Re: [beagleboard] Getting Bootchart setup on Debian 8.3

[Micka]

The ethernet is connected.

I've put some log in the file /etc/init.d/networking . And this file work
very quickly. Weird ... Looks like that systemd takes time to detect that
the service finished.


[   11.213262] net eth0: initializing cpsw version 1.12 (0)
[   11.215589] net eth0: phy found : id is : 0x7c0f1
[   11.231729] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready

[  117.675769] cpsw 4a10.ethernet eth0: Link is Up - 100Mbps/Full -
flow control rx/tx

but for some reason, it takes too much time !

Le mer. 29 juin 2016 à 17:00, Robert Nelson <robertcnel...@gmail.com> a
écrit :

> On Wed, Jun 29, 2016 at 5:44 AM, Micka <mickamus...@gmail.com> wrote:
> > Robert Nelson,
> >
> > About the service  /etc/init.d/networking
> >
> > did you modify it for the beaglebone black ?
> >
> > Because we know that the BBB have problem with ethernet. But where did
> you
> > try to correct the problem ? In the networking service ? Did you put a
> sleep
> > ?
> >
> > Where can I reduce the time of the execution of this service ?
>
> I didn't make any changes to that script...
>
> it's slow, specially if your eth0 isn't connected..
>
> thus we use connman ;)
>
> Regards,
>
> --
> Robert Nelson
> https://rcn-ee.com/
>
> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/CAOCHtYhAE%2B%2BCV8ThBkr%2BZMpqxMCEsoH%3DUuxqtN-MKnsRsPFSUA%40mail.gmail.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAF%2BMRt%3Dx%3Ddmkz%2Bf7odpR16d8b5TNueJyjJ9ipXGUEOcEAMvw-w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Getting Bootchart setup on Debian 8.3

[Micka]

Robert Nelson,

About the service  /etc/init.d/networking

did you modify it for the beaglebone black ?

Because we know that the BBB have problem with ethernet. But where did you
try to correct the problem ? In the networking service ? Did you put a
sleep ?

Where can I reduce the time of the execution of this service ?


micka,

Le jeu. 19 mai 2016 à 19:48, William Hermans <yyrk...@gmail.com> a écrit :

> *My apologies to All: I'm an interloper. Actually I'm using Debian Wheezy
>> and my problem is not related to bootchart. I hitched onto this thread,
>> suggested by Drew Fustini in the Adafruit forum. *
>>
>> *I have an Adafruit DS3231 Real Time Clock module attached to my BBB.
>> Debian is delaying for one minute to read the DS3231's clock time and
>> I would like to eliminate that one minute delay. I suspect that Debian is
>> trying to go through the Internet to read the time from ntpdate or whatever
>> and gives up after a minute, finally reading the clock data from
>> the DS3231 module.*
>>
>> *FWIW, I checked the status of the systemd-timesyncd service and found
>> that it's "inactive (dead)."*
>>
>> *Thanks,*
>> *John*
>>
>
> John,
>
> Maybe helpful for you, maybe not. But you could look into the wheezy
> package fake-hwclock, which keeps time as close as possible to accurate
> time between reboots. Which would then make that one minute delay at least
> bearable.
>
> The problem I'm thinking you're running into here is that it takes a while
> for the OS to come up. So until the system is read to take care of reading
> the real time clock . . .
>
> Perhaps you could find, or write a kernel module that loads time from the
> rtc at early boot ? But non of this is anything I'v personally had hands on
> with, except fake-hwclock.
>
> On Thu, May 19, 2016 at 10:33 AM, John Baker <bakerengineerin...@gmail.com
> > wrote:
>
>> My apologies to All: I'm an interloper. Actually I'm using Debian Wheezy
>> and my problem is not related to bootchart. I hitched onto this thread,
>> suggested by Drew Fustini in the Adafruit forum.
>>
>> I have an Adafruit DS3231 Real Time Clock module attached to my BBB.
>> Debian is delaying for one minute to read the DS3231's clock time and
>> I would like to eliminate that one minute delay. I suspect that Debian is
>> trying to go through the Internet to read the time from ntpdate or whatever
>> and gives up after a minute, finally reading the clock data from
>> the DS3231 module.
>>
>> FWIW, I checked the status of the systemd-timesyncd service and found
>> that it's "inactive (dead)."
>>
>> Thanks,
>> John
>>
>> On Thursday, May 19, 2016 at 5:08:51 AM UTC-7, Alex wrote:
>>>
>>> As Robert told u, you need to disable the service
>>> systemd-timesyncd:
>>>
>>> systemctl disable systemd-timesyncd
>>>
>>> Le jeu. 19 mai 2016 13:27, John Baker <john...@ieee.org> a écrit :
>>>
>>>> Thanks Micka.
>>>>
>>>> I just now tried that and putty.exe said that ntp isn't installed, so
>>>> not removed, but I'll bet it's gotta be something like that. Maybe
>>>> something for the Internet connection.
>>>>
>>>> John
>>>>
>>>> On 5/18/2016 8:33 PM, Micka wrote:
>>>>
>>>> sudo apt-get remove ntp
>>>>
>>>> Le mer. 18 mai 2016 23:53, John Baker <bakerengi...@gmail.com> a
>>>> écrit :
>>>>
>>>>> Robert:
>>>>> What script is trying to read the clock data from ntp? I have an
>>>>> Adafruit DS3231 for the Real Time Clock and the BBB is taking a minute
>>>>> before it gets the clock from the DS3231 so I suspect some script is 
>>>>> trying
>>>>> to read the ntp clock data and holding up the read of my DS3231 clock. Es
>>>>> posible?
>>>>> John
>>>>>
>>>>> --
>>>>> 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.
>>>>> To view this discussion on the web visit
>>>>> <https://groups.google.com/d/msgid/beagleboard/66884716-e25b-412e-98f1-97870f8f7127%40googlegroups.com>
>>>>> https://group

Re: [beagleboard] HDMI and interrupt GPIO1_25

[Micka]

Well from those lines:

http://lxr.free-electrons.com/source/drivers/gpu/drm/i2c/tda998x_drv.c?v=4.1#L1304

I thought that it was to help to read the edid data or about the
plug/unplug:

566 
<http://lxr.free-electrons.com/source/drivers/gpu/drm/i2c/tda998x_drv.c?v=4.1#L566>
* * only 2 interrupts may occur: screen plug/unplug and EDID read*

http://lxr.free-electrons.com/source/drivers/gpu/drm/i2c/tda998x_drv.c?v=4.1#L565






Le jeu. 23 juin 2016 à 21:49, Gerald Coley <ger...@beagleboard.org> a
écrit :

> This interrupt is to pass IR remote information to the processor over the
> HDMI from the TV. As the BBB is lacking a tuner, I am not sure how much
> value this feature has.
>
> Gerald
>
> On Thu, Jun 23, 2016 at 2:41 PM, Jason Kridner <jkrid...@beagleboard.org>
> wrote:
>
>> On Thu, Jun 23, 2016 at 3:24 AM Micka <mickamus...@gmail.com> wrote:
>>
>>> Hi,
>>>
>>> When Gerald Coley design the BBB, he planed to use the GPIO1_25 as an
>>> interrupt signal from the tda19988..
>>>
>>> I wanted to know why the interrupt GPIO1_25 is not used for interrupt.
>>>
>>
>> It looks like the driver supports an interrupt:
>>
>> http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/video/fbdev/da8xx-fb.c#n833
>>
>>
>> http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/gpu/drm/tilcdc/tilcdc_drv.c#n357
>>
>>
>> Are you concerned this interrupt is necessary for some function missing
>> in your system?
>>
>> Is this something we can enable in the device tree?
>>
>>
>> https://github.com/beagleboard/linux/blob/4.4/arch/arm/boot/dts/am335x-boneblack.dts
>>
>>
>> We probably need to ask the original developer why the IRQ wasn't
>> connected to the driver.
>>
>>
>>>
>>> Micka,
>>>
>>> --
>>> 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.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/beagleboard/CAF%2BMRtnFvUhqGqCNJMPVM%2Bb-f0OQr%2BSiZY8DUPCdHbgVWYkxMw%40mail.gmail.com
>>> <https://groups.google.com/d/msgid/beagleboard/CAF%2BMRtnFvUhqGqCNJMPVM%2Bb-f0OQr%2BSiZY8DUPCdHbgVWYkxMw%40mail.gmail.com?utm_medium=email_source=footer>
>>> .
>>> 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.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/beagleboard/CA%2BT6QPmb4Np86P-nHgvkfZirbZUhn0DyF413mqxyMdAb372yCQ%40mail.gmail.com
>> <https://groups.google.com/d/msgid/beagleboard/CA%2BT6QPmb4Np86P-nHgvkfZirbZUhn0DyF413mqxyMdAb372yCQ%40mail.gmail.com?utm_medium=email_source=footer>
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> Gerald
>
> ger...@beagleboard.org
> http://beagleboard.org/
> gcol...@emprodesign.com
>
> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/CAHK_S%2Bc4LGtZVo5gVoDOXHf1NM6D074eQBS4QPCkU67yvMUyrA%40mail.gmail.com
> <https://groups.google.com/d/msgid/beagleboard/CAHK_S%2Bc4LGtZVo5gVoDOXHf1NM6D074eQBS4QPCkU67yvMUyrA%40mail.gmail.com?utm_medium=email_source=footer>
> .
> 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAF%2BMRt%3D%2B0gd7EwHG585D1kdw9TWE8HfL7OgYF3dSRRhpG8dnFg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] HDMI and interrupt GPIO1_25

[Micka]

Hi,

Thx for the answer, no I don't need it. It's just by curiosity.



Le jeu. 23 juin 2016 à 21:41, Jason Kridner <jkrid...@beagleboard.org> a
écrit :

> On Thu, Jun 23, 2016 at 3:24 AM Micka <mickamus...@gmail.com> wrote:
>
>> Hi,
>>
>> When Gerald Coley design the BBB, he planed to use the GPIO1_25 as an
>> interrupt signal from the tda19988..
>>
>> I wanted to know why the interrupt GPIO1_25 is not used for interrupt.
>>
>
> It looks like the driver supports an interrupt:
>
> http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/video/fbdev/da8xx-fb.c#n833
>
>
> http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/gpu/drm/tilcdc/tilcdc_drv.c#n357
>
>
> Are you concerned this interrupt is necessary for some function missing in
> your system?
>
> Is this something we can enable in the device tree?
>
>
> https://github.com/beagleboard/linux/blob/4.4/arch/arm/boot/dts/am335x-boneblack.dts
>
>
> We probably need to ask the original developer why the IRQ wasn't
> connected to the driver.
>
>
>>
>> Micka,
>>
>> --
>> 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.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/beagleboard/CAF%2BMRtnFvUhqGqCNJMPVM%2Bb-f0OQr%2BSiZY8DUPCdHbgVWYkxMw%40mail.gmail.com
>> <https://groups.google.com/d/msgid/beagleboard/CAF%2BMRtnFvUhqGqCNJMPVM%2Bb-f0OQr%2BSiZY8DUPCdHbgVWYkxMw%40mail.gmail.com?utm_medium=email_source=footer>
>> .
>> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/CA%2BT6QPmb4Np86P-nHgvkfZirbZUhn0DyF413mqxyMdAb372yCQ%40mail.gmail.com
> <https://groups.google.com/d/msgid/beagleboard/CA%2BT6QPmb4Np86P-nHgvkfZirbZUhn0DyF413mqxyMdAb372yCQ%40mail.gmail.com?utm_medium=email_source=footer>
> .
> 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAF%2BMRtnyn5cUQuq0SO0HrqzcS7k2sBzy97QYgaNSAQ9kfjWs1w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] HDMI and interrupt GPIO1_25

[Micka]

Hi,

When Gerald Coley design the BBB, he planed to use the GPIO1_25 as an
interrupt signal from the tda19988..

I wanted to know why the interrupt GPIO1_25 is not used for interrupt.

Micka,

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAF%2BMRtnFvUhqGqCNJMPVM%2Bb-f0OQr%2BSiZY8DUPCdHbgVWYkxMw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Setting static IP

[Micka]

because connman is installed.

try this one : sudo apt-get remove connman --purge

that will remove connman, but you need to reboot after your beagle. or you
can keep it and configure your ip with connman.

Le mar. 21 juin 2016 à 12:27, lucas  a écrit :

> I am trying to set my Beaglebone Black to a static IP address.
>
> I edited /etc/network/interfaces as follows (leaving out some comments):
>
> # The loopback network interface
> auto lo
> iface lo inet loopback
>
> # The primary network interface
> auto eth0
> iface eth0 inet static
> address 192.168.169.211
> netmask 255.255.255.0
> gateway 192.168.169.1
>
> # Ethernet/RNDIS gadget (g_ether)
> # Used by: /opt/scripts/boot/autoconfigure_usb0.sh
> iface usb0 inet static
> address 192.168.7.2
> netmask 255.255.255.252
> network 192.168.7.0
> gateway 192.168.7.1
>
> Unfortunately it seem like the file is ignored and some other ip address
> is obtained, ostensibly by dhcp.
>
> I am running Debian 8.3 (Linux beaglebone 4.1.15-ti-rt-r43). Any idea how
> to fix this?
>
>
> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/5f7c1c75-4bc3-4d28-8264-2a66d55d262e%40googlegroups.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAF%2BMRtn1qrkx7RTAeinAsaX1ay7WFZ02xOPXMgvWZ8Vsx1Y_%3Dw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Capture analog input at near maximum sample rate?

[Micka]

the best woud be the PRU because you can store the data in the share
memory. That is the fastest way.

you can stop the acquisition whenever you want or let it go back at the
beginning of your memory and go on.


Le lun. 20 juin 2016 à 21:29,  a écrit :

> I'm looking to write a simple app for BBB.  When started from the command
> line, it would set up the ADC in continuous mode and read ~1 M samples from
> e.g. AN0 into memory.  After the capture is complete, it would write the
> data to a file and exit.
>
> Ideally, it would run at the hardware limit of 1.6 MSPS (15 cycles of 24
> MHz adc_clk per sample).  If that's not practical, 800 KSPS or better would
> be acceptable.
>
> What is an easy way to do this?  Most Beaglebone ADC examples sample at
> kilohertz rates or slower.
>
> This guide:
> http://processors.wiki.ti.com/index.php/Linux_Core_ADC_User%27s_Guide
> speaks of 200 KSPS.  What is the limitation here?
>
> I've seen various suggestions to use the PRU, but don't understand why.  I
> would think that since DMA would be required anyway, there should be no
> requirement to otherwise access the hardware with tight timing.  If PRU is
> indeed necessary, is there a suitable example or tutorial?  (None of the
> libpruio built-in examples deal with rapid sampling or large amounts of
> data.)
>
> Any other ideas for a simple way to capture data fast will be gratefully
> appreciated.
>
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/c5cae6bf-c8e0-45c4-ab5b-6bc236766d09%40googlegroups.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAF%2BMRtnELw1UDxA79pnBs-sZp-cG%3Dq8GRWoGJpuzFCCdjwodKQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: SPL bad magic at boot in the MLO file

[Micka]

OK that not it I think.

I've tried to understand when the header is written in the MLO. And it
looks like that it is the mkimage job . ( not sure ) .

the mkimage is call to create the MLO file. I discovered that the
function omapimage_set_header is called to create the header file.

So it's not at all this structure

typedef struct image_header {
__be32  ih_magic;   /* Image Header Magic Number*/

} image_header_t;

but it's using this header : struct gp_header.


And that where I'm confused, because in the file : common/spl/spl_mmc.c
it's looking at this header :

struct image_header *header;

header = (struct image_header *)(CONFIG_SYS_TEXT_BASE -
 sizeof(struct image_header));


What is wrong Robert Nelson, Where am I wrong ?


Le ven. 17 juin 2016 à 18:50, Micka <mickamus...@gmail.com> a écrit :

> ok
>
> When I compile the uboot, are we using this one ?
>
> arch/arm/cpu/armv7/start.S
>
> Can we add something like that :
>
> .long   0x27051956  /* U-Boot Magic Number
>  */
>
>
>
> Le ven. 17 juin 2016 à 18:47, Robert Nelson <robertcnel...@gmail.com> a
> écrit :
>
>> On Fri, Jun 17, 2016 at 11:31 AM, Micka <mickamus...@gmail.com> wrote:
>> > Lol, ok
>> >
>> > But what went wrong ?  It's checking a magic number to prevent something
>> > broken.
>> >
>> > Can I write back the correct magic number ?
>> >
>> > I found that in this file : arch/powerpc/cpu/mpc8xx/start.S
>> >
>> > it write somewhere the magic number : 0x27051956
>> >
>> > But I don't see where the magic number is written for the beaglebone
>> black
>> > uboot.
>>
>> it's for something generic, but we don't use it.. I'm tempted to just
>> patch it like my joke, as people do ask..
>>
>> Regards,
>>
>> --
>> Robert Nelson
>> https://rcn-ee.com/
>>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAF%2BMRtk0acqiw%2Bmx9SO1O_n-ofS3D%3DJr7VOw9U7HbuVif3ErBQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: SPL bad magic at boot in the MLO file

[Micka]

ok

When I compile the uboot, are we using this one ?

arch/arm/cpu/armv7/start.S

Can we add something like that :

.long   0x27051956  /* U-Boot Magic Number
 */



Le ven. 17 juin 2016 à 18:47, Robert Nelson <robertcnel...@gmail.com> a
écrit :

> On Fri, Jun 17, 2016 at 11:31 AM, Micka <mickamus...@gmail.com> wrote:
> > Lol, ok
> >
> > But what went wrong ?  It's checking a magic number to prevent something
> > broken.
> >
> > Can I write back the correct magic number ?
> >
> > I found that in this file : arch/powerpc/cpu/mpc8xx/start.S
> >
> > it write somewhere the magic number : 0x27051956
> >
> > But I don't see where the magic number is written for the beaglebone
> black
> > uboot.
>
> it's for something generic, but we don't use it.. I'm tempted to just
> patch it like my joke, as people do ask..
>
> Regards,
>
> --
> Robert Nelson
> https://rcn-ee.com/
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAF%2BMRt%3DjuSOybWctoChtwy5PYXq_ckkOX-yD_6fjyEfpuqTO%2Bg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: SPL bad magic at boot in the MLO file

[Micka]

Lol, ok

But what went wrong ?  It's checking a magic number to prevent something
broken.

Can I write back the correct magic number ?

I found that in this file : arch/powerpc/cpu/mpc8xx/start.S

it write somewhere the magic number : 0x27051956

But I don't see where the magic number is written for the beaglebone black
uboot.


any idea ?



Le ven. 17 juin 2016 à 18:23, Robert Nelson <robertcnel...@gmail.com> a
écrit :

> On Fri, Jun 17, 2016 at 11:18 AM, Micka <mickamus...@gmail.com> wrote:
> > I've compiled the uboot again and again, and it doesn't change anything
> when
> > I replace the old MLO file :
> >
> > dd if=./MLO of=${DISK} count=1 seek=1 bs=128k
> >
> >
> >
> > Le ven. 17 juin 2016 à 18:16, Micka <mickamus...@gmail.com> a écrit :
> >>
> >> Hi, when the board boot, I've the message that tell me :
> >>
> >> bad magic. and after a deep research, it come from the SPL :
> >>
> >> common/spl/spl_mmc.c
> >>
>
>
>  //if (image_get_magic(header) != IH_MAGIC) {
>   //   puts("bad magic\n");
>   // }
>
> fixed!
>
> Regards,
>
> --
> Robert Nelson
> https://rcn-ee.com/
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAF%2BMRtktwu9Yo9WchO%2BVpQ6Y1Vej2qLB397gBBhPnnFRDd-wmg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: SPL bad magic at boot in the MLO file

[Micka]

I've compiled the uboot again and again, and it doesn't change anything
when I replace the old MLO file :

dd if=./MLO of=${DISK} count=1 seek=1 bs=128k



Le ven. 17 juin 2016 à 18:16, Micka <mickamus...@gmail.com> a écrit :

> Hi, when the board boot, I've the message that tell me :
>
> bad magic. and after a deep research, it come from the SPL :
>
> common/spl/spl_mmc.c
>
> if (image_get_magic(header) != IH_MAGIC) {
> puts("bad magic\n");
>
>
> how can i fix that ?
>
> Micka,
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAF%2BMRt%3DG-49ZzBwDKzu6gXJO4Mevufbz17tLKWoc3x2VNkSqsQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] SPL bad magic at boot in the MLO file

[Micka]

Hi, when the board boot, I've the message that tell me :

bad magic. and after a deep research, it come from the SPL :

common/spl/spl_mmc.c

if (image_get_magic(header) != IH_MAGIC) {
puts("bad magic\n");


how can i fix that ?

Micka,

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAF%2BMRtk1Nq_K_B1UcHHrJqQZSxYcVSMBox_yfPYnpbPu1E67ew%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Device-Tree Clarifications (Beaglebone Black)

[Micka]

Why did we switch to the macro AM33XX_IOPAD  ?

What is the advantage doing so ? By curiousity

Le ven. 17 juin 2016 à 16:05, Robert Nelson  a
écrit :

> On Fri, Jun 17, 2016 at 4:03 AM,   wrote:
> > The starting point for my questions is the BB-SPIDEV0-00A0.dts.
> >
> > 1. Description of problem:
> >
> > The following fragment was taken from the above device tree spec:
> >
> > fragment@0 {
> > target = <_pinmux>;
> > __overlay__ {
> > /* default state has all gpios released and mode set to
> uart1 */
> > bb_spi0_pins: pinmux_bb_spi0_pins {
> > pinctrl-single,pins = <
> > 0x150 0x30  /* spi0_sclk.spi0_sclk, INPUT_PULLUP |
> MODE0
> > */
> > 0x154 0x30  /* spi0_d0.spi0_d0, INPUT_PULLUP | MODE0
> */
> > 0x158 0x10  /* spi0_d1.spi0_d1, OUTPUT_PULLUP |
> MODE0 */
> > 0x15c 0x10  /* spi0_cs0.spi0_cs0, OUTPUT_PULLUP |
> MODE0
> > */
> > >;
> > };
> > };
> > };
> >
> > The fragment configures the P9.17, P9.18, P9.21, P9.22 pins to Mode 0 for
> > the SPI driver. I'm also aware of the table P9 Header table with the
> offset
> > addresses of the pins and the AM335x Sitara Processors Technical
> Reference
> > Manual (Rev. M) with information on how to configure the CPU registers.
> >
> > My problem is that the addresses in the device tree fragment above do not
> > match the addresses in the Reference Manual.
> >
> > In the fragment above the offset addresses are: 0x150, 0x154, 0x158 and
> > 0x15c. In the Reference Manual Chapter 9.3 page 1372 the offset addresses
> > are: 0x950, 0x954, 0x958, 0x95c.
> >
> > Question: Can someone help me understand where are the addresses from the
> > fragment taken/obtained/calculated from?
>
> On mainline, we recently switched to the "0x950" address vs "0x150",
> via the AM33XX_IOPAD macro:
>
>
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/arch/arm/boot/dts/am335x-bone-common.dtsi?id=e03b2a26d6bf93d1631aa36985892877986ee7b9
>
> old + 0x800 = offsets shown in reference manual..
>
>
>
>
> >
> > 2. Description of problem
> >
> > The following fragments were taken from the above device tree
> specification:
> >
> > ...
> > fragment@0 {
> > target = <_pinmux>;
> > __overlay__ {
> > ...
> >
> > ...
> > fragment@1 {
> > target = <>;   /* spi0 is numbered correctly */
> > __overlay__ {
> > ...
> >
> > I could not find on the web what is the functionality of the target
> property
> > in a device tree. I'm somehow familiar with the aliases concept. So I
> think
> > _pinmux and  are aliases for "something". However there is
> > nothing defined in the device tree specification above.
> >
> > Questions:
> >
> > What is the functionality/role of the target property? Where are the
> > _pinmux and  defined and what do they mean?
>
> The "target" is where the overlay will either append or add data to
> the existing device tree.
>
> am33xx_pinmux:
>
>
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/arch/arm/boot/dts/am335x-bone-common.dtsi?id=refs/tags/v4.7-rc3#n64
>
> Whereas spi0, is adding to the base, as that doesn't exist.
>
> Regards,
>
> --
> Robert Nelson
> https://rcn-ee.com/
>
> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/CAOCHtYhWx9Ya8jGUjmkn4HthnW-u14V53S1ksM68fpACNMQ4mg%40mail.gmail.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAF%2BMRtn3edq_t1UnbCtiptO3w3R2THmRQ4VBP-4vGxhp%2BgEDKA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Creating an image of the debian OS with all the data that is stored in it.

[Micka]

Yes but if it's on a SDCard? dd is not good because depending of the
vendors the size of the SD vary.

Le ven. 27 mai 2016 15:51, Jan Meitner  a écrit :

>  *http://elinux.org/BeagleBone_Black_Extracting_eMMC_contents*
> 
>
>>
>> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/a3a9df99-0726-4aec-9d25-4a3d504304ef%40googlegroups.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAF%2BMRtnPngN9D%2BRYHE4%2B%2ByOv4Dmpo9pqszLy5nSfOtzdkgeDZg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Problem in Beaglebone Black based custom hardware

[Micka]

Did you check on the scope if the device 34 and 70 work on i2C0 ? From the
kernel log it doesn't. ( that why I said: check I2C0) .


[2.241577] dummy 0-0034: Error -121 writing to cec:0xff
[2.247357] tda998x 0-0070: Error -121 reading from 0xa
[2.252978] tda998x 0-0070: Error -121 writing to 0xa
[2.310939] tda998x 0-0070: Error -121 reading from 0xa
[2.316513] tda998x 0-0070: Error -121 writing to 0xa

Maybe those errors are related to something bigger. ( from my experience
it's because they are not powered, but it can be something else... )


Also, from your log you have a kernel panic, that why the LED doesn't blink
as you want

[  120.340186] INFO:* task kworker/u:1:21 blocked for more than 60 seconds*
.
[  120.347182] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables
this message.
[  120.355702] *Kernel panic - not syncing: hung_task: blocked tasks*

[  120.362013] [] (unwind_backtrace+0x0/0xe0) from []
(panic+0x84/0x1e0)
[  120.370589] [] (panic+0x84/0x1e0) from []
(watchdog+0x1d0/0x224)
[  120.378707] [] (watchdog+0x1d0/0x224) from []
(kthread+0xa0/0xac)
[  120.386914] [] (kthread+0xa0/0xac) from []
(ret_from_fork+0x14/0x3c)

you don't have more line after 120.38 ?

can you use the console after the kernel panic ? is it in the freeze state ?

Something went wrong on your board, and If I were you I will fix the issue
with the two device on I2C0. After that if you have still a kernel panic,
we will figure it out.


And finally you have this error :

[0.346640] tps65217-bl tps65217-bl: no platform data provided
[0.346668] tps65217-bl: probe of tps65217-bl failed with error
-22


Looks like that you are using the backlight driver, something went wrong
with it. I don't know this driver, but check the documentation for the
device tree :

http://lxr.free-electrons.com/source/Documentation/devicetree/bindings/video/backlight/tps65217-backlight.txt?v=4.1

maybe you didn't configure the driver correctly. I'm not an expert on this
driver ^^


Micka,

Le ven. 20 mai 2016 09:11, Santi <santiago.tel...@gmail.com> a écrit :

> Thanks to all for your answers.
>
> Alex, the log that I've published here is already the log from U-boot
> obtained via UART0.
> In reference to the Beaglebone Eeprom, I have to say that the first thing
> we do after assembling a new board is to write in the eeprom a copy of the
> information contained in the original Beaglebone Black eeprom. After that,
> we insert an SD card to launch from the SD, check the correct behaviour and
> then burn the operating system in the internal emmc. In reference to length
> mistmaches, impedances and so, I don't think that is the problem, since
> this is the 4th version of the board (it has never happened before), and we
> kept the routes for memories invariable from the original Beaglebone
> design, in order to prevent that kind of problems. In addition, the person
> doing the electronic design has a great expertise in high frecuency
> electronics and is aware of the problems that might appear due to a bad
> design causing lost of data synchrony.
>
> I've also checked i2c communication and I've read the full content of the
> eeprom to check consistency. Everything seems to be working fine in
> reference to i2c.
>
>
> El miércoles, 18 de mayo de 2016, 23:25:36 (UTC+2), Alex escribió:
>
>> You have a lot of error on your log
>>
>> You have to know that when you create your own board, you need to
>> understand how the U-boot and the kernel know that it is a
>> beaglebone-black. Otherwise you will have wrong settings, particularly on
>> the tps. ( I had also a lot of errors before)
>>
>> In the u-boot, at the beginning it check the name of the board and the
>> version from the eeprom that is on i2c0. Depending of that,  the U-boot
>> configure many thing, one of them is the tps.
>>
>> First you need to look at the log from the U-boot. It's easy: connect to
>> uart0 and copy those log here.
>>
>> Depending of those errors I will tell you what is wrong. But from your
>> log, you should put a scope on i2c0, Looks like that the kernel can't read
>> the tps register. But it can be the consequence of the U-boot misconfigured.
>> ( maybe because your eeprom is empty)
>>
>> One of the solution is to download the source of the U-boot and apply a
>> patch that force the U-boot to assume that the board is a beaglebone black:
>>
>>
>> https://raw.githubusercontent.com/RobertCNelson/Bootloader-Builder/master/patches/v2015.10/0002-NFM-Production-eeprom-assume-device-is-BeagleBone-Bl.patch
>>
>> Thanks again  Robert Nelson for all your help.
>>
>>
>> Micka,
>>
>>
>>
>>
>> Le mer. 18 mai 2016 20:44, <santiag...@gmail.com> a écrit

Re: [beagleboard] Getting Bootchart setup on Debian 8.3

[Micka]

As Robert told u, you need to disable the service
systemd-timesyncd:

systemctl disable systemd-timesyncd

Le jeu. 19 mai 2016 13:27, John Baker <johnba...@ieee.org> a écrit :

> Thanks Micka.
>
> I just now tried that and putty.exe said that ntp isn't installed, so not
> removed, but I'll bet it's gotta be something like that. Maybe something
> for the Internet connection.
>
> John
>
> On 5/18/2016 8:33 PM, Micka wrote:
>
> sudo apt-get remove ntp
>
> Le mer. 18 mai 2016 23:53, John Baker < <bakerengineerin...@gmail.com>
> bakerengineerin...@gmail.com> a écrit :
>
>> Robert:
>> What script is trying to read the clock data from ntp? I have an Adafruit
>> DS3231 for the Real Time Clock and the BBB is taking a minute before it
>> gets the clock from the DS3231 so I suspect some script is trying to read
>> the ntp clock data and holding up the read of my DS3231 clock. Es posible?
>> John
>>
>> --
>> 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.
>> To view this discussion on the web visit
>> <https://groups.google.com/d/msgid/beagleboard/66884716-e25b-412e-98f1-97870f8f7127%40googlegroups.com>
>> https://groups.google.com/d/msgid/beagleboard/66884716-e25b-412e-98f1-97870f8f7127%40googlegroups.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 a topic in the
> Google Groups "BeagleBoard" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/beagleboard/Rtn0sS_z9DA/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> beagleboard+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> <https://groups.google.com/d/msgid/beagleboard/CAF%2BMRtk%3DQWMYfn_4Ox9gGox9HYjtPC8Z7HTNbKESAevfEseYEA%40mail.gmail.com?utm_medium=email_source=footer>
> https://groups.google.com/d/msgid/beagleboard/CAF%2BMRtk%3DQWMYfn_4Ox9gGox9HYjtPC8Z7HTNbKESAevfEseYEA%40mail.gmail.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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/af3c4179-e373-0cc9-4665-b8bbf5b91bfb%40ieee.org
> <https://groups.google.com/d/msgid/beagleboard/af3c4179-e373-0cc9-4665-b8bbf5b91bfb%40ieee.org?utm_medium=email_source=footer>
> .
> 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAF%2BMRtkBcrRJ3Z%2B7m8QRf-xMHzsBRdHZ_Xj8arENzfLaVkRRvQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] TPS65217 & Vdd_core 1.125V or 1.2V or 1.1V or .... ?

[Micka]

I already looked at that file and in the starterware there is no line that
contain DEFDCD3.

What I'm saying, is that nowhere I find the same value for DEFDCD3. Some
time it's 1.125V, somehwere else it's .95V-1.1V and in the BB_SRM it is
1.1V .

I'm asking to Gerald, what is the correct value for Vdd_Core ? I think that
the correct one is 1.1V. And what is the range ? 0.95V-1.1V ( device tree )

Le mer. 18 mai 2016 à 22:31, John Syne <john3...@gmail.com> a écrit :

> On May 18, 2016, at 1:58 AM, Micka <mickamus...@gmail.com> wrote:
>
> Hi,
>
> In the u-boot
> http://git.denx.de/?p=u-boot.git;a=blob;f=board/ti/am335x/board.c;h=4330be64994dc6cbfaff4b865fee44d82f660a3d;hb=HEAD#l255
>
> there is those lines :
>
> 255
> <http://git.denx.de/?p=u-boot.git;a=blob;f=board/ti/am335x/board.c;h=4330be64994dc6cbfaff4b865fee44d82f660a3d;hb=HEAD#l255>
> /* Set DCDC3 (CORE) voltage to 1.125V */
> 256
> <http://git.denx.de/?p=u-boot.git;a=blob;f=board/ti/am335x/board.c;h=4330be64994dc6cbfaff4b865fee44d82f660a3d;hb=HEAD#l256>
> if (tps65217_voltage_update(TPS65217_DEFDCDC3,
> 257
> <http://git.denx.de/?p=u-boot.git;a=blob;f=board/ti/am335x/board.c;h=4330be64994dc6cbfaff4b865fee44d82f660a3d;hb=HEAD#l257>
> TPS65217_DCDC_VOLT_SEL_1125MV))
>
>
> In the device tree there is those lines :
>
> dcdc3_reg: regulator@2 {
> /* VDD_CORE voltage limits *0.95V -* *1.1V* with +/-4% tolerance */
> regulator-name = "vdd_core";
> regulator-min-microvolt = <925000>;
> regulator-max-microvolt = <115>;
> regulator-boot-on;
> regulator-always-on;
> };
>
> in the starterware from texas + the patch for the bbb I have nothing
> concerning the DEFDCD3.
>
> And finally in the BBB_SRM you have those lines :
>
> The VDD_CORE rail can deliver up to 1.2A at 1.1V. This rail is not
> accessible for use anywhere else on the board and only connects to the
> processor. This rail is fixed at 1.1V and is not scaled.
>
> So what is the correct configuration for this output ?
>
> I believe this is done in bootloader/src/armv7a/am335x/bl_platform.c
>
> In essence, you have to create a bootable SDCard for Starterware which
> sets the regulator voltages for you.
>
> Regards,
> John
>
>
>
> Micka,
>
>
>
> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/CAF%2BMRtm7heTJ45tuWoHt9v1ajBV4XN%2BCk7t%2BfGTn-mrjjJsD%2BA%40mail.gmail.com
> <https://groups.google.com/d/msgid/beagleboard/CAF%2BMRtm7heTJ45tuWoHt9v1ajBV4XN%2BCk7t%2BfGTn-mrjjJsD%2BA%40mail.gmail.com?utm_medium=email_source=footer>
> .
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/D2B2F1F3-E3ED-43C6-9B24-2D32028E99B4%40gmail.com
> <https://groups.google.com/d/msgid/beagleboard/D2B2F1F3-E3ED-43C6-9B24-2D32028E99B4%40gmail.com?utm_medium=email_source=footer>
> .
> 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAF%2BMRtk%3DekMzxdLE6J%2BnUF6aef7EC78EUg_GPRzA76_yAPk%3DiQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Hardware watchdog for BBB

[Micka]

He didn't finish his sentence.

Le jeu. 19 mai 2016 05:47, William Hermans  a écrit :

> *Be careful about taking hardware design info from computer science degree
>> types.  John seems to understand hardware this other dude bill is a blow
>> hard and a*
>
>
> That comment, and a nickle is worth about 5 cents. . .
>
>
>
> On Wed, May 18, 2016 at 7:38 PM, 'Mark Lazarewicz' via BeagleBoard <
> beagleboard@googlegroups.com> wrote:
>
>> Be careful about taking hardware design info from computer science degree
>> types.  John seems to understand hardware this other dude bill is a blow
>> hard and a
>>
>>
>>
>>
>> Sent from Yahoo Mail on Android
>> 
>>
>> On Mon, May 16, 2016 at 3:34 PM, John Syne
>>  wrote:
>>
>> On May 15, 2016, at 4:25 PM, evilwulfie  wrote:
>>
>> --
>> 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.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/beagleboard/746532426.5197607.1463625501671.JavaMail.yahoo%40mail.yahoo.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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/CALHSORqM8ewgB4SmnS%3DeD19i2ALwH%3D32LMMx7_VvnNdGXXwyew%40mail.gmail.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAF%2BMRt%3DpV4Y%3Dcg2-BrDPXoCpzUCbasDYYZ%3DTUN8T6%2BSm_vQWvQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Getting Bootchart setup on Debian 8.3

[Micka]

sudo apt-get remove ntp

Le mer. 18 mai 2016 23:53, John Baker  a
écrit :

> Robert:
> What script is trying to read the clock data from ntp? I have an Adafruit
> DS3231 for the Real Time Clock and the BBB is taking a minute before it
> gets the clock from the DS3231 so I suspect some script is trying to read
> the ntp clock data and holding up the read of my DS3231 clock. Es posible?
> John
>
> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/66884716-e25b-412e-98f1-97870f8f7127%40googlegroups.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAF%2BMRtk%3DQWMYfn_4Ox9gGox9HYjtPC8Z7HTNbKESAevfEseYEA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Problem in Beaglebone Black based custom hardware

[Micka]

You have a lot of error on your log

You have to know that when you create your own board, you need to
understand how the U-boot and the kernel know that it is a
beaglebone-black. Otherwise you will have wrong settings, particularly on
the tps. ( I had also a lot of errors before)

In the u-boot, at the beginning it check the name of the board and the
version from the eeprom that is on i2c0. Depending of that,  the U-boot
configure many thing, one of them is the tps.

First you need to look at the log from the U-boot. It's easy: connect to
uart0 and copy those log here.

Depending of those errors I will tell you what is wrong. But from your log,
you should put a scope on i2c0, Looks like that the kernel can't read the
tps register. But it can be the consequence of the U-boot misconfigured. (
maybe because your eeprom is empty)

One of the solution is to download the source of the U-boot and apply a
patch that force the U-boot to assume that the board is a beaglebone black:

https://raw.githubusercontent.com/RobertCNelson/Bootloader-Builder/master/patches/v2015.10/0002-NFM-Production-eeprom-assume-device-is-BeagleBone-Bl.patch

Thanks again  Robert Nelson for all your help.


Micka,





Le mer. 18 mai 2016 20:44, <santiago.tel...@gmail.com> a écrit :

> Hello!
>
> I'm experiencing a really weird problem with custom hardware based in
> Beaglebone Black. This is the 4th revision of our hardware and we have
> never found this issue until now. Everything related with the Beaglebone
> Black part of the circuit remains invariable (except for RAM and emmc,
> since because of lack of stock we had to change to compatible
> ICs, EMMC04G-S100-A08U from Kingston and D2516EC4BXGGB, also from Kingston).
>
> We have 4 prototypes for this model:  3 of them are experiencing this
> problem, but not the other one.
>
> The problem: I run Ubuntu 12.04 from an SD card, with the intention of
> flashing an Ubuntu 14.04 image to the board flash. The operating systems
> launches from the SD and I'm able to log In, but roughly one minute after
> that, the board freezes (a few USRx leds remain fixed and I can't do
> anything in the board anymore).
>
> As I've told, this is happening in 3 of 4 prototypes that we have. One
> common thing that happens in the 3 boards which are freezing is that USR3
> led remains on (it doesn't blink), and this is not happening in the board
> that works ok.
>
> Of course, we have checked all voltages in the board and looked for short
> circuits, but everything seems to be ok.
>
> I'll paste the system log obtained from the debug uart, since I think the
> last 7 lines can be specially significant to explain the problem. Any help
> or suggestion would be appreciated.
>
> Thanks in advance!
>
> 18/05/2016 14:16:39.353 [RX] -  
> U-Boot SPL 2013.10-00249-g15c5cdf (Nov 17 2013 - 16:35:11)
> reading args
> spl: error reading image args, err - -1
> reading u-boot.img
> reading u-boot.img
> 
> 
> U-Boot 2013.10-00249-g15c5cdf (Nov 17 2013 - 16:35:11)
> 
> I2C:   ready
> DRAM:  512 MiB
> WARNING: Caches not enabled
> NAND:  0 MiB
> MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
> *** Warning - readenv() failed, using default environment
> 
> Net:not set. Validating first E-fuse MAC
> cpsw, usb_ether
> Hit any key to stop autoboot:  10 
> mmc0 is current device
> SD/MMC found on device 0
> reading uEnv.txt
> 340 bytes read in 3 ms (110.4 KiB/s)
> Loaded environment from uEnv.txt
> Importing environment from mmc ...
> Running uenvcmd ...
> 3314544 bytes read in 487 ms (6.5 MiB/s)
> 24884 bytes read in 48 ms (505.9 KiB/s)
> Kernel image @ 0x8020 [ 0x00 - 0x329370 ]
> ## Flattened Device Tree blob at 80f8
>Booting using the fdt blob at 0x80f8
>Using Device Tree in place at 80f8, end 80f89133
> 
> Starting kernel ...
> 
> Uncompressing Linux... done, booting the kernel.
> [0.00] Booting Linux on physical CPU 0x0
> [0.00] Initializing cgroup subsys cpu
> [0.00] Linux version 3.8.13-bone30 (root@imx6q-sabrelite-1gb-1)
> (gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) ) #1 SMP Thu Nov 14
> 11:19:20 UTC 2013
> [0.00] CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7),
> cr=10c5387d
> [0.00] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing
> instruction cache
> [0.00] Machine: Generic AM33XX (Flattened Device Tree), model: TI
> AM335x BeagleBone
> [0.00] Memory policy: ECC disabled, Data cache writeback
> [0.00] AM335X ES1.0 (neon )
> [0.00] PERCPU: Embedded 9 pages/cpu @c0e45000 s14080 r8192 d14592
> u36864
> [0.00] Built 1 zonelists in Zone order, mobility grouping on.
> Total pages: 129792
> [0.00] Kernel command line: console=ttyO

Re: [beagleboard] Beaglebone Black and ROS

[Micka]

Beaglebone black is a linux device... So any tutorial that explain ros with
linux will work.

Le mer. 18 mai 2016 15:32,  a écrit :

>
> How can i learn to controll beaglebone black with ros? Any book, tutorial,
> online course?
>
> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/bf9de850-c14a-4567-9e79-cd5db17a0eb8%40googlegroups.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAF%2BMRt%3DMRF5Y_QoYpPgDSvY9RTdJpjgrRVYAop9-uKqrg355kA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] TPS65217 & Vdd_core 1.125V or 1.2V or 1.1V or .... ?

[Micka]

Hi,

In the u-boot
http://git.denx.de/?p=u-boot.git;a=blob;f=board/ti/am335x/board.c;h=4330be64994dc6cbfaff4b865fee44d82f660a3d;hb=HEAD#l255

there is those lines :

255
<http://git.denx.de/?p=u-boot.git;a=blob;f=board/ti/am335x/board.c;h=4330be64994dc6cbfaff4b865fee44d82f660a3d;hb=HEAD#l255>
/* Set DCDC3 (CORE) voltage to 1.125V */
256
<http://git.denx.de/?p=u-boot.git;a=blob;f=board/ti/am335x/board.c;h=4330be64994dc6cbfaff4b865fee44d82f660a3d;hb=HEAD#l256>
if (tps65217_voltage_update(TPS65217_DEFDCDC3,
257
<http://git.denx.de/?p=u-boot.git;a=blob;f=board/ti/am335x/board.c;h=4330be64994dc6cbfaff4b865fee44d82f660a3d;hb=HEAD#l257>
TPS65217_DCDC_VOLT_SEL_1125MV))


In the device tree there is those lines :

dcdc3_reg: regulator@2 {
/* VDD_CORE voltage limits *0.95V -* *1.1V* with +/-4% tolerance */
regulator-name = "vdd_core";
regulator-min-microvolt = <925000>;
regulator-max-microvolt = <115>;
regulator-boot-on;
regulator-always-on;
};

in the starterware from texas + the patch for the bbb I have nothing
concerning the DEFDCD3.

And finally in the BBB_SRM you have those lines :

The VDD_CORE rail can deliver up to 1.2A at 1.1V. This rail is not
accessible for use anywhere else on the board and only connects to the
processor. This rail is fixed at 1.1V and is not scaled.

So what is the correct configuration for this output ?


Micka,

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAF%2BMRtm7heTJ45tuWoHt9v1ajBV4XN%2BCk7t%2BfGTn-mrjjJsD%2BA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Hardware watchdog for BBB

[Micka]

Gerald what is your opinion on this subject ?

Le lun. 16 mai 2016 21:46, evilwulfie  a écrit :

> spend 50 bux on a power supply to solve a 5 dollar problem  yeah right.
>
>
>
> On 5/16/2016 12:34 PM, John Syne wrote:
>
>
> On May 15, 2016, at 4:25 PM, evilwulfie < 
> evilwul...@gmail.com> wrote:
>
> msp430 has an internal watchdog
>
> And so does the AM3358, so I’m not sure whats your point? If it is a
> micro-controller, it is not guaranteed to boot up successfully every time,
> given an unstable power supply. To start with, you need to make the power
> supply more predictable so that brown outs, dips and sags are not seen by
> the micro-controller and that power down only occurs if the input power
> fails for more than a specified time. Also, if you do start a shutdown,
> then a full power cycle is needed in a controlled manner. When input power
> returns, don’t boot until the input power looks reliable.
>
> This is where you need an understanding of how the power utility network
> operates, which includes understanding how protection operates, what an ARC
> (Automatic Reclosure Relays) do, etc. For example, when a large breaker
> trips due to a protective signal, the ARC will attempt to reclose that
> breaker, sometimes more than once. At night, in a storm, you will see your
> lights dim for a second or two; that is an ARC operation. When a
> transformer has water in the oil or when a insulator is arching, or a power
> line is arching on the ground, these all result in very strange power
> behavior. In summary, power failure isn’t just an on or off problem, but a
> multitude of more problematic cases.
>
> Regards,
> John
>
>
> On 5/15/2016 3:37 PM, John Syne wrote:
>
>
> On May 15, 2016, at 3:14 PM, evilwulfie  wrote:
>
> We use an external msp430 for our intelligent watchdog
>
> So who or what monitors the MSP430? Since it is a micro-controller, it is
> easy to get it into a lock situation. All you need is a programable power
> supply which will ramp up and down the voltage into the micro-controller at
> predefined times and it will lock and become completely unresponsive.
> Granted this will rarely happen, but in our applications where 100K or more
> devices are installed, we cannot accept some devices locking up because of
> a power failure.
>
> Regards,
> John
>
>
>
> On 5/15/2016 1:07 PM, Super Twang wrote:
>
>
>
> I've just come across this conversation in my own search for a rock-solid,
> embeddable configuration for the BeagleBone Black.  I’m trying to develop
> an embedded controller device that needs to live behind walls, in ceilings
> and in other inaccessible places. ( It is for the automation of art & other
> electronic installations.)
>
> From what I gather here, the BBB is not quite up to the task, without an
> external watchdog circuit (please correct me if I’m misreading this thread).
>
> @John3909: Your suggestion of the GreenPak prompted my own discovery of
> that tech — it looks great, esp the ecosystem of tools around the platform.
>
> In looking around, I found some Silego application notes that implement a
> hardware watchdog for MCUs.
> http://www.silego.com/products/352/312/AN-1058.html  This might be a
> useful starting point for anyone using GreenPak for a hardware watchdog.
>
> @John3909: Does this design look like it might be a good fit for the BBB?
> (Not knowing how to read GreenPak internals, it is not obvious to me)
>
> Alternately, I'm wondering in the two years that have passed since this
> thread started, if anyone has developed a hardware watchdog design for the
> BBB they'd be willing to share.  An open-source hardware watchdog for the
> BBB would go a long way towards ameliorating the hardware issues with the
> PMIC on RevC, and allow it to prosper as a base for applications where
> long-term reliability matters.
>
> Although I’m first and foremost a software engineer, I've got some
> electronics chops (albeit mostly digital), but (sadly) very limited
> hardware design equipment (oscilloscope, etc).  [That said, I have iron,
> and will solder!]  I’d be happy to develop & contribute the software
> components for such a system (I’d envision a library + device tree overlay)
> if someone(s) else would like to partner up to design the hardware side.
>
> Best,
>
> ST
>
> --
> 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.
> To view this discussion on the web visit
> 
> https://groups.google.com/d/msgid/beagleboard/c7fb39d8-84ef-4127-9db8-cd65a6965e31%40googlegroups.com
> .
> For more 

Re: [beagleboard] Hardware watchdog for BBB

[Micka]

The UCCx946 is designed to provide accurate microprocessor supervision,
including reset and watchdog functions. During power up, the device asserts
a reset signal RES with VDD as low as 1 V. The reset signal remains
asserted until the VDD voltage rises and remains above the reset threshold
for the reset period. Both reset threshold and reset period are
programmable by the user.

The UCCx946 is also resistant to glitches on the VDD line. Once RES has
been deasserted, any drops below the threshold voltage need to be of
certain time duration and voltage magnitude to generate a reset signal.
These values are shown in Figure 1. An I/O line of the microprocessor may
be tied to the watchdog input (WDI) for watchdog functions. If the I/O line
is not toggled within a set watchdog period, programmable by the user, WDO
is asserted. The watchdog function is disabled during reset condition

Le lun. 16 mai 2016 09:50, Micka <mickamus...@gmail.com> a écrit :

> You dont need an external microcontroller  Some watchdog from Texas do
> a good job like the uccx946.
>
> Le lun. 16 mai 2016 09:01, arsi <a...@chello.sk> a écrit :
>
>> Hi,
>>
>> I use this:
>>
>>
>>
>>
>>
>> PIC 10F200 source code:
>>
>> /*
>>File:   main.c
>>Author: arsi
>>
>>Created on May 22, 2015, 10:32 AM
>>  */#include #include #include #define _XTAL_FREQ 
>> 400#pragma config WDTE = ON// Watchdog Timer (WDT 
>> enabled)#pragma config CP = OFF // Code Protect (Code protection 
>> off)#pragma config MCLRE = OFF  // Master Clear Enable (GP3/MCLR pin 
>> fuction is digital I/O, MCLR internally tied to VDD)
>> void delay1() {
>> __delay_ms(1000);
>> }bool flag = false;int counter = 0;
>> void main(void) {#asm
>> CLRWDT
>> CLRF TMR0
>> CLRWDT
>> MOVLW 0b
>> OPTION#endasm
>> CLRWDT();
>> TRIS = 0b1110;
>> CLRWDT();
>> GP0 = 0;
>> __delay_ms(500);
>> CLRWDT();
>> TRIS = 0b;
>> CLRWDT();
>> //pause for BBB boot up
>> for (int i = 0; i < 120; i++) {
>> delay1();
>> CLRWDT();
>> }
>> counter = 0;
>> while (true) {
>> delay1();
>> if (counter < 120) {
>> CLRWDT();
>> }
>> if (flag != GP1) {
>> counter = 0;
>> flag = GP1;
>> } else {
>> counter++;
>> }
>>
>> }
>> }
>>
>>
>>
>> ***
>> wd script on BBB:
>>
>> #!/bin/bash
>> sleep 10
>> echo 60 > /sys/class/gpio/export
>> echo "out" > /sys/class/gpio/gpio60/directionwhile :do
>> echo "0" > /sys/class/gpio/gpio60/value
>> sleep 1
>> echo "1" > /sys/class/gpio/gpio60/value
>> sleep 1
>>
>> done
>>
>>
>>
>> ***
>>
>> Arsi
>>
>> --
>>
>> *From:* Kb2pnm
>> *Sent:* Saturday, March 22, 2014 6:08PM
>> *To:* Beagleboard
>> *Subject:* [beagleboard] Hardware watchdog for BBB
>>
>>
>> HI, I have been working for a wile on safe power supply for BBB with
>> backup power provided by supercapacitors. In case of power failure there
>> is  just enough  time to safely and nicely shut down BBB. For some reason
>> BBB does not always wake up fully. I need hardware dogwatch. Did anybody
>> design such a thing? I was able to find some design for ardunio:
>> http://www.playwitharduino.com/?p=291.
>> Anybody has any experience with hardware dogwatch for BBB??
>> Thanks in advance
>> Robert
>> --
>> 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 th

Re: [beagleboard] Hardware watchdog for BBB

[Micka]

You dont need an external microcontroller  Some watchdog from Texas do
a good job like the uccx946.

Le lun. 16 mai 2016 09:01, arsi  a écrit :

> Hi,
>
> I use this:
>
>
>
>
>
> PIC 10F200 source code:
>
> /*
>File:   main.c
>Author: arsi
>
>Created on May 22, 2015, 10:32 AM
>  */#include #include #include #define _XTAL_FREQ 
> 400#pragma config WDTE = ON// Watchdog Timer (WDT enabled)#pragma 
> config CP = OFF // Code Protect (Code protection off)#pragma config 
> MCLRE = OFF  // Master Clear Enable (GP3/MCLR pin fuction is digital I/O, 
> MCLR internally tied to VDD)
> void delay1() {
> __delay_ms(1000);
> }bool flag = false;int counter = 0;
> void main(void) {#asm
> CLRWDT
> CLRF TMR0
> CLRWDT
> MOVLW 0b
> OPTION#endasm
> CLRWDT();
> TRIS = 0b1110;
> CLRWDT();
> GP0 = 0;
> __delay_ms(500);
> CLRWDT();
> TRIS = 0b;
> CLRWDT();
> //pause for BBB boot up
> for (int i = 0; i < 120; i++) {
> delay1();
> CLRWDT();
> }
> counter = 0;
> while (true) {
> delay1();
> if (counter < 120) {
> CLRWDT();
> }
> if (flag != GP1) {
> counter = 0;
> flag = GP1;
> } else {
> counter++;
> }
>
> }
> }
>
>
>
> ***
> wd script on BBB:
>
> #!/bin/bash
> sleep 10
> echo 60 > /sys/class/gpio/export
> echo "out" > /sys/class/gpio/gpio60/directionwhile :do
> echo "0" > /sys/class/gpio/gpio60/value
> sleep 1
> echo "1" > /sys/class/gpio/gpio60/value
> sleep 1
>
> done
>
>
>
> ***
>
> Arsi
>
> --
>
> *From:* Kb2pnm
> *Sent:* Saturday, March 22, 2014 6:08PM
> *To:* Beagleboard
> *Subject:* [beagleboard] Hardware watchdog for BBB
>
>
> HI, I have been working for a wile on safe power supply for BBB with
> backup power provided by supercapacitors. In case of power failure there
> is  just enough  time to safely and nicely shut down BBB. For some reason
> BBB does not always wake up fully. I need hardware dogwatch. Did anybody
> design such a thing? I was able to find some design for ardunio:
> http://www.playwitharduino.com/?p=291.
> Anybody has any experience with hardware dogwatch for BBB??
> Thanks in advance
> Robert
> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/57397009.205%40chello.sk
> 
> .
> 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAF%2BMRtmfNSrCXk-egMpz-gGqzjt%3D8qRgsrzv2FbrQUqrLAw0Lw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] debian 8: initramfs unpacking failed junk in compressed archive

[Micka]

Hi,

initramfs unpacking failed junk in compressed archive

What should I do with this error ?


Micka,

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAF%2BMRt%3DZqdcB6f-hesJAn4jJpvnued%3D%2B%3D950x5yMH0kaG-PPSw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Getting Bootchart setup on Debian 8.3

[Micka]

Robert Nelson,

If I'm not wrong in the file /etc/init.d/networking

The line that take a lot of time is : *udevadm settle*

  Watches the udev event queue, and exits if all current events are
   handled.


That where we wait for a long long time !


Le mar. 10 mai 2016 à 00:29, William Hermans <yyrk...@gmail.com> a écrit :

> @Robert,
>
> By the way, I'm curious what's holding back the BBB's boot up in jessie ?
> I remember it used to be every bit as snappy as the above stats listed for
> my rpi 3. Except the BBB didn't have, or even need quad cores . . .
>
> On Mon, May 9, 2016 at 3:26 PM, William Hermans <yyrk...@gmail.com> wrote:
>
>>
>> Startup finished in 3.159s (kernel) + 7.910s (userspace) = 11.069s
>>
>> *cough*Raspbian GNU/Linux 8 (jessie) rpi (Linux 4.1.19-v7+ #858 SMP Tue
>> Mar 15 15:56:00 GMT 2016) arm*cough*
>>
>> On Mon, May 9, 2016 at 8:03 AM, Robert Nelson <robertcnel...@gmail.com>
>> wrote:
>>
>>>
>>>
>>> On Mon, May 9, 2016 at 10:00 AM, Micka <mickamus...@gmail.com> wrote:
>>>
>>>> Robert,
>>>>
>>>> Which service is calling the script /opt/scripts/boot/am335x_evm.sh ?
>>>>
>>>
>>> generic-board-startup.service ->
>>>
>>> /opt/scripts/boot/generic-startup.sh ->
>>>
>>> /opt/scripts/boot/am335x_evm.sh
>>>
>>> Regards,
>>>
>>> --
>>> Robert Nelson
>>> https://rcn-ee.com/
>>>
>>> --
>>> 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.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/beagleboard/CAOCHtYhW8Pg5owxnqCow5mfrrY%3D0fgLUkpupXRW7Ywem-i%2BuDQ%40mail.gmail.com
>>> <https://groups.google.com/d/msgid/beagleboard/CAOCHtYhW8Pg5owxnqCow5mfrrY%3D0fgLUkpupXRW7Ywem-i%2BuDQ%40mail.gmail.com?utm_medium=email_source=footer>
>>> .
>>>
>>> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/CALHSORqWNwep724c_D5uHyzLRCzeZrU5MYjQij7%3DBODg1hZKow%40mail.gmail.com
> <https://groups.google.com/d/msgid/beagleboard/CALHSORqWNwep724c_D5uHyzLRCzeZrU5MYjQij7%3DBODg1hZKow%40mail.gmail.com?utm_medium=email_source=footer>
> .
> 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAF%2BMRt%3Deb0ZTbWOpr_q_QnhdLfc4KQbxx5sJYS9%2B1ANyT27gBA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Getting Bootchart setup on Debian 8.3

[Micka]

The problem comes from the network  I will look into that tomorrow.

Le mar. 10 mai 2016 à 00:26, William Hermans <yyrk...@gmail.com> a écrit :

>
> Startup finished in 3.159s (kernel) + 7.910s (userspace) = 11.069s
>
> *cough*Raspbian GNU/Linux 8 (jessie) rpi (Linux 4.1.19-v7+ #858 SMP Tue
> Mar 15 15:56:00 GMT 2016) arm*cough*
>
> On Mon, May 9, 2016 at 8:03 AM, Robert Nelson <robertcnel...@gmail.com>
> wrote:
>
>>
>>
>> On Mon, May 9, 2016 at 10:00 AM, Micka <mickamus...@gmail.com> wrote:
>>
>>> Robert,
>>>
>>> Which service is calling the script /opt/scripts/boot/am335x_evm.sh ?
>>>
>>
>> generic-board-startup.service ->
>>
>> /opt/scripts/boot/generic-startup.sh ->
>>
>> /opt/scripts/boot/am335x_evm.sh
>>
>> Regards,
>>
>> --
>> Robert Nelson
>> https://rcn-ee.com/
>>
>> --
>> 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.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/beagleboard/CAOCHtYhW8Pg5owxnqCow5mfrrY%3D0fgLUkpupXRW7Ywem-i%2BuDQ%40mail.gmail.com
>> <https://groups.google.com/d/msgid/beagleboard/CAOCHtYhW8Pg5owxnqCow5mfrrY%3D0fgLUkpupXRW7Ywem-i%2BuDQ%40mail.gmail.com?utm_medium=email_source=footer>
>> .
>>
>> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/CALHSORp7pEHyK88EWNAe-jp2VDN%3D%3DhmgOV759N%2BQ4g1aQEKWqw%40mail.gmail.com
> <https://groups.google.com/d/msgid/beagleboard/CALHSORp7pEHyK88EWNAe-jp2VDN%3D%3DhmgOV759N%2BQ4g1aQEKWqw%40mail.gmail.com?utm_medium=email_source=footer>
> .
> 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAF%2BMRtmU_iKiLws9kk%2Bk_KyKUP4X79Tg4y1x54s-1wGGjm-3tg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Getting Bootchart setup on Debian 8.3

[Micka]

Robert,

Which service is calling the script /opt/scripts/boot/am335x_evm.sh ?

  bonescript-autorun.service
  bonescript.service
  capemgr.service



Le lun. 9 mai 2016 à 16:42, Robert Nelson <robertcnel...@gmail.com> a
écrit :

> On Mon, May 9, 2016 at 9:38 AM, Micka <mickamus...@gmail.com> wrote:
>
>> yes sorry,
>>
>> I know that It does a lot of thing, and it tooks a lot of time ^^ .
>>
>> I will have to dig into it .
>>
>
> Yeah, i'd like to cut it down in time. ;)
>
> Regards,
>
>
> --
> Robert Nelson
> https://rcn-ee.com/
>
> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/CAOCHtYg2JryDiRAjBAeip9iiB54gP-iPLrwhyRU%3DtXHN7xbmRw%40mail.gmail.com
> <https://groups.google.com/d/msgid/beagleboard/CAOCHtYg2JryDiRAjBAeip9iiB54gP-iPLrwhyRU%3DtXHN7xbmRw%40mail.gmail.com?utm_medium=email_source=footer>
> .
> 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAF%2BMRtndTB%2BybZ4gLuw72hK8dJM-Xe0osOC9x5cqmBudkQh7Pg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Getting Bootchart setup on Debian 8.3

[Micka]

yes sorry,

I know that It does a lot of thing, and it tooks a lot of time ^^ .

I will have to dig into it .



Le lun. 9 mai 2016 à 15:38, Robert Nelson <robertcnel...@gmail.com> a
écrit :

> On Mon, May 9, 2016 at 8:33 AM, Micka <mickamus...@gmail.com> wrote:
>
>> Thank you Robert !
>>
>> networking.service (18.800s)
>> generic-board-startup.service (6.242s)
>>
>
> This hits the board eeprom over i2c, along with a module load, fires up
> udhpc and finally an overlay load..
>
> Regards,
>
> --
> Robert Nelson
> https://rcn-ee.com/
>
> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/CAOCHtYhMQM6_V%3DzuJ%3D%3DecP-QR5U1%3DQm0dyszUi08b2Kou600aA%40mail.gmail.com
> <https://groups.google.com/d/msgid/beagleboard/CAOCHtYhMQM6_V%3DzuJ%3D%3DecP-QR5U1%3DQm0dyszUi08b2Kou600aA%40mail.gmail.com?utm_medium=email_source=footer>
> .
> 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAF%2BMRtmmzWyz-mhi-D11JXWA77NHF%2Biq%2BkVoC6ev9hYWo%3DOX-g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Getting Bootchart setup on Debian 8.3

[Micka]

Thank you Robert !

networking.service (18.800s)
generic-board-startup.service (6.242s)

lol

Le lun. 9 mai 2016 à 15:25, Robert Nelson  a
écrit :

> On Mon, May 9, 2016 at 7:52 AM, Jean-Sebastien Stoezel <
> js.stoe...@gmail.com> wrote:
>
>> Hi:
>>
>> I would like to reduce the boot time of my BBB/BBG, running Debian 8.3.
>> While I was able to find related posts on this forum, they seem old-ish and
>> I wasn't able to implement what they suggested.
>>
>> The first advice was to install Bootchart, which seems to be
>> pre-installed on the Debian 8.3 I am running. What I can't seem to be able
>> to do is setup Bootchart to actually collect data.
>> The information I found online suggests modifying /boot/uEnv.txt to
>> include
>>
>> *systemd=quiet init=/sbin/bootchartd *
>>
>> But this still didn't seem to enable Bootchart (i.e. no
>> /var/log/bootchart.tgz file generated).
>>
>> Would anybody have updated instructions on how to setup Bootchart with
>> systemd and Debian 8.3?
>>
>
>
> systemd-analyze plot > file.svg
>
> Regards,
>
> --
> Robert Nelson
> https://rcn-ee.com/
>
> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/CAOCHtYgFZjxUhLu9UMDb7Ncj7JQvk4XGjeQsZJV7m6U39TgAXw%40mail.gmail.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAF%2BMRtnqzq0WDu19hKSbCJb_WsjfgEDVnCQu9fk3bkkz-vrmVg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] debian 8 image : connman static ip : set nameserver

[Micka]

Hi,

I'm using debian 8 for the beaglebone black ...

I discovered that the beaglebone switch to connman to manage the network ?
why ? that more complicate than using the file /etc/network/interfaces

I've difficulties with the nameserver, normally it's in the file
/etc/resolv.conf, but with connman, it does't work !

Any idea ?

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAF%2BMRtmUEEHWzPFXmc%3Dzjk2Faq2hLi12vH%3D%3Dd%2BfM7gToE1%3DVEg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] error at boot in the image : bone-debian-8.4-lxqt-4gb-armhf-2016-04-25-4gb

[Micka]

this one :

fsck: error 2 (No such file or directory) while executing fsck.ext4 for
/dev/mmcblk0p1

I don't understand it.

also, how do you set the IP address on jessie ?

/etc/network/interfaces ?
auto eth0
iface eth0 inet static
address 100.91.120.21
netmask 255.255.255.0
gateway 100.91.120.254





Le lun. 2 mai 2016 à 14:56, Robert Nelson <robertcnel...@gmail.com> a
écrit :

> Hi Micka,
>
> On Mon, May 2, 2016 at 5:28 AM, Micka <mickamus...@gmail.com> wrote:
>
>> Starting kernel ...
>>
>> [3.540286] wkup_m3_ipc 44e11324.wkup_m3_ipc: could not get rproc
>> handle
>> [3.788349] cpu cpu0: cpu0 clock notifier not ready, retry
>> [3.939012] bone_capemgr bone_capemgr: slot #0: No cape found
>> [3.999007] bone_capemgr bone_capemgr: slot #1: No cape found
>> [4.059010] bone_capemgr bone_capemgr: slot #2: No cape found
>> [4.119005] bone_capemgr bone_capemgr: slot #3: No cape found
>> Loading, please wait...
>> fsck: error 2 (No such file or directory) while executing fsck.ext4 for
>> /dev/mmcblk0p1
>> fsck exited with status code 8
>> [   11.750782] systemd[1]: Failed to set memory.limit_in_bytes on :
>> Invalid argument
>> [   12.536934] systemd-fsck[164]: rootfs: clean, 133831/217728 files,
>> 795110/870144 blocks
>> [   21.686784]  remoteproc1: failed to load am335x-pru0-fw
>> [   21.766819]  remoteproc1: request_firmware failed: -2
>> [   21.772016] pru-rproc 4a334000.pru0: rproc_boot failed
>> [   21.970925]  remoteproc1: failed to load am335x-pru1-fw
>> [   21.984090]  remoteproc1: request_firmware failed: -2
>> [   21.989339] pru-rproc 4a338000.pru1: rproc_boot failed
>>
>
>
> Correct, there are a few of them, which one is catching your eye that
> needs some explaining..
>
> Regards,
>
> --
> Robert Nelson
> https://rcn-ee.com/
>
> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/CAOCHtYha_fFaJrVSy5PviyAEEVEr8uen7zi7LEfTxBYhGy3c1A%40mail.gmail.com
> <https://groups.google.com/d/msgid/beagleboard/CAOCHtYha_fFaJrVSy5PviyAEEVEr8uen7zi7LEfTxBYhGy3c1A%40mail.gmail.com?utm_medium=email_source=footer>
> .
> 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAF%2BMRtntN8pcrUduhmUmbSa9Ksu9twXt%2BW3Eh9pXJ0u5NDUZjw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] error at boot in the image : bone-debian-8.4-lxqt-4gb-armhf-2016-04-25-4gb

[Micka]

Starting kernel ...

[3.540286] wkup_m3_ipc 44e11324.wkup_m3_ipc: could not get rproc handle
[3.788349] cpu cpu0: cpu0 clock notifier not ready, retry
[3.939012] bone_capemgr bone_capemgr: slot #0: No cape found
[3.999007] bone_capemgr bone_capemgr: slot #1: No cape found
[4.059010] bone_capemgr bone_capemgr: slot #2: No cape found
[4.119005] bone_capemgr bone_capemgr: slot #3: No cape found
Loading, please wait...
fsck: error 2 (No such file or directory) while executing fsck.ext4 for
/dev/mmcblk0p1
fsck exited with status code 8
[   11.750782] systemd[1]: Failed to set memory.limit_in_bytes on : Invalid
argument
[   12.536934] systemd-fsck[164]: rootfs: clean, 133831/217728 files,
795110/870144 blocks
[   21.686784]  remoteproc1: failed to load am335x-pru0-fw
[   21.766819]  remoteproc1: request_firmware failed: -2
[   21.772016] pru-rproc 4a334000.pru0: rproc_boot failed
[   21.970925]  remoteproc1: failed to load am335x-pru1-fw
[   21.984090]  remoteproc1: request_firmware failed: -2
[   21.989339] pru-rproc 4a338000.pru1: rproc_boot 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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAF%2BMRtnp_QBFPY%3DoeVkDhH%3DJgWVY8pDfk_yJYPgX-R_At8vR7Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Fast Pin Toggling Using MMAP

[Micka]

use the PRU it's faster ^^

Le jeu. 28 avr. 2016 à 17:55, William Hermans  a écrit :

> *1) I could not find START_ADDR, END_ADDR, OE, SETDATAOUT, CLEARDATAOUT
>> from technical manual. Where can I find them for the pins from P9_11 ...
>> upto P9_18*
>>
>
> Setdataout, and cleardataout are in the TRM. Pages 4093-4094.
>
> *2) what is the explanation of the following statement? What does it do?*
>>
>> *define PIN ( 1<<28) *
>>
>
>
>
> *If you do not know what this does, then you need to read, and understand
> how bit manipulation works in C. This specifically is what is known as a
> bit shift.*
>
>> *3) **I am going to use it for SPI communication, so since the timing is
>> critical, and Linux is not RT, there is a possibility that some other
>> interrupts may damage my communaction. Do you think that it would be a
>> problem? If yes, what precautions can I get?*
>>
>
> Bad idea. You have SPI modules on the board already. Why would you not use
> them ? Also, if you know Linux is not real time( enough ) then why would
> you use Linux ?
>
> On Thu, Apr 28, 2016 at 8:02 AM, TJF  wrote:
>
>> Hi Frank!
>>
>> Your example controls one GPIO subsystem. The pins P9_11 to P9_18 are
>> connected to two GPIO subsystems. That's why you cannot control all pins at
>> 2.6 MHz. You'll have to find a set of pins connected to a single GPIO
>> subsystem (either GPIO0 or GPIO1).
>>
>> As John mentioned, this is stuff for the PRUSS.
>>
>> BR
>>
>> --
>> 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.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/beagleboard/4fa09157-deff-49cf-b899-ed775ed2562b%40googlegroups.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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/CALHSORojmnsJo31UbR7C7RnaoCrGKFGP3a9R%3DKBd1Cy5s6J_iQ%40mail.gmail.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAF%2BMRtmZ6HpMJ1Sf%2Bgug6uOddb%2BdbwCemnkJaNHHpoggcTFjVA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: RS485 support for BBB

[Micka]

Or you go on the driver omap which work very well !

Micka,

Le mer. 27 avr. 2016 à 09:05, William Hermans <yyrk...@gmail.com> a écrit :

> Seems to me, the answer is: Not until you write your own driver.
>
> On Tue, Apr 26, 2016 at 11:13 PM, 'Artur Festyn' via BeagleBoard <
> beagleboard@googlegroups.com> wrote:
>
>> So the answer is: not now, but soon?
>>
>>
>> 2016-04-27 3:07 GMT+01:00 Robert Nelson <robertcnel...@gmail.com>:
>>
>>>
>>>
>>> On Tue, Apr 26, 2016 at 8:52 PM, Peter Hurley <pe...@hurleysoftware.com>
>>> wrote:
>>>
>>>> On 04/26/2016 06:26 PM, Robert Nelson wrote:
>>>>
>>>> On Tue, Apr 26, 2016 at 8:18 PM, Peter Hurley <pe...@hurleysoftware.com
>>>> > wrote:
>>>>
>>>>> On 04/25/2016 10:54 PM, Micka wrote:
>>>>> > I repeat only omap driver work for rs485
>>>>>
>>>>> RS485 support was added to the 8250 driver for 4.6
>>>>>
>>>>
>>>> and i've been evil, syncing's
>>>>
>>>> /drivers/tty/serial/8250/
>>>> and parts of:
>>>> /drivers/tty/serial/
>>>> from mainline, back to our v4.4.x-ti & v4.5.x-bone kernel's. ;)
>>>>
>>>>
>>>> Ah, ok, good to know.
>>>>
>>>> It does not support gpio RTS.
>>>>> Some preliminary patches for gpio RTS support have been
>>>>> submitted by not accepted.
>>>>
>>>>
>>>> I've been following that and including those too..  We did have one
>>>> user who was successful, haven't heard much from him since he submitted the
>>>> working overlay..  (so i'm assuming it's still working. ;) )
>>>>
>>>>
>>>> Ok, but you should know there's zero chance of that last patch going
>>>> into mainline in its current form because it breaks console on everything
>>>> else.
>>>>
>>>
>>> Okay thanks!  I'll revert that last one and keep watching the serial
>>> mainline list for updates..
>>>
>>> Regards,
>>>
>>> --
>>> Robert Nelson
>>> https://rcn-ee.com/
>>>
>>> --
>>> For more options, visit http://beagleboard.org/discuss
>>> ---
>>> You received this message because you are subscribed to a topic in the
>>> Google Groups "BeagleBoard" group.
>>> To unsubscribe from this topic, visit
>>> https://groups.google.com/d/topic/beagleboard/nMtRpdWSJu0/unsubscribe.
>>> To unsubscribe from this group and all its topics, send an email to
>>> beagleboard+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/beagleboard/CAOCHtYh6Ox9-_kMwbQm2t05SKzWFQXQTp14Z1enRE9h8Mw0PtA%40mail.gmail.com
>>> <https://groups.google.com/d/msgid/beagleboard/CAOCHtYh6Ox9-_kMwbQm2t05SKzWFQXQTp14Z1enRE9h8Mw0PtA%40mail.gmail.com?utm_medium=email_source=footer>
>>> .
>>>
>>> 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.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/beagleboard/CAAPjYCYxfmuPpG6-y1BQ%2BdXUtxc_72n7AWmh1KMA5PP%2Bq_9igg%40mail.gmail.com
>> <https://groups.google.com/d/msgid/beagleboard/CAAPjYCYxfmuPpG6-y1BQ%2BdXUtxc_72n7AWmh1KMA5PP%2Bq_9igg%40mail.gmail.com?utm_medium=email_source=footer>
>> .
>>
>> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/CALHSORq%3D5cgOsAy7mPxZU4JjE7gQQLiphktQTWRNVUHSnO3y7g%40mail.gmail.com
> <https://groups.google.com/d/msgid/beagleboard/CALHSORq%3D5cgOsAy7mPxZU4JjE7gQQLiphktQTWRNVUHSnO3y7g%40mail.gmail.com?utm_medium=email_source=footer>
> .
> 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAF%2BMRtme3T29Ny2ZuRyZ30EiR20KpNTMpMGgg6ZOCfK-Hns3MQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] toolchain : bone-debian-7.8-lxde-4gb-armhf-2015-03-01-4gb.img

[Micka]

Hi,

I can't compile on the beaglebone black because there is too much source to
compile. On a VM, the cross compile goes very fast !

I've tried to cross compile with ubuntu 12.4.5 , but it looks like that I
don't have the same lib on ubuntu :

beagle :
ldd --version /lib/arm-linux-gnueabihf/libgcc_s.so.1
ldd (Debian EGLIBC 2.13-38+deb7u10) 2.13

ubuntu:
ldd --version /usr/arm-linux-gnueabihf/lib/libgcc_s.so.1
ldd (Ubuntu EGLIBC 2.15-0ubuntu10.13) 2.15

I've to try and find the correct toolchain (_(

any idea ? can I copy all file in the beagle and copy in the ubuntu folder.
beagle  /lib/arm-linux-gnueabihf to ubuntu /usr/arm-linux-gnueabihf/lib/

??
Le mer. 20 avr. 2016 à 10:24, William Hermans <yyrk...@gmail.com> a écrit :

> *I agree with you, I'm also on the kernel 4.1.20.*
>>
>> *But for cross compilation I have an issue, and I need to find the
>> correct toolchain.*
>>
>> *That why I'm going to try Jessy, I hope that I will find easily the
>> toolchain on the linaro webpage.*
>>
>
> If you can manage to install Ubuntu 14.04 on something, that's a real
> solution. Or better yet you can Install Lubuntu 14.04( based on LXDE
> instead of unity ), which is much faster. Since it uses LXDE instead of
> Unity. It'll even run fast in a VM, if thats how you want to run it.
>
> *Or* you can just do all your compiling natively on the Beaglebone, like I
> do. I used an NFS share + a ramdisk to keep from compiling on the eMMC or
> an sdcard.
>
> Anyway, it's getting late( early ) here so I probably wont respond to any
> more posts for ~8 hours . . .time to sleep. But I'll be willing to discuss
> options with you if you want to stay with a 4.6.3 gcc. After i wake up.
>
> On Wed, Apr 20, 2016 at 1:16 AM, Micka <mickamus...@gmail.com> wrote:
>
>> I agree with you, I'm also on the kernel 4.1.20.
>>
>> But for cross compilation I have an issue, and I need to find the correct
>> toolchain.
>>
>> That why I'm going to try Jessy, I hope that I will find easily the
>> toolchain on the linaro webpage.
>>
>>
>>
>> Micka,
>>
>> Le mer. 20 avr. 2016 à 10:08, William Hermans <yyrk...@gmail.com> a
>> écrit :
>>
>>> Personally, I do not think it matters much which rootfs you run, Jessie
>>> or wheezy. This is just a matter of  taste. The important part, at least in
>>> my mind, is using a 4.1.x kernel.
>>>
>>> On Wed, Apr 20, 2016 at 1:07 AM, William Hermans <yyrk...@gmail.com>
>>> wrote:
>>>
>>>> william@beaglebone:~$ cat /etc/dogtag
>>>> BeagleBoard.org Debian Image 2015-03-01
>>>> william@beaglebone:~$ uname -r
>>>> 4.1.14-bone-rt-r17
>>>>
>>>> I'm avoiding Jessie like a plague, for now. Also avoiding systemd.
>>>> Although the documentation for systemd has much improved over the last year
>>>> or so. But I'm still not interested. Yet.
>>>>
>>>> On Wed, Apr 20, 2016 at 1:04 AM, Micka <mickamus...@gmail.com> wrote:
>>>>
>>>>> Ok, which version of Debian are you using ?
>>>>>
>>>>> I'm going to switch to this one :
>>>>>
>>>>>
>>>>> https://rcn-ee.com/rootfs/bb.org/testing/2016-04-10/lxqt-4gb/bone-debian-8.4-lxqt-4gb-armhf-2016-04-10-4gb.img.xz
>>>>>
>>>>>
>>>>> Micka,
>>>>>
>>>>> Le mer. 20 avr. 2016 à 10:02, William Hermans <yyrk...@gmail.com> a
>>>>> écrit :
>>>>>
>>>>>> That is I could not find a binary for Linaros 4.6.3 gcc toolchain.
>>>>>>
>>>>>> On Wed, Apr 20, 2016 at 1:00 AM, William Hermans <yyrk...@gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>>> You need to define what you mean by "toolchain". Because sudo
>>>>>>> apt-get install gcc gets you a toolchain on the beaglebone.
>>>>>>>
>>>>>>> Now if you mean a cross compiler toolchain. For 4.6* as far as I can
>>>>>>> tell you have two options.
>>>>>>>
>>>>>>>
>>>>>>>- You can download the source tarball, and use crosstool-NG
>>>>>>>- You can download, install, and run Ubuntu 14.04, and use their
>>>>>>>apt repo to install a 4.6.3 armhf cross toolchain.
>>>>>>>
>>>>>>> It does not seem as though the binaries are available from anywhere
>>>>>>> any more, but I did not have an exact file name t

Re: [beagleboard] Re: RS485 support for BBB

[Micka]

I dont know about 8250, but omap work well. I'm more confident about omap
handling the gpio than the driver 8250.

I've been using omap for rs485 since the driver 3.8 and I've nothing to
complain about.

I will also switch to the driver 8250 when it will be ready ( a lot of test
need to be done )


Micka,



Le mar. 26 avr. 2016 08:05, 'Artur Festyn' via BeagleBoard <
beagleboard@googlegroups.com> a écrit :

> Hi Micka.
> no ttyO, its 8250 driver.
> shouldn't 4.5 kernel work after these patches are applied or is it still
> too early?
>
> -rw-r--r--  1 root root 1440 Apr 21 12:26
> 0001-tty-serial-8250-fix-RS485-half-duplex-RX.patch
> -rw-r--r--  1 root root 8243 Apr 21 12:26
> 0002-tty-serial-8250-make-UART_MCR-register-access-consis.patch
> -rw-r--r--  1 root root 2743 Apr 21 12:26
> 0003-serial-mctrl_gpio-add-modem-control-read-routine.patch
> -rw-r--r--  1 root root 1347 Apr 21 12:26
> 0004-serial-mctrl_gpio-add-IRQ-locking.patch
> -rw-r--r--  1 root root 7924 Apr 21 12:26
> 0005-tty-serial-8250-use-mctrl_gpio-helpers.patch
>
> the last one clearly states that use of any gpio as rts should be possible
>
>
> 2016-04-26 6:54 GMT+01:00 Micka <mickamus...@gmail.com>:
>
>> Can you show me what this command show :
>>
>> dmesg|grep ttyO*
>>
>> I repeat only omap driver work for rs485
>>
>> Le mar. 26 avr. 2016 00:40, 'Artur Festyn' via BeagleBoard <
>> beagleboard@googlegroups.com> a écrit :
>>
>>> It is easy and already disabled.
>>> My question is about RS485 and custom gpio to drive DE pin of RS485 chip.
>>>
>>>
>>> 2016-04-25 23:22 GMT+01:00 evilwulfie <evilwul...@gmail.com>:
>>>
>>>> read this. disabling I2C2 is not as easy as using an overlay
>>>> if you are not using capes sure but IMHO is always best to leave the
>>>> default things enabled and just work with overlays
>>>>
>>>>
>>>> http://www.embedded-things.com/bbb/enable-canbus-on-the-beaglebone-black/
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> On 4/25/2016 2:09 PM, 'Artur Festyn' via BeagleBoard wrote:
>>>>
>>>> Honestly I don't know. I though this might be useful info :)
>>>> Three is no problem to disable I2C-2, but I am using those pins for
>>>> CAN0.
>>>> That is why I want to use custom gpio to drive RS485 DE which doesn't
>>>> work.
>>>>
>>>> 2016-04-25 21:56 GMT+01:00 William Hermans <yyrk...@gmail.com>:
>>>>
>>>>> *cat /proc/tty/driver/serial*
>>>>>
>>>>> *serinfo:1.0 driver revision:*
>>>>> *0: uart:8250 mmio:0x44E09000 irq:158 tx:2451 rx:0 RTS|CTS|DTR|DSR*
>>>>> *1: uart:8250 mmio:0x48022000 irq:159 tx:24 rx:0 CTS|DSR|CD|RI*
>>>>> *2: uart:8250 mmio:0x48024000 irq:160 tx:0 rx:0 CTS|DSR*
>>>>> *3: uart:unknown port: irq:0*
>>>>> *4: uart:8250 mmio:0x481A8000 irq:161 tx:2 rx:1 brk:1 CTS|DSR*
>>>>>
>>>>> *5: uart:unknown port: irq:0*
>>>>>
>>>>> What is this supposed to mean ? That says UART0 has RTS, CTS, etc, but
>>>>> they're not connected to anything. So the CTS on UART1 means nothing.
>>>>> Because it's connected to I2C-2, which I'm sure you would have all kinds 
>>>>> of
>>>>> fun disabling I2C-2 . . .
>>>>>
>>>>>
>>>>> On Mon, Apr 25, 2016 at 1:14 PM, 'Artur Festyn' via BeagleBoard <
>>>>> <beagleboard@googlegroups.com>beagleboard@googlegroups.com> wrote:
>>>>>
>>>>>> cat /proc/tty/driver/serial
>>>>>> serinfo:1.0 driver revision:
>>>>>> 0: uart:8250 mmio:0x44E09000 irq:158 tx:2451 rx:0 RTS|CTS|DTR|DSR
>>>>>> *1: uart:8250 mmio:0x48022000 irq:159 tx:24 rx:0 CTS|DSR|CD|RI*
>>>>>> 2: uart:8250 mmio:0x48024000 irq:160 tx:0 rx:0 CTS|DSR
>>>>>> 3: uart:unknown port: irq:0
>>>>>> 4: uart:8250 mmio:0x481A8000 irq:161 tx:2 rx:1 brk:1 CTS|DSR
>>>>>> 5: uart:unknown port: irq:0
>>>>>>
>>>>>>
>>>>>> 2016-04-25 21:12 GMT+01:00 Artur Festyn < <fes...@googlemail.com>
>>>>>> fes...@googlemail.com>:
>>>>>>
>>>>>>> I can't use RTS/CTS pins on UART4 because I need HDMI.
>>>>>>> New RS485 patches suppose to help to use any gpio as RS485 RTS and
>>>>>>> in fact 

Re: [beagleboard] Re: RS485 support for BBB

[Micka]

Can you show me what this command show :

dmesg|grep ttyO*

I repeat only omap driver work for rs485

Le mar. 26 avr. 2016 00:40, 'Artur Festyn' via BeagleBoard <
beagleboard@googlegroups.com> a écrit :

> It is easy and already disabled.
> My question is about RS485 and custom gpio to drive DE pin of RS485 chip.
>
>
> 2016-04-25 23:22 GMT+01:00 evilwulfie :
>
>> read this. disabling I2C2 is not as easy as using an overlay
>> if you are not using capes sure but IMHO is always best to leave the
>> default things enabled and just work with overlays
>>
>> http://www.embedded-things.com/bbb/enable-canbus-on-the-beaglebone-black/
>>
>>
>>
>>
>>
>> On 4/25/2016 2:09 PM, 'Artur Festyn' via BeagleBoard wrote:
>>
>> Honestly I don't know. I though this might be useful info :)
>> Three is no problem to disable I2C-2, but I am using those pins for CAN0.
>> That is why I want to use custom gpio to drive RS485 DE which doesn't
>> work.
>>
>> 2016-04-25 21:56 GMT+01:00 William Hermans :
>>
>>> *cat /proc/tty/driver/serial*
>>>
>>> *serinfo:1.0 driver revision:*
>>> *0: uart:8250 mmio:0x44E09000 irq:158 tx:2451 rx:0 RTS|CTS|DTR|DSR*
>>> *1: uart:8250 mmio:0x48022000 irq:159 tx:24 rx:0 CTS|DSR|CD|RI*
>>> *2: uart:8250 mmio:0x48024000 irq:160 tx:0 rx:0 CTS|DSR*
>>> *3: uart:unknown port: irq:0*
>>> *4: uart:8250 mmio:0x481A8000 irq:161 tx:2 rx:1 brk:1 CTS|DSR*
>>>
>>> *5: uart:unknown port: irq:0*
>>>
>>> What is this supposed to mean ? That says UART0 has RTS, CTS, etc, but
>>> they're not connected to anything. So the CTS on UART1 means nothing.
>>> Because it's connected to I2C-2, which I'm sure you would have all kinds of
>>> fun disabling I2C-2 . . .
>>>
>>>
>>> On Mon, Apr 25, 2016 at 1:14 PM, 'Artur Festyn' via BeagleBoard <
>>> beagleboard@googlegroups.com> wrote:
>>>
 cat /proc/tty/driver/serial
 serinfo:1.0 driver revision:
 0: uart:8250 mmio:0x44E09000 irq:158 tx:2451 rx:0 RTS|CTS|DTR|DSR
 *1: uart:8250 mmio:0x48022000 irq:159 tx:24 rx:0 CTS|DSR|CD|RI*
 2: uart:8250 mmio:0x48024000 irq:160 tx:0 rx:0 CTS|DSR
 3: uart:unknown port: irq:0
 4: uart:8250 mmio:0x481A8000 irq:161 tx:2 rx:1 brk:1 CTS|DSR
 5: uart:unknown port: irq:0


 2016-04-25 21:12 GMT+01:00 Artur Festyn < 
 fes...@googlemail.com>:

> I can't use RTS/CTS pins on UART4 because I need HDMI.
> New RS485 patches suppose to help to use any gpio as RS485 RTS and in
> fact any gpio for any UART as RTS/CTS.
>
>
>
>
> 2016-04-25 21:00 GMT+01:00 evilwulfie < 
> evilwul...@gmail.com>:
>
>> any reason you want to use uart1 ?
>>
>> if you use uart4 you can use the whole uart tx rx and rts. trying to
>> bitbang rts for rs485 on uart1 sounds hard
>>
>>
>>
>> On 4/25/2016 12:24 PM, 'Jan Kinkazu' via BeagleBoard wrote:
>>
>> So i compiled (bb-kernel, all patches) and installed 4.5.2-bone4
>> I have modified am335-boneblack.dts and compiled it.
>>
>> #include "am335x-peripheral-ttyS1.dtsi"
>> #include "am335x-bone-pinmux-ttyS1.dtsi"
>>
>> _pinmux {
>> uart1_pins: pinmux_uart1_pins {
>> pinctrl-single,pins = <
>> /* P9_23: uart1_de */
>> BONE_P9_23 (PIN_OUTPUT_PULLDOWN | MUX_MODE7)
>> >;
>> };
>> };
>>
>>  {
>> pinctrl-names = "default";
>> pinctrl-0 = <_pins>;
>> status = "okay";
>> rts-gpios = < 17 GPIO_ACTIVE_HIGH>;
>> rs485-rts-active-high;
>> rs485-rx-during-tx;
>> rs485-rts-delay = <1 1>;
>> linux,rs485-enabled-at-boot-time;
>> };
>>
>> RS485 doesn't work, what do I do wrong?
>>
>> Kind regards
>>
>>
>> On Friday, 12 February 2016 15:33:40 UTC, Taceant Omnes wrote:
>>>
>>> I would like to use RS485 with the BBB.
>>>
>>> root@beaglebone:~/test# uname -a
>>> Linux beaglebone 4.1.15-ti-r40 #1 SMP PREEMPT Thu Jan 7 23:32:17 UTC
>>> 2016 armv7l GNU/Linux
>>>
>>> I am using the kernel above. Its source code is at
>>>
>>> 
>>> https://github.com/RobertCNelson/linux-stable-rcn-ee/tree/4.1.15-ti-rt-r40
>>>
>>> ... however it does not include the changes in this patch:
>>>
>>> 
>>> https://github.com/RobertCNelson/bb-kernel/blob/am33x-v3.8/patches/fixes/0007-omap-RS485-support-by-Michael-Musset.patch#L30
>>>
>>> Which kernel should I use that includes the changes in the patch or
>>> something similar?
>>>
>> --
>> For more options,