[beagleboard] Really slow Command Execution I2C .NET

[Manuel Gass]

Hello BeagleBone Community,
I am currently taking a somewhat unconventional approach to Beagelbone 
programming.
But now I have a problem for which I can not find a solution.
I have a problem with the speed of the processing of two I2C commands.
The bus is operated with 100kHZ and this speed was also measured with an 
oscilloscope.
But between the processing of two I2C commands is now a time of 13ms, with 
which I unfortunately can not work.

I link you below a picture with my Github-issue, maybe someone here has an 
idea if this behavior is normal or how I can fix this problem.
I would be grateful for any help.


-- 
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/fb6abb43-16f7-4f02-a9a6-11afcc2f3eddn%40googlegroups.com.

Re: [beagleboard] Re: problems compiling an out of tree driver for a xM on kernel 5.4.24

[Michael McCann]

Hi Jake,

Yes, I did find a solution! Using the cross development tools downloaded by
Nelson's script makes things work correctly. This the script I'm using to
build drivers:

CROSS_COMPILE_PATH=/usr1/github.com.RoberCNelson.arm7-multiplatform/armv7-multiplatform/dl/gcc-arm-8.3-2019.03-x86_64-arm-linux-gnueabihf/bin/arm-linux-gnueabihf-
make -C $KERNEL_ROOT M=$(pwd) ARCH=arm CROSS_COMPILE=$CROSS_COMPILE_PATH

Mike

On Fri, Mar 5, 2021 at 9:11 AM Jake  wrote:

> Hi! I'm having the same error when trying to compile a out of tree driver.
> Have you found the solution?
> I'm also using the kernel from RobertCNelson/armv7-multiplatform.
> Thanks!
>
> On Saturday, February 6, 2021 at 8:50:47 AM UTC-7, kb2...@gmail.com wrote:
>>
>> Has anyone else seen this error message when compiling an out of tree
>> module?
>>
>> make: Entering directory '/usr1/github.com
>> .RoberCNelson.arm7-multiplatform/armv7-multiplatform/KERNEL'
>>   AR  /usr1/BeagleXmDrivers/built-in.a
>>   CC [M]  /usr1/BeagleXmDrivers/hello.o
>> cc1: error: cannot load plugin
>> ./scripts/gcc-plugins/arm_ssp_per_task_plugin.so
>>./scripts/gcc-plugins/arm_ssp_per_task_plugin.so: undefined symbol:
>> _Z9rtx_alloc8rtx_code
>> make[1]: *** [scripts/Makefile.build:266: /usr1/BeagleXmDrivers/hello.o]
>> Error 1
>> make: *** [Makefile:1690: /usr1/BeagleXmDrivers] Error 2
>> make: Leaving directory '/usr1/github.com
>> .RoberCNelson.arm7-multiplatform/armv7-multiplatform/KERNEL'
>> t
>>
>> Mike
>>
> --
> 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/2678cbb0-2650-43b2-8055-6c98a4f81f6fo%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/CACmz4mByYxr-oG%2BeLeWbT4BBZ8FnZip11gL_h2rUCoDtDNMkCQ%40mail.gmail.com.

Re: [beagleboard] Re: GPIO, libpruio & dtbo Question

[Don Pancoe]

I don't mean to start a fight here. You are all providing helpful
information. I think I will proceed on one of the following paths.

   1. Dig in and understand the GPIO registers. I have seen those in the
   libpruio docs, but just haven't groked them yet.
   2. Failing that, I can use libpruio to read the button during the
   *customSleep()* function, where it will both call a *break* right there
   as well as set an *abort* flag to notify any subsequent tests that they
   should also not execute.
   3. And lastly, really dive into the device tree more long-term per
   Seth's info, because I think that would be useful knowledge for future
   projects.

Thanks,
Don

--
Don Pancoe, P.E.
Industrial Designer, Electrical Engineer
DonPancoe.com 


On Fri, Mar 5, 2021 at 3:48 AM TJF  wrote:

>
> Dennis Bieber schrieb am Donnerstag, 4. März 2021 um 23:41:22 UTC+1:
>
>> libpruio
>> does not seem to support such -- cf:
>> https://groups.google.com/g/beagleboard/c/3wphAPs9Uws (which is the
>> underlying C level, I doubt the Python interface adds any features)
>>
> Nonsens! Use
>
> io.IntcInit
>
> to configure the interrupt table (IRQ[0-4,6,7]). And mask your event in
> the GPIO registers
>
> LEVELDETECT[0,1]
> RISINGDETECT
> FALLINGDETECT
>
> If need be also set the GPIO registers
>
> DEBOUNCENABLE
> DEBOUNCINGTIME
>
> and then catch (and reset) the new IRQ in a thread. But this isn't worth
> the effort!
>
> As mentioned above, the while loop should get placed in a custom sleep
> function. And since the app does nothing in that sleep function, the
> abortPIN can get polled fast enough (20 to 100 Hz).
>
> Dennis Bieber schrieb am Donnerstag, 4. März 2021 um 23:41:22 UTC+1:
>
>> Non Sequitur: "TJF" is, as I recall, the author of that libpruio package,
>> and pushes it as the only solution for everything related to Beaglebone
>> GPIO.
>>
> Nonsens! You can find hundreds of threads here without any pushing. Since
> the OP already implemented libpruio for the eCAP feature, why shouldn't he
> use further features?
>
>
> --
> 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/bd3d4e00-58e8-4e6d-86df-004e5305b0a2n%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/CAP3tSUPDKm2gnhiTH0d5PuutpRBa1TaHhjMQNBJ5-q83GJ6V4A%40mail.gmail.com.

[beagleboard] Re: problems compiling an out of tree driver for a xM on kernel 5.4.24

[Jake]

Hi! I'm having the same error when trying to compile a out of tree driver.
Have you found the solution? 
I'm also using the kernel from RobertCNelson/armv7-multiplatform. 
Thanks!

On Saturday, February 6, 2021 at 8:50:47 AM UTC-7, kb2...@gmail.com wrote:
>
> Has anyone else seen this error message when compiling an out of tree 
> module?
>
> make: Entering directory 
> '/usr1/github.com.RoberCNelson.arm7-multiplatform/armv7-multiplatform/KERNEL'
>   AR  /usr1/BeagleXmDrivers/built-in.a
>   CC [M]  /usr1/BeagleXmDrivers/hello.o
> cc1: error: cannot load plugin 
> ./scripts/gcc-plugins/arm_ssp_per_task_plugin.so
>./scripts/gcc-plugins/arm_ssp_per_task_plugin.so: undefined symbol: 
> _Z9rtx_alloc8rtx_code
> make[1]: *** [scripts/Makefile.build:266: /usr1/BeagleXmDrivers/hello.o] 
> Error 1
> make: *** [Makefile:1690: /usr1/BeagleXmDrivers] Error 2
> make: Leaving directory 
> '/usr1/github.com.RoberCNelson.arm7-multiplatform/armv7-multiplatform/KERNEL'
> t
>
> Mike
>

-- 
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/2678cbb0-2650-43b2-8055-6c98a4f81f6fo%40googlegroups.com.

[beagleboard] BBB Setting up the Interrupt Vector Table

[Josh Cole]

Hi everyone,

I'm working on a low-level kernel for the Beaglebone Black. I've gotten to 
a point in my project where I want to specify an IRQ handler and enable 
interrupts.

According to the technical reference manual 
(section 
26.1.4), there are two primary locations you can load a disk image to. The 
first is what they call "Public ROM" which seems pretty straightforward. 
You load your image to address 0x2 and the interrupt vector table is 
the first thing which gets encountered.

The second location you can load an image is "Public RAM" (which I'm 
using). This starts executing at 0x402F0400 and you get 109kb of space for 
your application. The weird part is, *the interrupt vector table appears to 
be located super far away from the entrypoint*, at location 0x4030CE00. 
This is more than 109kb away, so it can't be included in the image which 
gets flashed to the device.

