On Mon, Dec 21, 2015 at 10:11 PM, wrote:
>
>> > Where are the User LED blink codes provided or documented?
>>
>> The only real LED blink code is on bootup, a solid pattern
>>
>> [] [] [] [] - off
>> [x] [] [] [] - on, starting mmc scan...
>> [x] [x] [] [] - scanning mmc...
>> [x] [x] [x] [] - pro
> > Where are the User LED blink codes provided or documented?
>
> The only real LED blink code is on bootup, a solid pattern
>
> [] [] [] [] - off
> [x] [] [] [] - on, starting mmc scan...
> [x] [x] [] [] - scanning mmc...
> [x] [x] [x] [] - processed boot script...
> [x] [x] [x] [x] - jum
On Mon, Dec 21, 2015 at 9:06 PM, wrote:
> I attempted to flash the eMMC image on a BeagleBone Black, but I've lost
> control of the device. At minimum, I lost SSH, HTTP and other network
> connectivity, and I suspect the device may be bricked.
Well, physical damage is the only way to brick this
I attempted to flash the eMMC image on a BeagleBone Black, but I've lost
control of the device. At minimum, I lost SSH, HTTP and other network
connectivity, and I suspect the device may be bricked.
I'm now trying to decipher the User LED blink codes to understand the
device state and where thin
>
> *Sure, internally, it's just bmaptools/dd...*
>
> * and it'll dump errors/directions to the serial console..*
>
> * For almost all *.img's i include a *.job.txt file that'll just work.*
>
Ok, cool. I kind of half expected this to be a Jessie only feature.
On Mon, Dec 21, 2015 at 5:17 PM, Robe
On Mon, Dec 21, 2015 at 5:35 PM, William Hermans wrote:
> Robert, can this also be used with the "release" images as well ?
Sure, internally, it's just bmaptools/dd...
and it'll dump errors/directions to the serial console..
For almost all *.img's i include a *.job.txt file that'll just work.
Robert, can this also be used with the "release" images as well ?
On Mon, Dec 21, 2015 at 3:41 PM, Robert Nelson
wrote:
> On Mon, Dec 21, 2015 at 4:35 PM, Maxim Podbereznyy
> wrote:
> > so I need both microsd card and USB flash drive?
>
> There is also a hook to do it from a single "usbflasher
Ahh!!!
Thanks Gerald.
Interesting that this is not configurable.
Great to know what to expect though.
Bill
On Tuesday, December 15, 2015 at 1:54:08 PM UTC-8, Gerald wrote:
>
> It is in the data sheet, not the TRM.
>
> Table 4-1, columns 7 and 8.
>
> Gerald
>
> On Tue, Dec 15, 2015 at 2:52 PM,
On Mon, Dec 21, 2015 at 4:35 PM, Maxim Podbereznyy wrote:
> so I need both microsd card and USB flash drive?
There is also a hook to do it from a single "usbflasher" microSD card:
https://github.com/RobertCNelson/boot-scripts/blob/master/tools/eMMC/init-eMMC-flasher-from-usb-media.sh#L575
Just
so I need both microsd card and USB flash drive?
2015-12-22 1:33 GMT+03:00 Robert Nelson :
> On Mon, Dec 21, 2015 at 4:32 PM, Maxim Podbereznyy
> wrote:
> > Robert,
> >
> > if I use now very simple flasher
> > BBB-blank-eMMC-flasher-debian-7.8-console-armhf-2015-07-28-2gb which does
> > all job
On Mon, Dec 21, 2015 at 4:32 PM, Maxim Podbereznyy wrote:
> Robert,
>
> if I use now very simple flasher
> BBB-blank-eMMC-flasher-debian-7.8-console-armhf-2015-07-28-2gb which does
> all job just perfect, why is your suggested way so complicated? :)
It's 'complex' because everyone wanted differen
Robert,
if I use now very simple
flasher BBB-blank-eMMC-flasher-debian-7.8-console-armhf-2015-07-28-2gb
which does all job just perfect, why is your suggested way so complicated?
:)
2015-12-22 1:28 GMT+03:00 Robert Nelson :
> On Mon, Dec 21, 2015 at 4:16 PM, Maxim Podbereznyy
> wrote:
> > Hi!
>
On Mon, Dec 21, 2015 at 4:16 PM, Maxim Podbereznyy wrote:
> Hi!
>
> Where can I get the flasher image for BLANK boards? I can see a number of
> flasher images for different boards/clones but they all boot only on boards
> with filled EEPROM.
Step 1:
Grab the "usbflasher"
https://rcn-ee.com/root
Hi!
Where can I get the flasher image for BLANK boards? I can see a number of
flasher images for different boards/clones but they all boot only on boards
with filled EEPROM.
--
LinkedIn - http://www.linkedin.com/in/maximpodbereznyy
Company - http://www.linkedin.com/company/mentorel
Facebook - ht
Since you are talking about interrupts, you can only implement interrupt
routines in kernel code, but all kernel code is developed in C, not C++.
Starting with the Linux Kernel source code, do the following:
git grep irqreturn_t
This will give you all interrupt routings in the Kernel source. Yo
Hi Samer and Andrew,
I have the same quetions as Samer's. I'm glad I can find some answer here,
but I still have further questions below. Could you provide
your suggestions?
1. I didn't see any *.dtbo file in /system/vendor/firmware. Here is what I
see.
shell@beagleboneblack:/system/vendor/fir
so what results did you get from your project? were you able to attach
interrupt in c++ for beaglebone?
On Tuesday, 22 April 2014 03:09:28 UTC+5:30, Patrick Ireland wrote:
>
> With a cursory exploration, it appears that I am unable to attach
> interrupt handlers from C++ code. Is this indeed t
do you have interrupt code for beaglebone in c++. help me out here.
On Friday, 27 December 2013 11:36:47 UTC+5:30, Dave Hylands wrote:
>
> Hi,
>
>
> On Tue, Dec 24, 2013 at 2:58 PM, >
> wrote:
> >
> > Hey Guys,
> >
> > i am quite new to embedded linux ...
> > My regular province are microcontroll
I found it more convenient for my small module to tweak and compile it on
the beaglebone itself, but I'll set everything up to compile it directly on
the host, then.
thanks for your help
On Sunday, December 20, 2015 at 9:50:03 PM UTC+1, RobertCNelson wrote:
>
>
> On Dec 20, 2015 2:06 PM, "Will
19 matches
Mail list logo
