I wish knw if there are someone working with the Octoprint on that board.
I could not find anywhere any topic/community on that matter.
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups
"BeagleBoard" group.
To
Hi everyone,
I tried to run a lcd-display ST7066 (probably similar to the hd44870) with
the folowing code:
import Adafruit_BBIO.GPIO as GPIO
import time
# Define GPIO to LCD mapping
LCD_RS="P9_15"
LCD_E="P9_16
On Tuesday, July 5, 2016 at 10:03:07 AM UTC-7, yyr...@gmail.com wrote:
>
> SYS_RESETIN Does not seem to function as I would expect it to. I would
> expect that toggling this pin would somehow cause a system reset. It does
> not. Can anyone shed any light on the functionality of this pin ? I do
I guess to answer my own question:
https://groups.google.com/forum/#!topic/beagleboard/ogyyRufIVVs The
post by David
Belohrad is very descriptive. Especially the part where grounding PWR_BTN
will completely turn off the PMIC. Which a lot of people seem to be having
issues with completely turning of
@Gerald
So hey where can I find good official documentation on SYS_RESETIN ? I've
poured over the SRM, and the TRM, and have not really found any clear
documentation on the subject matter. Also, what little the documentation
does mention anything, names are confused between SYS_RESET, SYS_RESETIN,
Schematic
On Jul 5, 2016 1:29 PM, "William Hermans" wrote:
> @Gerald
>
> So hey where can I find good official documentation on SYS_RESETIN ? I've
> poured over the SRM, and the TRM, and have not really found any clear
> documentation on the subject matter. Also, what little the documentation
> d
Schematic may tell me that it is connected to the PMIC through a buffer, a
button, and back out to another part I do not recognize offhand. But a
schematic does not tell me how this pin is used, or processed within the
OS. There is a lot of conflicting information out there so it is hard to
get a "
a patch in the post form 2013 I found may lead to some pertinent
information. But much has changed in the kernel since then . . .
On Tue, Jul 5, 2016 at 11:40 AM, William Hermans wrote:
> Schematic may tell me that it is connected to the PMIC through a buffer, a
> button, and back out to another
In the AM3358 TRM. It is an interrupt input to the processor. The SW can
cleanup before making it an output to reset the board. So, if the SW does
not handle it, it does not reset anything.
Gerald
On Tue, Jul 5, 2016 at 1:29 PM, William Hermans wrote:
> @Gerald
>
> So hey where can I find good
On 7/5/2016 1:29 PM, William Hermans wrote:
> @Gerald
>
> So hey where can I find good official documentation on SYS_RESETIN ? I've
> poured
> over the SRM, and the TRM, and have not really found any clear documentation
> on
> the subject matter. Also, what little the documentation does mentio
>
> *In the AM3358 TRM. It is an interrupt input to the processor. The SW can
> cleanup before making it an output to reset the board. So, if the SW does
> not handle it, it does not reset anything.*
>
> *Gerald*
>
Thanks Gerald.
I kind of figured already that about the software aspect. I'm toggl
AM335x is the TRM name. But I was afraid I would get jumped because that is
not the processor used, instead it is the AM3358.
Look up AM3358 and select the TRM listed on that page.
Gerald
On Tue, Jul 5, 2016 at 2:23 PM, William Hermans wrote:
> *In the AM3358 TRM. It is an interrupt input to
> *Section 8.1.7 of the TRM "Reset Management", with some additional*
> * details in the data sheet (sprs717). It can be confusing, since the*
> * physical reset pin (nRESETIN_OUT) is both an input and an output, but*
> * the individual RESET_IN and RESET_OUT signals are "broken out" on-chip*
> *
>
> AM335x is the TRM name. But I was afraid I would get jumped because that
> is not the processor used, instead it is the AM3358.
>
> Look up AM3358 and select the TRM listed on that page.
>
> Gerald
I don't think anyone would get on your case over saying "AM335X". But I was
starting to wonder
>
> *My next step was actually to watch /proc/interrupts, which actually I
> think I'm still going to do. In order to see if there are in fact any
> interrupts happening from all this pin toggling im doing.*
>
No dice. But before I give up I'm going to switch form a TI kernel to a
bone kernel and
The OctoPrint Wiki has an article on how to use it, the Replicape project using
some OctoPrint on a BBB.
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups
"BeagleBoard" group.
To unsubscribe from this group a
On Mon, Jul 4, 2016 at 9:14 PM, 'Morgaine' via BeagleBoard
wrote:
> John Syne writes:
>>
>> > a power supply that is spec’d at 4A should not shutdown when it sees a
>> > 4A load, but rather, it should current limit at 4A. If the power supply is
>> > spec’d at 4A, then 4A should not be treated as a
Thanks Brian,
Your post helped me. :)
On Monday, February 16, 2015 at 7:44:33 PM UTC-8, Brian Anderson wrote:
>
> Enric,
>
> I think your problem may be related to ConnMan. ConnMan is a network
> manager that is installed on the Jessie test images. It manages your
> network connections, includ
On Tue, 5 Jul 2016 16:00:05 -0400, you wrote:
>On Mon, Jul 4, 2016 at 9:14 PM, 'Morgaine' via BeagleBoard
> wrote:
>> John Syne writes:
>>>
>>> > a power supply that is spec’d at 4A should not shutdown when it sees a
>>> > 4A load, but rather, it should current limit at 4A. If the power supply is
You know that you are nit picking right now. The requirements are clear, 5V2A.
Test any of these supplies, and see what happens to the supply when you try to
take 3A, it won’t and it will current limit at close to 2A. For UL
requirements, they all have short circuit protection, which is a safety
20 matches
Mail list logo