I am at a loss about how to get an instruction to that particular location 
in memory since my image fundamentally can't be that size. Any guidance on 
how to setup the IVT for Public RAM would be greatly appreciated.

Thank you for your time!

-- 
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/22478461-4689-43f1-baf5-fa28f531dec5n%40googlegroups.com.

Re: [beagleboard] Re: BeagleBone Black QNX 6.5.0 SP1

[Lucas SOLDA]

I don't know how to change Mode of the GPIO. Still searching lol


Le vendredi 5 mars 2021 à 14:28:08 UTC+1, Lucas SOLDA a écrit :

> Thank you, now I can add files ! 
>
> Now I try to make GPIO work
>
> Le vendredi 5 mars 2021 à 14:07:37 UTC+1, robert.sty...@gmail.com a 
> écrit :
>
>> Add a partition or another storage device. To mount once booted.
>>
>> Add a partition to your storage, 
>> so that you have a smallish boot image partition which will be read-only 
>> and a data partition which is read/write.
>>
>> Add another storage device,
>> so that you have read/write storage which is not just volatile RAM-disk. 
>> I think we used FTP or IDE to copy files to the R/W storage and add to the 
>> PATH.
>>
>>
>> On Friday, 5 March 2021 at 10:51:37 UTC lucas...@gmail.com wrote:
>>
>>> Well, we found a solution to just use the prebuilt image I attached 
>>> earlier but know it is only in read mode. I don't the username and the 
>>> password so I can't put my librairies to usr/lib...
>>> What a shame that OS
>>>
>>> Le vendredi 5 mars 2021 à 08:32:14 UTC+1, Lucas SOLDA a écrit :
>>>
 Thank you all for your answers, I will try to answer you in one post.

 *"You never told us if your product was using custom hardware or 
 incorporating the beaglebone board."*
 If I use something else than QNX, I won't be able to port all the work 
 made by my colleague. In fact, we are creating and developping our own 
 electronic cards and we use QNX to programm them. We wanted to use the 
 BeagleBone Black to realize some tests (test bench) on our products and by 
 using QNX, we just should have ported our already existing programs. I'm 
 not the person in charge of programming, builing, compiling QNX but I 
 develop the product in which our cards are installed. This is why I don't 
 understand everything about BSP, QNX, etc. 

 *"As you ask, what is missing from the BSP that needs building?" : *We 
 want to add the IsaGraf drivers in order to make the BeagleBone Black a 
 target source in which we can send programms. I think, the BSp does need 
 to 
 be modified in that case , doesn't it ?

 We cannot upgrade our QNX development system because it would be too 
 dangerous. We have only one licence and we don't want to destroy anything.
 Le vendredi 5 mars 2021 à 04:07:15 UTC+1, robert.sty...@gmail.com a 
 écrit :

> Upgrading QNX Development System.
>
> From memory, it is more involved than downloading a SP file and 
> running it. 
> You have to unzip the download.
> Find the old files.
> Copy the old files to a backup name or folder.
> Copy the new files from the zip archive, over the old files.
>
> On Friday, 5 March 2021 at 02:59:32 UTC robert.sty...@gmail.com wrote:
>
>> As you ask, what is missing from the BSP that needs building? If 
>> nothing, the next step is getting network setup to connect with SSH and 
>> IDE, possibly run network file system client to access files on your 
>> development PC.
>>
>>
>> Re: File System Image (I cannot remember all the details) 
>>
>> You use an IDE BSP project to build a bootable image including your 
>> application (started by boot script which also loads any needed drivers).
>> This bootable image can be copied to a flash drive or accessed from a 
>> network file system (during development).
>> The bootable image may be compressed read-only and expanded into a 
>> RAM backed 'disk' or expanded on the fly.
>>
>> During application development, the bootable image boots to "sh" 
>> command line. You can run any missed commands in the boot script.
>> You use the IDE to connect the debugger over ethernet to QNX process 
>> and temporary download your debug version application. The IDE debugger 
>> can 
>> run, pause, single-step, etc.
>>
>> In the BSP project you edit a configuration which controls what is 
>> included in the boot image. You add or remove files from the prebuilt 
>> folder. You edit the start up script to load and configure drivers. 
>>
>> In QNX drivers and file-systems are server processes/programs which 
>> respond to certain messages. Most QNX programs and applications are 
>> servers 
>> which wait on a message queue. 
>> QNX provides a POSIX wrapper server which converts system calls into 
>> send-wait-reply messages or convert signals into send-and-forget pulse 
>> messages. QNX also has time limited blocking on both send and receive 
>> messages.
>>
>> The QNX micro-kernel schedules process execution, allocates memory 
>> for messages, and transfers messages between processes.
>> It is supported server programs to implement the OS functions. 
>>
>> On Friday, 5 March 2021 at 00:22:31 UTC lazarman wrote:
>>
>>> The file system isn't the BSP. This part 

