Re: [beagleboard] Re: Beagle Bone Black stopping at Starting Kernel....

2017-09-26 Thread Madhu K 
Hi,

There are two options to boot the beaglebone black.

1) Boot the beaglebone black from U-boot : In this method whenever
u-boot prompt comes, you can load the uImage and device tree from
u-boot prompt and let the board boot, in this case uEnv.txt is not
required. You can specify the load address and environment in u-boot
itself.

2) Boot the beaglebone black automatically: In this cas, what ever you
are doing above you neeed to specify in the uEnv.txt file.

So I wanted to know which method you are following.

Regards,
Madhu



On Wed, Sep 27, 2017 at 8:51 AM, Ashish Maurya
 wrote:
> Thanks Madhu for replying ...
> I am a newbie, please correct my understanding about uEnv.txt if i am wrong, 
> i am setting the env variables manually like-
> U-Boot# setenv bootargs 'console=ttyO2,115200n8 root=/dev/mmcblk0p2 rw'
> Not sure whether this file is still needed?
> If yes, then please guide me through the process how to get that.
> Thank you very much 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/4e6e6149-3625-4d28-ac75-fe55643e1319%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/CAA2oCO%3DvXaRp8YzdPzLiKVj%3D5uaw_MDSDmPdh72QRrk6Tp_%3D%2Bg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: PocketBeagle U-Boot Overlays [naming???]

2017-09-26 Thread William Hermans 
Just out of curiosity though. What's with the sudden interest with Mikrobus
click devices ? Just wondering, as we used one of their boards in a design
about a year ago.

-- 
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/CALHSORpZNtq1K-A31zZ6ye-ErR5F5VUyWi-%2BRgN2Y4d8Ma_80Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: PocketBeagle U-Boot Overlays [naming???]

2017-09-26 Thread William Hermans 
On Tue, Sep 26, 2017 at 9:02 PM, Robert Nelson 
wrote:

> On Tue, Sep 26, 2017 at 9:55 PM, Graham  wrote:
> > The interface names seem much more self explanatory.
> > The U/M option is workable.
>
> They list 381 varients:
>
> https://shop.mikroe.com/click
>
> So 381 * 2 dtb overlays..
>
> 99% of them use one interface, SPI/I2C/UART
>
> So if we had to use the interface name, i'd probably simplify it to just:
>
> PB-I2C1-RTC-6-CLICK-00A0.dtbo
> PB-I2C2-RTC-6-CLICK-00A0.dtbo
>
> Maybe that'll be good enough to help users know which side to plug in?
>
> Regards,
>

Looks good to 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/CALHSORrw-kREL46mVS7OipdTLRkrzP9yJ8GPaJ6q6LOb06pc-Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: PocketBeagle U-Boot Overlays [naming???]

2017-09-26 Thread Robert Nelson 
On Tue, Sep 26, 2017 at 9:55 PM, Graham  wrote:
> The interface names seem much more self explanatory.
> The U/M option is workable.

They list 381 varients:

https://shop.mikroe.com/click

So 381 * 2 dtb overlays..

99% of them use one interface, SPI/I2C/UART

So if we had to use the interface name, i'd probably simplify it to just:

PB-I2C1-RTC-6-CLICK-00A0.dtbo
PB-I2C2-RTC-6-CLICK-00A0.dtbo

Maybe that'll be good enough to help users know which side to plug in?

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/CAOCHtYigAyWYUg19R9EwDs1%3D3%2B78U3w3c%2BeqF%2B9cOQi%2BZWLeiA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Beagle Bone Black stopping at Starting Kernel....

2017-09-26 Thread Ashish Maurya 
Thanks Madhu for replying ...
I am a newbie, please correct my understanding about uEnv.txt if i am wrong, i 
am setting the env variables manually like-
U-Boot# setenv bootargs 'console=ttyO2,115200n8 root=/dev/mmcblk0p2 rw'
Not sure whether this file is still needed?
If yes, then please guide me through the process how to get that.
Thank you very much 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/4e6e6149-3625-4d28-ac75-fe55643e1319%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: PocketBeagle U-Boot Overlays [naming???]

2017-09-26 Thread Graham 
The interface names seem much more self explanatory.
The U/M option is workable.

--- Graham

==

