Thanks Robert!!
Sorry to eat into your weekend again...
My toolchain (5.4.1-2017.01) is a little older than the one on eewiki.
Will upgrade it and retry.
Rgds, jeff
On Friday, July 21, 2017 at 8:40:53 PM UTC-5, RobertCNelson wrote:
>
> On Fri, Jul 21, 2017 at 10:56 AM, Jeff Andich > wrote:
On Fri, Jul 21, 2017 at 10:56 AM, Jeff Andich wrote:
> Don't know if this is a useful or erroneous datapoint, but I tested the
> above steps (2017.01 branch of u-boot with latest TI git tree merged in but
> patching with the older version of the 0001 bootz-n-fixes patch file),
> and my 572xEV
I think you're right John. I don't have a pulldown resistor. I forgot it...
I'll try again now and let you know the answer when I'm done. Thanks!!
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups
"BeagleBoar
I would move either D3 or D4 and place it in the spot where D2 should be.
That would allow the WiFi to work whether you're on USB, AC, or LiPo. There
are some limitations here though. If a large enough power surge occurs on
the WiFi chip then the PMIC might think there's a short circuit due to t
On Fri, Jul 21, 2017 at 6:39 PM, Sebastián Sáez wrote:
> Hi,
>
> In Debian stretch, cloud9 is no longer root
>
> Is it possible to remove root access to cloud 9 for Debian 8?
Yes, just a few changes required:
in the cloud9.service file:
Change the [Service] to have:
WorkingDirectory=/opt/cloud
Hi,
In Debian stretch, cloud9 is no longer root
Is it possible to remove root access to cloud 9 for Debian 8?
regards,
Sebastián
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups
"BeagleBoard" group.
To un
Do you have a resistor pull up or pull down on this pin? If your button pulls
the GPIO pin low, then you need a resistor pull up of at least 10K. It seems
like you don’t have this resistor connected and hence noise is triggering the
interrupt.
Regards,
John
> On Jul 21, 2017, at 3:01 PM, Wi
Hello again John. I was able to observe the error occurring and the
interruption being executed without reason. But the response from
"console.log (JSON.stringify (x));" was still the same when the interrupt
was executed correctly, ie when I pressed the button.
So, if you have any suggestions,
John, in the correct execution of the interrupt, that is, when I press a
button so that the interrupt is actually executed, the answer is this
below. I'm still waiting to know if self-interrupt will run again and then
see what new response from "console.log (JSON.stringify (x))".
Response to th
In toggleState, use console.log(JSON.stringify(x)); to see why the interrupt
triggered.
Regards,
John
> On Jul 21, 2017, at 1:52 PM, William B wrote:
>
> Hello! I'm using an interrupt with Beaglebone Black as indicated below,
> however I'm having problem.
> PROBLEM: The interrupt that goe
Hello! I'm using an interrupt with Beaglebone Black as indicated below,
however I'm having problem.
PROBLEM: The interrupt that goes through the callback function
"toggleState" is triggering itself, without any external reason or action.
Has anyone seen this happen and knows how to solve it?
Adding that I want MLO, U-Boot, and the EXT-4 all on the eMMC. Will be
using the SD card as a FAT32 for data only.
Thanks,
Kenny
On Friday, July 21, 2017 at 12:05:25 PM UTC-7, Kenny Koller wrote:
>
> Apologies. Reposting because I forgot to fill out the type/categories...
>
>
> I'm comfortable
Apologies. Reposting because I forgot to fill out the type/categories...
I'm comfortable with raw mode booting for SPL/MLO and U-Boot. I'd like to
configure U-Boot to pull the kernel and DTB from an EXT4 partition on the
eMMC.
Using strings I decoded the default state of the variables and work
I'm comfortable with raw mode booting for SPL/MLO and U-Boot. I'd like to
configure U-Boot to pull the kernel and DTB from an EXT4 partition on the
eMMC.
Using strings I decoded the default state of the variables and worked back
from $bootcmd (please see below).
Must U-Boot be built with mmcde
Hi Edgar,
I would recommend that you buy this book as it will answer most of the question
you have asked:
Mastering Embedded Linux Programming - Second Edition by Chris Simmonds
If you buy the Kindle edition, you can start reading immediately on you Tablet,
Mac, PC or Kindle device. If you sea
Hi Robert, thanks for the response and apologies for the delay getting back
to you. This has improved the screen flicker issue. On the login screen,
I'm being prompted for a password for 'Demo User' and after entering
temppwd, I am thrown back to the same login screen.
I'm not sure what I need
Don't know if this is a useful or erroneous datapoint, but I tested the
above steps (2017.01 branch of u-boot with latest TI git tree merged in but
patching with the older version of the 0001 bootz-n-fixes patch file),
and my 572xEVM appears dead...
FYI, jeff
On Friday, July 21, 2017 at
Thanks Robert!
If there's anything I can test here, let me know..
Is it maybe worthwhile to try the following or is there a mismatch between
the latest TI tree and the older version of the bootz-n-fixes patch?
1) git clone https://github.com/u-boot/u-boot
2) checkout v2017.01 -b tmp
3) git pull
On Fri, Jul 21, 2017 at 10:01 AM, Jeff Andich wrote:
> Hi,
>
> Yesterday, for some reason, when I fetched the 2017.01 u-boot, it no longer
> runs on my 572xEVM/??BB-X15?? Nothing prints out on console and no lights
> blink around the SD Card. However, when I re-dd'ed MLO and u-boot.img to
> the
Hi,
Yesterday, for some reason, when I fetched the 2017.01 u-boot, it no longer
runs on my 572xEVM/??BB-X15?? Nothing prints out on console and no lights
blink around the SD Card. However, when I re-dd'ed MLO and u-boot.img to
the SD Card fetched 2 months ago, using the same instructions for
20 matches
Mail list logo