Re: [beagleboard] Re: BeagleBone Black QNX 6.5.0 SP1

[Lucas SOLDA]

Thank you, now I can add files ! 

Now I try to make GPIO work

Le vendredi 5 mars 2021 à 14:07:37 UTC+1, robert.sty...@gmail.com a écrit :

> Add a partition or another storage device. To mount once booted.
>
> Add a partition to your storage, 
> so that you have a smallish boot image partition which will be read-only 
> and a data partition which is read/write.
>
> Add another storage device,
> so that you have read/write storage which is not just volatile RAM-disk. I 
> think we used FTP or IDE to copy files to the R/W storage and add to the 
> PATH.
>
>
> On Friday, 5 March 2021 at 10:51:37 UTC lucas...@gmail.com wrote:
>
>> Well, we found a solution to just use the prebuilt image I attached 
>> earlier but know it is only in read mode. I don't the username and the 
>> password so I can't put my librairies to usr/lib...
>> What a shame that OS
>>
>> Le vendredi 5 mars 2021 à 08:32:14 UTC+1, Lucas SOLDA a écrit :
>>
>>> Thank you all for your answers, I will try to answer you in one post.
>>>
>>> *"You never told us if your product was using custom hardware or 
>>> incorporating the beaglebone board."*
>>> If I use something else than QNX, I won't be able to port all the work 
>>> made by my colleague. In fact, we are creating and developping our own 
>>> electronic cards and we use QNX to programm them. We wanted to use the 
>>> BeagleBone Black to realize some tests (test bench) on our products and by 
>>> using QNX, we just should have ported our already existing programs. I'm 
>>> not the person in charge of programming, builing, compiling QNX but I 
>>> develop the product in which our cards are installed. This is why I don't 
>>> understand everything about BSP, QNX, etc. 
>>>
>>> *"As you ask, what is missing from the BSP that needs building?" : *We 
>>> want to add the IsaGraf drivers in order to make the BeagleBone Black a 
>>> target source in which we can send programms. I think, the BSp does need to 
>>> be modified in that case , doesn't it ?
>>>
>>> We cannot upgrade our QNX development system because it would be too 
>>> dangerous. We have only one licence and we don't want to destroy anything.
>>> Le vendredi 5 mars 2021 à 04:07:15 UTC+1, robert.sty...@gmail.com a 
>>> écrit :
>>>
 Upgrading QNX Development System.

 From memory, it is more involved than downloading a SP file and running 
 it. 
 You have to unzip the download.
 Find the old files.
 Copy the old files to a backup name or folder.
 Copy the new files from the zip archive, over the old files.

 On Friday, 5 March 2021 at 02:59:32 UTC robert.sty...@gmail.com wrote:

> As you ask, what is missing from the BSP that needs building? If 
> nothing, the next step is getting network setup to connect with SSH and 
> IDE, possibly run network file system client to access files on your 
> development PC.
>
>
> Re: File System Image (I cannot remember all the details) 
>
> You use an IDE BSP project to build a bootable image including your 
> application (started by boot script which also loads any needed drivers).
> This bootable image can be copied to a flash drive or accessed from a 
> network file system (during development).
> The bootable image may be compressed read-only and expanded into a RAM 
> backed 'disk' or expanded on the fly.
>
> During application development, the bootable image boots to "sh" 
> command line. You can run any missed commands in the boot script.
> You use the IDE to connect the debugger over ethernet to QNX process 
> and temporary download your debug version application. The IDE debugger 
> can 
> run, pause, single-step, etc.
>
> In the BSP project you edit a configuration which controls what is 
> included in the boot image. You add or remove files from the prebuilt 
> folder. You edit the start up script to load and configure drivers. 
>
> In QNX drivers and file-systems are server processes/programs which 
> respond to certain messages. Most QNX programs and applications are 
> servers 
> which wait on a message queue. 
> QNX provides a POSIX wrapper server which converts system calls into 
> send-wait-reply messages or convert signals into send-and-forget pulse 
> messages. QNX also has time limited blocking on both send and receive 
> messages.
>
> The QNX micro-kernel schedules process execution, allocates memory for 
> messages, and transfers messages between processes.
> It is supported server programs to implement the OS functions. 
>
> On Friday, 5 March 2021 at 00:22:31 UTC lazarman wrote:
>
>> The file system isn't the BSP. This part supplies all architecture 
>> specific(ASP) functions like Cache,MMU and the board specific drivers 
>> for 
>> on chip peripherals on all cores.
>>
>> If I understand Lucas correctly and you look at the zip file he 
>> provided  

Re: [beagleboard] Re: BeagleBone Black QNX 6.5.0 SP1

[robert.sty...@gmail.com]

Add a partition or another storage device. To mount once booted.

Add a partition to your storage, 
so that you have a smallish boot image partition which will be read-only 
and a data partition which is read/write.

Add another storage device,
so that you have read/write storage which is not just volatile RAM-disk. I 
think we used FTP or IDE to copy files to the R/W storage and add to the 
PATH.


On Friday, 5 March 2021 at 10:51:37 UTC lucas...@gmail.com wrote:

> Well, we found a solution to just use the prebuilt image I attached 
> earlier but know it is only in read mode. I don't the username and the 
> password so I can't put my librairies to usr/lib...
> What a shame that OS
>
> Le vendredi 5 mars 2021 à 08:32:14 UTC+1, Lucas SOLDA a écrit :
>
>> Thank you all for your answers, I will try to answer you in one post.
>>
>> *"You never told us if your product was using custom hardware or 
>> incorporating the beaglebone board."*
>> If I use something else than QNX, I won't be able to port all the work 
>> made by my colleague. In fact, we are creating and developping our own 
>> electronic cards and we use QNX to programm them. We wanted to use the 
>> BeagleBone Black to realize some tests (test bench) on our products and by 
>> using QNX, we just should have ported our already existing programs. I'm 
>> not the person in charge of programming, builing, compiling QNX but I 
>> develop the product in which our cards are installed. This is why I don't 
>> understand everything about BSP, QNX, etc. 
>>
>> *"As you ask, what is missing from the BSP that needs building?" : *We 
>> want to add the IsaGraf drivers in order to make the BeagleBone Black a 
>> target source in which we can send programms. I think, the BSp does need to 
>> be modified in that case , doesn't it ?
>>
>> We cannot upgrade our QNX development system because it would be too 
>> dangerous. We have only one licence and we don't want to destroy anything.
>> Le vendredi 5 mars 2021 à 04:07:15 UTC+1, robert.sty...@gmail.com a 
>> écrit :
>>
>>> Upgrading QNX Development System.
>>>
>>> From memory, it is more involved than downloading a SP file and running 
>>> it. 
>>> You have to unzip the download.
>>> Find the old files.
>>> Copy the old files to a backup name or folder.
>>> Copy the new files from the zip archive, over the old files.
>>>
>>> On Friday, 5 March 2021 at 02:59:32 UTC robert.sty...@gmail.com wrote:
>>>
 As you ask, what is missing from the BSP that needs building? If 
 nothing, the next step is getting network setup to connect with SSH and 
 IDE, possibly run network file system client to access files on your 
 development PC.


 Re: File System Image (I cannot remember all the details) 

 You use an IDE BSP project to build a bootable image including your 
 application (started by boot script which also loads any needed drivers).
 This bootable image can be copied to a flash drive or accessed from a 
 network file system (during development).
 The bootable image may be compressed read-only and expanded into a RAM 
 backed 'disk' or expanded on the fly.

 During application development, the bootable image boots to "sh" 
 command line. You can run any missed commands in the boot script.
 You use the IDE to connect the debugger over ethernet to QNX process 
 and temporary download your debug version application. The IDE debugger 
 can 
 run, pause, single-step, etc.

 In the BSP project you edit a configuration which controls what is 
 included in the boot image. You add or remove files from the prebuilt 
 folder. You edit the start up script to load and configure drivers. 

 In QNX drivers and file-systems are server processes/programs which 
 respond to certain messages. Most QNX programs and applications are 
 servers 
 which wait on a message queue. 
 QNX provides a POSIX wrapper server which converts system calls into 
 send-wait-reply messages or convert signals into send-and-forget pulse 
 messages. QNX also has time limited blocking on both send and receive 
 messages.

 The QNX micro-kernel schedules process execution, allocates memory for 
 messages, and transfers messages between processes.
 It is supported server programs to implement the OS functions. 

 On Friday, 5 March 2021 at 00:22:31 UTC lazarman wrote:

> The file system isn't the BSP. This part supplies all architecture 
> specific(ASP) functions like Cache,MMU and the board specific drivers for 
> on chip peripherals on all cores.
>
> If I understand Lucas correctly and you look at the zip file he 
> provided  the support is limited as to drivers and he needs to recompile 
> that and add to it.
> That's the only reason he can't use the binary.
>
> From your response it appears you didn't need to modify this.
>
> I would guess the x15 BSP is 

Re: [beagleboard] Re: BeagleBone Black QNX 6.5.0 SP1

[Lucas SOLDA]

Well, we found a solution to just use the prebuilt image I attached earlier 
but know it is only in read mode. I don't the username and the password so 
I can't put my librairies to usr/lib...
What a shame that OS

Le vendredi 5 mars 2021 à 08:32:14 UTC+1, Lucas SOLDA a écrit :

> Thank you all for your answers, I will try to answer you in one post.
>
> *"You never told us if your product was using custom hardware or 
> incorporating the beaglebone board."*
> If I use something else than QNX, I won't be able to port all the work 
> made by my colleague. In fact, we are creating and developping our own 
> electronic cards and we use QNX to programm them. We wanted to use the 
> BeagleBone Black to realize some tests (test bench) on our products and by 
> using QNX, we just should have ported our already existing programs. I'm 
> not the person in charge of programming, builing, compiling QNX but I 
> develop the product in which our cards are installed. This is why I don't 
> understand everything about BSP, QNX, etc. 
>
> *"As you ask, what is missing from the BSP that needs building?" : *We 
> want to add the IsaGraf drivers in order to make the BeagleBone Black a 
> target source in which we can send programms. I think, the BSp does need to 
> be modified in that case , doesn't it ?
>
> We cannot upgrade our QNX development system because it would be too 
> dangerous. We have only one licence and we don't want to destroy anything.
> Le vendredi 5 mars 2021 à 04:07:15 UTC+1, robert.sty...@gmail.com a 
> écrit :
>
>> Upgrading QNX Development System.
>>
>> From memory, it is more involved than downloading a SP file and running 
>> it. 
>> You have to unzip the download.
>> Find the old files.
>> Copy the old files to a backup name or folder.
>> Copy the new files from the zip archive, over the old files.
>>
>> On Friday, 5 March 2021 at 02:59:32 UTC robert.sty...@gmail.com wrote:
>>
>>> As you ask, what is missing from the BSP that needs building? If 
>>> nothing, the next step is getting network setup to connect with SSH and 
>>> IDE, possibly run network file system client to access files on your 
>>> development PC.
>>>
>>>
>>> Re: File System Image (I cannot remember all the details) 
>>>
>>> You use an IDE BSP project to build a bootable image including your 
>>> application (started by boot script which also loads any needed drivers).
>>> This bootable image can be copied to a flash drive or accessed from a 
>>> network file system (during development).
>>> The bootable image may be compressed read-only and expanded into a RAM 
>>> backed 'disk' or expanded on the fly.
>>>
>>> During application development, the bootable image boots to "sh" command 
>>> line. You can run any missed commands in the boot script.
>>> You use the IDE to connect the debugger over ethernet to QNX process and 
>>> temporary download your debug version application. The IDE debugger can 
>>> run, pause, single-step, etc.
>>>
>>> In the BSP project you edit a configuration which controls what is 
>>> included in the boot image. You add or remove files from the prebuilt 
>>> folder. You edit the start up script to load and configure drivers. 
>>>
>>> In QNX drivers and file-systems are server processes/programs which 
>>> respond to certain messages. Most QNX programs and applications are servers 
>>> which wait on a message queue. 
>>> QNX provides a POSIX wrapper server which converts system calls into 
>>> send-wait-reply messages or convert signals into send-and-forget pulse 
>>> messages. QNX also has time limited blocking on both send and receive 
>>> messages.
>>>
>>> The QNX micro-kernel schedules process execution, allocates memory for 
>>> messages, and transfers messages between processes.
>>> It is supported server programs to implement the OS functions. 
>>>
>>> On Friday, 5 March 2021 at 00:22:31 UTC lazarman wrote:
>>>
 The file system isn't the BSP. This part supplies all architecture 
 specific(ASP) functions like Cache,MMU and the board specific drivers for 
 on chip peripherals on all cores.

 If I understand Lucas correctly and you look at the zip file he 
 provided  the support is limited as to drivers and he needs to recompile 
 that and add to it.
 That's the only reason he can't use the binary.

 From your response it appears you didn't need to modify this.

 I would guess the x15 BSP is more inclusive and mature but doubt it 
 provided loading  c6x  DSP code or Cortex M4 code but it's not relevant to 
 Lucas.

 Your experience with support below 

 <>>> answered <>>> program it for <>>> community support

 To me it sounds like Lucas has the tin can  support which is similar to 
 open source support.

 Ie post and pray

 Sent from Yahoo Mail on Android 
 

 On Thu, Mar 4, 2021 at 4:34 PM, Robert Forsyth
  wrote:

 Old product 