On Tuesday, September 26, 2017 at 5:15:32 PM UTC-5, RobertCNelson wrote:
>
> On Tue, Sep 26, 2017 at 4:36 PM, Robert Nelson  > wrote: 
> > So i'm working on adding support for a few Overlays (taking advantage 
> > of the CLICK interface).. 
> > 
> > What do you guys think of this naming: 
> > 
> > Option A/B: (there's no A or B on the board) 
> > 
> > PB-A-RTC-6-CLICK-00A0.dtbo 
> > PB-B-RTC-6-CLICK-00A0.dtbo 
> > 
> > Use the interface names: 
> > 
> > PB-U4-I2C1-SPI0-RTC-6-CLICK-00A0.dtbo 
> > PB-U2-I2C2-SPI1-RTC-6-CLICK-00A0.dtbo 
> > 
> > Option U/M (aka U=USB, M=MicroSD) because Click "fits" over that... 
> > 
> > PB-U-RTC-6-CLICK-00A0.dtbo 
> > PB-M-RTC-6-CLICK-00A0.dtbo 
> > 
> > I personally like the U/M option.. as it the easiest to explain to new 
> > users (or is it?). 
>
> Ps, if we assume "config-pin" we can make these much simplier: 
>
>
> https://github.com/RobertCNelson/bb.org-overlays/commit/aa5491da3444e3f33dc128ab8650312b32ded0f1
>  
>
> root@beaglebone:~# dmesg | grep rtc 
> [1.836679] rtc-ds1307 1-006f: rtc core: registered mcp7941x as rtc0 
> [1.836716] rtc-ds1307 1-006f: 64 bytes nvram 
> [1.839208] omap_rtc 44e3e000.rtc: already running 
> [1.839793] omap_rtc 44e3e000.rtc: rtc core: registered 44e3e000.rtc as 
> rtc1 
> [1.950076] PM: bootloader does not support rtc-only! 
> [1.952034] rtc-ds1307 1-006f: setting system clock to 2017-09-26 
> 17:00:18 UTC (1506445218) 
>
> 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/f8e6fe43-9947-42c8-9e05-ab1eb8c84111%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: PocketBeagle U-Boot Overlays [naming???]

2017-09-26 Thread Robert Nelson 
On Tue, Sep 26, 2017 at 4:36 PM, Robert Nelson  wrote:
> So i'm working on adding support for a few Overlays (taking advantage
> of the CLICK interface)..
>
> What do you guys think of this naming:
>
> Option A/B: (there's no A or B on the board)
>
> PB-A-RTC-6-CLICK-00A0.dtbo
> PB-B-RTC-6-CLICK-00A0.dtbo
>
> Use the interface names:
>
> PB-U4-I2C1-SPI0-RTC-6-CLICK-00A0.dtbo
> PB-U2-I2C2-SPI1-RTC-6-CLICK-00A0.dtbo
>
> Option U/M (aka U=USB, M=MicroSD) because Click "fits" over that...
>
> PB-U-RTC-6-CLICK-00A0.dtbo
> PB-M-RTC-6-CLICK-00A0.dtbo
>
> I personally like the U/M option.. as it the easiest to explain to new
> users (or is it?).

Ps, if we assume "config-pin" we can make these much simplier:

https://github.com/RobertCNelson/bb.org-overlays/commit/aa5491da3444e3f33dc128ab8650312b32ded0f1

root@beaglebone:~# dmesg | grep rtc
[1.836679] rtc-ds1307 1-006f: rtc core: registered mcp7941x as rtc0
[1.836716] rtc-ds1307 1-006f: 64 bytes nvram
[1.839208] omap_rtc 44e3e000.rtc: already running
[1.839793] omap_rtc 44e3e000.rtc: rtc core: registered 44e3e000.rtc as rtc1
[1.950076] PM: bootloader does not support rtc-only!
[1.952034] rtc-ds1307 1-006f: setting system clock to 2017-09-26
17:00:18 UTC (1506445218)

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/CAOCHtYiPcCMoNWdWroUt3nyrY3G6Vh%3D40EA-QDVM-M7M-uziWg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] PocketBeagle U-Boot Overlays [naming???]

2017-09-26 Thread Robert Nelson 
So i'm working on adding support for a few Overlays (taking advantage
of the CLICK interface)..

What do you guys think of this naming:

Option A/B: (there's no A or B on the board)

PB-A-RTC-6-CLICK-00A0.dtbo
PB-B-RTC-6-CLICK-00A0.dtbo

Use the interface names:

PB-U4-I2C1-SPI0-RTC-6-CLICK-00A0.dtbo
PB-U2-I2C2-SPI1-RTC-6-CLICK-00A0.dtbo

Option U/M (aka U=USB, M=MicroSD) because Click "fits" over that...

PB-U-RTC-6-CLICK-00A0.dtbo
PB-M-RTC-6-CLICK-00A0.dtbo

I personally like the U/M option.. as it the easiest to explain to new
users (or is it?).

Thoughs???

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/CAOCHtYiwi9xsQbUCLnGpuOxANnc5Y2X3L851np%3DxNdq7nUPTGg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Announcing $25 PocketBeagle

2017-09-26 Thread Robert Nelson 
On Tue, Sep 26, 2017 at 1:56 PM, Mikester  wrote:
> Out of the box, plugging the PB into a USB port a single blue LED turns on
> and nothing shows up on any PC connected to it.
>
> Is there an OS pre-installed or do I have to use an image on microSD card to
> boot?

Nope, it's up to "you"...

Here's a fresh build:

https://rcn-ee.net/rootfs/bb.org/testing/2017-09-26/stretch-iot/bone-debian-9.1-iot-armhf-2017-09-26-4gb.img.xz

> Will the USB show up as a serial device or do I have to hard wire the RX and
> TX pins to a USB TTL-232R-3V3 converter?

Over the usb port, a usb ethernet and usb serial port will show up..

> Can I use an OTG Micro USB adapter to plug in a USB ethernet device?

I don't have that configured yet..

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/CAOCHtYh08Zkc%3D3QR6t7Ff%3DVwqeoKr%3DL%2BLMCoyRz7t%3DfBMiNx4A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Announcing $25 PocketBeagle

2017-09-26 Thread Mikester 
Out of the box, plugging the PB into a USB port a single blue LED turns on 
and nothing shows up on any PC connected to it.

Is there an OS pre-installed or do I have to use an image on microSD card 
to boot?
Will the USB show up as a serial device or do I have to hard wire the RX 
and TX pins to a USB TTL-232R-3V3 converter?
Can I use an OTG Micro USB adapter to plug in a USB ethernet device?


On Friday, September 22, 2017 at 10:16:16 AM UTC-4, RobertCNelson wrote:
>
>
> Console is on T0 Rx/Tx by default 
>
> On powerup (remember to hit the pwr button), you can ssh/serial in 
> over the usb port. 
>
>
>

-- 
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/1e3c2c35-a60f-4355-a371-c350b141ccb2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Seeed Grove Base Cape v2, no EEPROM

2017-09-26 Thread Peder Madsen 
I actually think it will work without anything written to the EEPROM on the 
cape. But I followed this technique to put something on the EEPROM and I 
have used it afterwards with success. I used a recent Debian on the 
Beagleboard:

Ensure address switches are pushed to 11 (0x57).
To obtain current contents of eeprom:
cat /sys/bus/i2c/devices/2-0057/eeprom | hexdump -C
To write to cape eeprom, first obtain the text to write:
wget https://github.com/qunanan/GBCFBBv2-Test/raw/master/eeprom.dump
Then write it to the cape eeprom:
cat eeprom.dump > /sys/bus/i2c/devices/2-0057/eeprom
When booting, capemgr will look for a firmware called BB-GREEN_GROVE-00A2 
in /lib/firmware
Even though no firmware of that name is available, the cape works anyway.

Regards Peder Madsen

On Tuesday, September 26, 2017 at 6:39:18 AM UTC+2, Charles Quarra wrote:
>
>
> Does anyone have a Device Tree Overlay spec that can be used for this 
> cape? I cannot find anything like this anywhere, and clearly the cape 
> cannot be loaded without one
>
> On Friday, February 17, 2017 at 8:19:44 AM UTC-5, Peder Madsen wrote:
>>
>> I recently acquired the Seeed Grove Based Cape v2 
>> 
>>  which 
>> apparently does not have a populated EEPROM when delivered. According to 
>> Seed, this seems deliberate although it would be nice with a default 
>> configuration. As an answer to my inquiry regarding this, Seed referred to 
>> the EEPROM utiliity created by Josh Datko and hosted on github 
>> . 
>> While I'm prepared to try my luck with this, I'll appreciate if anybody 
>> already equipped with this cape would be able to post a suitable image I 
>> could burn into my cape.
>>
>>
>>

-- 
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/d91f871f-b44a-415d-babd-9450ac04d7bc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: How to Drive Nixie Clock

2017-09-26 Thread Graham 
fadj:


If you do not understand why your single transistor circuit does not work, 
then I suggest you go read up on "emitter follower" circuits and then think 
about why they are not appropriate in this circumstance.

I suggest you use the second circuit, with the two transistors, and go take 
or repeat a class on semiconductor devices.

I would also add a "pull-down" resistor to the input of the first 
transistor in the two-transistor circuit, so that it can not turn on when 
the driving circuit is not initialized, and "floating".


--- Graham

==



On Tuesday, September 26, 2017 at 6:59:46 AM UTC-5, fadj...@gmail.com wrote:
>
> Good day,all.
>
>
> I am a student who majoring in electronics and I am currently working on 
> my first nixie clock which will be running with Arduino, using a 74141 
> nixie driver for the cathodes (common for 6 tubes) and multiplexing the 
> anodes.
>
>  
>
> See the following picture:
>
>
> 
>
>
> I am using a MPSA42 NPN transistor with the collector connected to 
> +170VDC, the base driven by the Arduino output, and the emitter connects to 
> the tube's anode. The problem is that the switching with the MPSA42 
> doesn't seem to work (doesn't turn ON).
>
> MPSA42 Datasheet 
>
> However,such as this picture:
>
>
> 
>
>
>
> I saw some other design which used both MPSA42 and MPSA92 each of the six 
> anodes like it.My questions:
>
>
>
>- l What might be the reason why the single MPSA42 configuration would 
>not switch ON?
>- l Why would the other design add the MPSA92 and whats the logic 
>behind using the MPSA42 + MPSA92 combination?
>
> PlePlease give me some help! Thank you in advance!
>
>