[beagleboard] Re: GPIO, libpruio & dtbo Question

[TJF]

Dennis Bieber schrieb am Donnerstag, 4. März 2021 um 23:41:22 UTC+1:

> libpruio 
> does not seem to support such -- cf: 
> https://groups.google.com/g/beagleboard/c/3wphAPs9Uws (which is the 
> underlying C level, I doubt the Python interface adds any features) 
>
Nonsens! Use

io.IntcInit

to configure the interrupt table (IRQ[0-4,6,7]). And mask your event in the 
GPIO registers

LEVELDETECT[0,1]
RISINGDETECT
FALLINGDETECT

If need be also set the GPIO registers

DEBOUNCENABLE
DEBOUNCINGTIME

and then catch (and reset) the new IRQ in a thread. But this isn't worth 
the effort!

As mentioned above, the while loop should get placed in a custom sleep 
function. And since the app does nothing in that sleep function, the 
abortPIN can get polled fast enough (20 to 100 Hz).

Dennis Bieber schrieb am Donnerstag, 4. März 2021 um 23:41:22 UTC+1:

> Non Sequitur: "TJF" is, as I recall, the author of that libpruio package, 
> and pushes it as the only solution for everything related to Beaglebone 
> GPIO. 
>
Nonsens! You can find hundreds of threads here without any pushing. Since 
the OP already implemented libpruio for the eCAP feature, why shouldn't he 
use further features?
 

-- 
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/bd3d4e00-58e8-4e6d-86df-004e5305b0a2n%40googlegroups.com.