-- 
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/c56a7664-adfa-4f73-a255-8d6479315ced%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] EMMC OS corruption in Beaglebone Black

2017-09-26 Thread jeevan . j 
Hi,
I am using large number of Beaglebones for a VPN. But some of the 
beaglebones stopped working due to OS corruption( Not even detecting while 
connecting directly to PC). It will start working when we reload the OS 
with the memory card. I would like to install the OS as read only for the 
prevention of this problem.
How can I install the OS in Beaglebone as read only.

-- 
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/5024b2c9-542d-439e-b849-7d4f4fa08ec3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] How to Drive Nixie Clock

2017-09-26 Thread fadjdagd 


Good day,all.


I am a student who majoring in electronics and I am currently working on my 
first nixie clock which will be running with Arduino, using a 74141 nixie 
driver for the cathodes (common for 6 tubes) and multiplexing the anodes.

 

See the following picture:




I am using a MPSA42 NPN transistor with the collector connected to +170VDC, 
the base driven by the Arduino output, and the emitter connects to the tube's 
anode. The problem is that the switching with the MPSA42 doesn't seem to 
work (doesn't turn ON).

MPSA42 Datasheet 

However,such as this picture:





I saw some other design which used both MPSA42 and MPSA92 each of the six 
anodes like it.My questions:



   - l What might be the reason why the single MPSA42 configuration would 
   not switch ON?
   - l Why would the other design add the MPSA92 and whats the logic behind 
   using the MPSA42 + MPSA92 combination?
   
PlePlease give me some help! Thank you in advance!

-- 
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/87ef7156-67f8-43cf-a264-60a81f38e8b6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Beagle Bone Black stopping at Starting Kernel....

2017-09-26 Thread Madhu K 
Hi,

where is your uEnv.txt file?

Regards,
Madhu

On Tuesday, September 26, 2017 at 1:42:19 PM UTC+5:30, Ashish Maurya wrote:
>
> This is what I doing...
>
> U-Boot 2014.04 (Sep 21 2017 - 11:25:07)
>
> I2C:   ready
> DRAM:  512 MiB
> MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
> Using default environment
>
> Net:not set. Validating first E-fuse MAC
> cpsw, usb_ether
> Hit any key to stop autoboot:  0 
> U-Boot# 
> U-Boot# fatls mmc 0:1
> 76868   mlo 
>329548   u-boot.img 
>   4964640   uimage 
> 26024   am335x-boneblack.dtb 
> system volume information/
>
> 4 file(s), 1 dir(s)
>
> U-Boot# fatload mmc 0:1 0x8060 uImage
> reading uImage
> 4964640 bytes read in 1714 ms (2.8 MiB/s)
> U-Boot# fatload mmc 0:1 0x8050 am335x-boneblack.dtb
> reading am335x-boneblack.dtb
> 26024 bytes read in 19 ms (1.3 MiB/s)
> U-Boot# setenv bootargs 'console=ttyO2,115200n8 root=/dev/mmcblk0p2 rw'
> U-Boot# print bootargs
> bootargs=console=ttyO2,115200n8 root=/dev/mmcblk0p2 rw
> U-Boot# bootm 0x8060 - 0x8050
> ## Booting kernel from Legacy Image at 8060 ...
>Image Name:   Linux-3.12.1-bbb
>Image Type:   ARM Linux Kernel Image (uncompressed)
>Data Size:4964576 Bytes = 4.7 MiB
>Load Address: 80008000
>Entry Point:  80008000
>Verifying Checksum ... OK
> ## Flattened Device Tree blob at 8050
>Booting using the fdt blob at 0x8050
>Loading Kernel Image ... OK
>Using Device Tree in place at 8050, end 805095a7
>
> Starting kernel ...
>
>
>
> This is how I built the images-
> Using linux-3.12-bone-black kernel.
> make -j 4 ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- zImage modules dtbs 
> make -j 4 ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- uImage 
> LOADADDR=0x80008000
> make -j 4 ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- modules_install \
> INSTALL_MOD_PATH=/mnt/rootfs
> make -j 4 ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- \
> uImage-dtb.am335x-boneblack LOADADDR=0x80008000
>
> SD card has two partitions, first fat and another ext2. First contains 
> - MLO,u-boot.img,uImage,am335x-boneblack.dtb
> second contains rootfs.
>
> Not getting where I am doing wrong, please help...
> Thank You.
>

-- 
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/1e68c4a8-8d77-41c2-95ff-379e81185874%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Beagle Bone Black stopping at Starting Kernel....

2017-09-26 Thread Ashish Maurya 
This is what I doing...

U-Boot 2014.04 (Sep 21 2017 - 11:25:07)

I2C:   ready
DRAM:  512 MiB
MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
Using default environment

Net:not set. Validating first E-fuse MAC
cpsw, usb_ether
Hit any key to stop autoboot:  0 
U-Boot# 
U-Boot# fatls mmc 0:1
76868   mlo 
   329548   u-boot.img 
  4964640   uimage 
26024   am335x-boneblack.dtb 
system volume information/

4 file(s), 1 dir(s)

U-Boot# fatload mmc 0:1 0x8060 uImage
reading uImage
4964640 bytes read in 1714 ms (2.8 MiB/s)
U-Boot# fatload mmc 0:1 0x8050 am335x-boneblack.dtb
reading am335x-boneblack.dtb
26024 bytes read in 19 ms (1.3 MiB/s)
U-Boot# setenv bootargs 'console=ttyO2,115200n8 root=/dev/mmcblk0p2 rw'
U-Boot# print bootargs
bootargs=console=ttyO2,115200n8 root=/dev/mmcblk0p2 rw
U-Boot# bootm 0x8060 - 0x8050
## Booting kernel from Legacy Image at 8060 ...
   Image Name:   Linux-3.12.1-bbb
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:4964576 Bytes = 4.7 MiB
   Load Address: 80008000
   Entry Point:  80008000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 8050
   Booting using the fdt blob at 0x8050
   Loading Kernel Image ... OK
   Using Device Tree in place at 8050, end 805095a7

Starting kernel ...



This is how I built the images-
Using linux-3.12-bone-black kernel.
make -j 4 ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- zImage modules dtbs 
make -j 4 ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- uImage 
LOADADDR=0x80008000
make -j 4 ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- modules_install \
INSTALL_MOD_PATH=/mnt/rootfs
make -j 4 ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- \
uImage-dtb.am335x-boneblack LOADADDR=0x80008000

SD card has two partitions, first fat and another ext2. First contains 
- MLO,u-boot.img,uImage,am335x-boneblack.dtb
second contains rootfs.

Not getting where I am doing wrong, please help...
Thank You.

-- 
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/df0144cb-ab59-4be3-8285-fdb84b1bd500%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.