Date   

Re: New Pi won't boot up

Don Moore
 

here's an observation or two.
First, when I view the card from the windows machine I see 4 partitions, the first called 'boot' and the other 3 empty which I suspect are not.
Second, the keyboard/mouse don't function and that is because, I think, the hub does not light up indicating either it needs power or software to make it happen.

If I download the new OS do I put it on the boot partition or elsewhere?
Once downloaded and put back into the Pi will it boot up and will the keyboard start up?

cheers,
Don - ve3zda


Re: New Pi won't boot up

Chris Morrison
 

For a project in work, we bought 20 Raspberry Pi B+ starter bundles from a supplier on selling through Amazon UK. The bundle included the Pi B+, case, power supply, HDMI cable and a pre loaded SD card. 

It was a luck of the draw if the pre-loaded SD cards worked out of the box. It appeared some of them were loaded with the the wrong image.  e.g. it came with the Raspberry Pi B 2 image, not the B+.

I cant remember how many had the wrong image image but it became quicker for us just to wipe SD card, copy the network install image and them boot them up to finished the install. That way we got the latest images/updates.

Chris 
M1PTT 


Re: New Pi won't boot up

Max
 

My response was in regards to this statement "If not or its a card from an earlier Pi then it wont work. You will need to down load and create an SD with the latest NOOBs on it.
I had the same problem as you describe when I took a known good SD from an existing pi and tried it in the 2."

This was aimed at people who had a running model B or B+ and tried using the same image in the new model 2 B. If the software is brought up to date before moving to the new board you essentially have the same thing as you get with a new download minus a few things. I have made too many changes to the image (dated Sept 10, 2013) that I use to start over again.

Max KG4PID
 


From: "jerome schatten va7vv@... [Raspberry_Pi_4-Ham_RADIO]"
To: Raspberry_Pi_4-Ham_RADIO@...
Sent: Sunday, May 10, 2015 7:43 PM
Subject: Re: [Raspberry_Pi_4-Ham_RADIO] Re: New Pi won't boot up

 
How can you do an apt-get  anything if the pi doesn't boot?
jerome va7vv




From: "Max Harper kg4pid@... [Raspberry_Pi_4-Ham_RADIO]"
To: Raspberry_Pi_4-Ham_RADIO@...
Sent: Sunday, May 10, 2015 3:53 PM
Subject: Re: [Raspberry_Pi_4-Ham_RADIO] Re: New Pi won't boot up

 
I'm running an image on my model 2 that is over two years old. But to get it to work you have to do apt-get update and apt-get upgrade to bring the software up to date. I have six of the new Pi model 2's running on this same image, I know it works.

Max
 



From: "special@... [Raspberry_Pi_4-Ham_RADIO]"
To: Raspberry_Pi_4-Ham_RADIO@...
Sent: Sunday, May 10, 2015 4:41 PM
Subject: [Raspberry_Pi_4-Ham_RADIO] Re: New Pi won't boot up

 
Did the kit come with the latest NOOBS on the sd card?
If not or its a card from an earlier Pi then it wont work. You will need to down load and create an SD with the latest NOOBs on it.
I had the same problem as you describe when I took a known good SD from an existing pi and tried it in the 2.


Dale







Re: multimeters with a USB interface linux?

Siegfried Jackstien
 

No ... you were probably talking about 20-30 year old gear :-)


Dg9bfc


Sigi

-----Ursprüngliche Nachricht-----
Von: Raspberry_Pi_4-Ham_RADIO@yahoogroups.com [mailto:Raspberry_Pi_4-
Ham_RADIO@yahoogroups.com]
Gesendet: Sonntag, 10. Mai 2015 20:45
An: Raspberry_Pi_4-Ham_RADIO@yahoogroups.com
Betreff: Re: [Raspberry_Pi_4-Ham_RADIO] Re: multimeters with a USB
interface linux?




Hi Dick Ok It was worth checking, as these things get more processing
power it becomes possible....I am probably talking of 10 year old product,
where we saw that problem.

Alan
G3NYK

----- Original Message -----
From: g4bbh@btinternet.com [Raspberry_Pi_4-Ham_RADIO]
<mailto:g4bbh@btinternet.com [Raspberry_Pi_4-Ham_RADIO]>
To: Raspberry_Pi_4-Ham_RADIO@yahoogroups.com
Sent: Sunday, May 10, 2015 9:03 PM
Subject: Re: [Raspberry_Pi_4-Ham_RADIO] Re: multimeters with a USB
interface linux?

Hi Alan
The article at linuxtoys.org suggests that it is ASCII data. I seem
to remember that my Chinese made cheap DMM with RS-232 also responded as
ASCII strings when I looked at it as a 1200bd serial port (under windows)
with my USB to RS-232 adapter. A quick check on the RPi2 also had results
using a terminal emulator and /dev//ttyUSB0. Not gone further than that.
A good start might be to 'sniff' the serial data using original
Windows software and see what the protocols are but that needs an older
window machine if the software won't run on Win7
Dick G4BBH


Re: SOLVED - TNC-Pi in i2c mode with JNOS 2.0?

Bradley Andrews
 

Hello group,

After a whole lot of fiddling I think I’ve found the proper incantation to make this all work magically together. If I weren’t such a Linux NOOB I probably would have found it earlier. Oh well, gotta learn somehow!

 

(In case you don’t remember, I’m trying to get JNOS 2.0 running on the Pi to work with the TNC-Pi in i2c mode.)

 

The missing ingredient in all the instructions was inclusion of the path ‘ /dev’ in the ‘comname’ field of the i2ckiss command. I have i2ckiss in the jnos directory.

 

Usage: i2ckiss [-p ] [-d] [-l] [-v] <i2cbus> symlink

(Question for John ‘BPQ: What are the –p, -d, -l, -v options used for?)

 

For device address of 16 (0x10) which I’ve chosen to call ‘tnc16’:

sudo ./I2ckiss 1 16 symlink /dev/tnc16

 

Response:

“i2ckiss 1.0.1.0

Slave device is /dev/pts/1

Resetting TNC…

Symlink: success

Symlink from /dev/pts/1 to /dev/tnc16 created”

 

Note that sometimes instead of “symlink: success” I receive “symlink: no such file or directory”. I have not been able to determine why, but it still appears to work. (Any Linux gurus who might be able to shed light?)

 

Then in JNOS 2.0 (Linux version) the attach command is:

Usage: attach asy <io_addr> <mtu> []

attach asy tnc16 – ax25 vhf 4096 256 19200

where ‘-‘ is . Note that is required, as is , though Linux doesn’t use them. The ‘vhf’ is the name of the interface by which all other JNOS commands will know it.

 

Before adding the path to the field of i2ckiss, the symlink file ‘tnc16’ would be created in the /home/pi/jnos folder. Somewhere along the line I got the idea (picture the flickering bulb above Beavis and Butt-head) that maybe the JNOS attach command needed the path so I tried

attach asy /home/pi/jnos/tnc16 – ax25 vhf 4096 256 19200

and got the response

“can’t lock /dev//home/pi/jnos/tnc16

(/var/lock/LCK../hotnc16): no sych file or directory”

The two slashes after /dev clued me in that JNOS was looking in the /dev directory already. (Again, maybe if I weren’t such a NOOB I would have known this?)

 

Taking a cue from the autoexec.nos file generated by the JNOS 2.0 automated installer, which shells out to the Linux command line and creates a ‘tun’ interface through which JNOS can interact with the Linux TCP/IP stack, I added a ‘shell’ command to my autoexec.nos file which will run the i2ckiss command when JNOS starts up. This must run before the ‘attach’ command discussed above.

shell sudo ./i2ckiss 1 16 symlink /dev/tnc16

Responses from the i2ckiss command will appear in JNOS.

 

So this is the section I added to my autoexec.nos file:

 

#  To use TNC-Pi in i2c mode DEBUGGED 10May15 KB9BPF

#  Create pty pair, then create symlink to /dev/pts/1

#  by shelling out to Linux command line and running i2ckiss

#

shell sudo ./i2ckiss 1 16 symlink /dev/tnc16

#

#  responds with "... symlink from /dev/pts/1 to tnc16 created"

#

# Give it a chance to come up. Probably 5 seconds is way longer than necessary.

#

pause 5

#

# Usage: attach asy [] []

# note: Linux uses the device name for

# = 'tnc16': symlink to tnc16 created by i2ckiss command above

# note: Linux doesn't use so = '-'

# = 'asy', = 'ax0', = '-', = 'ax25',

# = 'vhf', = 4096, = 256, = 19200 (this worked)

#

attach asy tnc16 - ax25 vhf 4096 256 19200

 

For a second TNC-Pi with an i2c address of 32 (0x20) I added these lines:

 

#  Create pty pair, then create symlink to /dev/pts/2

#  by shelling out to Linux command line and running i2ckiss

#

shell sudo ./i2ckiss 1 32 symlink /dev/tnc32

#

#  responds with "... symlink from /dev/pts/2 to tnc32 created"

#

# Give it a chance to come up. Probably 5 seconds is way longer than necessary.

#

pause 5

#

# Usage: attach asy [] []

# note: Linux uses the device name for

# = 'tnc32': symlink to tnc32 created by i2ckiss command above

# note: Linux doesn't use = '-'

# = 'asy', = 'ax0', = '-', = 'ax25',

# = 'vhf2', = 4096, = 256, = 19200 (this worked)

#

attach asy tnc32 - ax25 vhf2 4096 256 19200

 

Then do all the usual configuring of the interfaces ‘vhf’ and ‘vhf2’. Ifconfig decription, ipaddress, ‘route’ commands, etc. as you would any other TNC.

 

[I haven’t tried it with Xastir yet, but I expect that /dev/tnc16 will be the right thing to add to the device list. Don’t know if Xastir allows something like the JNOS ‘shell’ command. If not, will have to run i2ckiss command before running Xastir.]

 

I found that if I did not unlink the TNC-Pis after JNOS uses them, the next time I start JNOS they won’t work. I think this was even when the i2ckiss symlinks were created manually, before adding the shell commands to ‘autoexec.nos’. JNOS also runs commands from the ‘onexit.nos’ file when it exits, so I added these lines to ‘onexit.nos’ to shell out and unlink them automatically .

 

# shell out to unlink the i2ckiss symlinks

shell sudo unlink /dev/tnc16

pause 5

shell sudo unlink /dev/tnc32

pause 5

 

Along the way I learned these other things, too. I’ll mention them here in case another NOOB needs them.

 

pitnc_getparams and pitnc_setparams must be run as SuperUser. I also found that I had to add ‘./’ to the beginning of the command name to make them work.

Ex.: sudo ./pitnc_getparams 1 16

Without the ‘sudo’ it will complain “cannot find i2cbus /dev/i2c-1”

 

When I initially began playing with the i2ckiss command, no matter what I did I got “permission denied”. Internet search clued me to check the user permissions.

In file manager, right-click i2ckiss. Goto the Permissions tab.

I found i2ckiss’s permissions set to ‘Nobody’. Set them to ‘Anybody’. Also, remember to run the i2ckiss command as SuperUser.

 

And, don’t forget to follow John Wiseman’s instructions and add user ‘pi’i to the i2c group:

sudo usermod –a –G i2c pi

 

One last thing: Make sure your TNC-Pis are running the latest TNC-Pi firmware from John Hansen W2FS before attempting to use the i2c bus with the TNC-Pi. When you run pitnc_getparams (‘pitnc_getparams 0 0’ for TNC-Pis running in default async serial mode) it will tell you the version. The PICs that John shipped with my kits were version 3 by mistake, and they did not do the ‘turn the TXD pot fully CCW to reset the TNC to default’ trick, which caused me considerable consternation until I contacted him. The latest version, which confusingly identifies as version 1, is much easier to work with.

 

Good luck and 73,

Brad KB9BPF

 

P.S. I’m hoping to get to Dayton next weekend!

 

 

 

From: Raspberry_Pi_4-Ham_RADIO@... [mailto:Raspberry_Pi_4-Ham_RADIO@...]
Sent: Saturday, May 02, 2015 9:24 AM
To: Raspberry_Pi_4-Ham_RADIO@...
Subject: Re: [Raspberry_Pi_4-Ham_RADIO] TNC-Pi in i2c mode with JNOS 2.0?

 

 

Brad,

I assume you are referring to this:

To use with a KISS application

./i2ckiss 0 16 symlink com1

i2ckiss will create a pty pair, then create a symlink to com1. The
application would then be configured to use port com1.

I'm not a jnos expert, but I think in linux the device name replaces the
IO Addr and the Vector is unused, so the attach command would be

attach asy com1 0 []

Or forget about jnos and run LinBPQ!

73, John G8BPQ

------ Original Message ------
From: "'Brad Andrews' kb9bpf@... [Raspberry_Pi_4-Ham_RADIO]"

To: Raspberry_Pi_4-Ham_RADIO@...
Sent: 02/05/2015 15:07:33
Subject: RE: [Raspberry_Pi_4-Ham_RADIO] TNC-Pi in i2c mode with JNOS
2.0?

Thanks for the reply, James.

I think you are referring to the document by John J. McDonough, WB8RCR.

On page 13 the screen print of the output of the pitnc_getparams
command, parameter 07, ‘I2C Address (0 = async) Hex’ is zero, so the
TNC-Pi is running in async mode, not I2C mode.

This works well for me using one TNC-Pi and JNOS that was compiled on
Raspian from the source.

However, what I am trying to accomplish is some way for JNOS to
communicate with the TNC-Pi in I2C mode so that I can have more than one
TNC-Pi attached at a time for multiple radio ports. The section of the
TNC-Pi manual on using i2ckiss with applications other than BPQ isn’t
specific enough for me to translate to a JNOS attach command. I’m hoping
someone has been able to do this and can instruct me.

Thanks again,

Brad


Re: New Pi won't boot up

Bob Nielsen <n7xy@...>
 

Obviously you cannot. One needs to download the latest image from raspberrypi.org and install it on a microSD card. The newer image will work with the original PI B snd B+, as well as the B2.


Bob, N7XY

On May 10, 2015, at 5:43 PM, jerome schatten va7vv@ehpes.com [Raspberry_Pi_4-Ham_RADIO] <Raspberry_Pi_4-Ham_RADIO@yahoogroups.com> wrote:


How can you do an apt-get anything if the pi doesn't boot?
jerome va7vv

From: "Max Harper kg4pid@yahoo.com [Raspberry_Pi_4-Ham_RADIO]" <Raspberry_Pi_4-Ham_RADIO@yahoogroups.com>
To: Raspberry_Pi_4-Ham_RADIO@yahoogroups.com
Sent: Sunday, May 10, 2015 3:53 PM
Subject: Re: [Raspberry_Pi_4-Ham_RADIO] Re: New Pi won't boot up


I'm running an image on my model 2 that is over two years old. But to get it to work you have to do apt-get update and apt-get upgrade to bring the software up to date. I have six of the new Pi model 2's running on this same image, I know it works.

Max



From: "special@ilizarov.org.uk [Raspberry_Pi_4-Ham_RADIO]" <Raspberry_Pi_4-Ham_RADIO@yahoogroups.com>
To: Raspberry_Pi_4-Ham_RADIO@yahoogroups.com
Sent: Sunday, May 10, 2015 4:41 PM
Subject: [Raspberry_Pi_4-Ham_RADIO] Re: New Pi won't boot up


Did the kit come with the latest NOOBS on the sd card?
If not or its a card from an earlier Pi then it wont work. You will need to down load and create an SD with the latest NOOBs on it.
I had the same problem as you describe when I took a known good SD from an existing pi and tried it in the 2.


Dale






Re: New Pi won't boot up

jerome schatten
 

How can you do an apt-get  anything if the pi doesn't boot?
jerome va7vv


From: "Max Harper kg4pid@... [Raspberry_Pi_4-Ham_RADIO]"
To: Raspberry_Pi_4-Ham_RADIO@...
Sent: Sunday, May 10, 2015 3:53 PM
Subject: Re: [Raspberry_Pi_4-Ham_RADIO] Re: New Pi won't boot up

 
I'm running an image on my model 2 that is over two years old. But to get it to work you have to do apt-get update and apt-get upgrade to bring the software up to date. I have six of the new Pi model 2's running on this same image, I know it works.

Max
 



From: "special@... [Raspberry_Pi_4-Ham_RADIO]"
To: Raspberry_Pi_4-Ham_RADIO@...
Sent: Sunday, May 10, 2015 4:41 PM
Subject: [Raspberry_Pi_4-Ham_RADIO] Re: New Pi won't boot up

 
Did the kit come with the latest NOOBS on the sd card?
If not or its a card from an earlier Pi then it wont work. You will need to down load and create an SD with the latest NOOBs on it.
I had the same problem as you describe when I took a known good SD from an existing pi and tried it in the 2.


Dale





Re: New Pi won't boot up

Steve Black
 

Starter kit is B+ so it is set for B+. Pi2 requires the updated image to run properly. You must download a new image for the Pi2 from the website and then use it to start up the Pi2. Steve kb1chu


On 5/10/2015 7:34 PM, Don Moore ve3zda@... [Raspberry_Pi_4-Ham_RADIO] wrote:
 
Yes, the kit came with a power supply.  Printed on it is the output voltage of 5V and 2100mA.  The red led stays on once the power is applied. So that should mean that the power supply should be okay?
It's a Pi2 but the starter kit is a B+




Re: New Pi won't boot up

Don Moore
 

Yes, the kit came with a power supply.  Printed on it is the output voltage of 5V and 2100mA.  The red led stays on once the power is applied. So that should mean that the power supply should be okay?
It's a Pi2 but the starter kit is a B+



Re: New Pi won't boot up

Max
 

I'm running an image on my model 2 that is over two years old. But to get it to work you have to do apt-get update and apt-get upgrade to bring the software up to date. I have six of the new Pi model 2's running on this same image, I know it works.

Max
 


From: "special@... [Raspberry_Pi_4-Ham_RADIO]"
To: Raspberry_Pi_4-Ham_RADIO@...
Sent: Sunday, May 10, 2015 4:41 PM
Subject: [Raspberry_Pi_4-Ham_RADIO] Re: New Pi won't boot up

 
Did the kit come with the latest NOOBS on the sd card?
If not or its a card from an earlier Pi then it wont work. You will need to down load and create an SD with the latest NOOBs on it.
I had the same problem as you describe when I took a known good SD from an existing pi and tried it in the 2.


Dale



Re: New Pi won't boot up

Don Moore
 

Yes, it comes with Raspbian OS flashed on it.

I've been watching the video etc. but so far no luck. I did notice that in the video, all of the leds flicker away on bootup.  I will keep reading and thanks..

Don



On Sunday, May 10, 2015 6:44 PM, "Anthony Stortz anthony.stortz@... [Raspberry_Pi_4-Ham_RADIO]" wrote:


 
I'm not sure if the starter kit comes with an image flashed to the memory card or not. Did you flash/load an operating system image to the memory card?

If you just opened the box and hooked everything up, I'd suggest going to the following link which is a tutorial on how to get it up and running.

https://www.raspberrypi.org/help/quick-start-guide/


On Sun, May 10, 2015 at 3:58 PM, ve3zda@... [Raspberry_Pi_4-Ham_RADIO] <Raspberry_Pi_4-Ham_RADIO@...> wrote:
 
Hi, I'm a newbie to Raspberry and am looking for or seeking information on how to figure out why it won't start up.
I purchased the starter kit for the Raspberry Pi B+ and a Raspberry Pi 2

I plugged the kit parts into the pi, and a usb wireless keyboard/mouse.
I'm also using the HDMI cable in order to use the TV as the monitor.
Once ready I then turned on the power switch.
The red led came on steady and the green one to the left of it lit for a second or two then went out.
The monitor lit up indicating that it is 1080p and a Raspberry across the top and the background has the 4 standard colors in 4 equal parts of the screen but that's it.
I expected the other leds near the red to flicker but that did not happen.
I tried several times and got the same result each time.

I then took the micro SD card out and checked to see if there is any data on it and there is, just over 9 MB.  If there is supposed to be more than that how would I go about trying to view/read it to ensure that everything that is needed to get started is in fact on the card?  I'm wondering if I can't see it all because it may be bindery or something and not readily visible.  I'm using a windows machine to check the card.

Is there something else I could try to get it to boot up?



--
Anthony J. Stortz Jr.
CIPM, PME
Email: anthony.stortz@...
Phone: 832.413.2224



Re: New Pi won't boot up

Max
 

A little more info is needed. Did you create the microSD card yourself or did it come loaded with your kit? I've read where some have received a card that wasn't loaded correctly. The card has two partitions on it, the first is formatted as FAT and the second is the Linux partition so windows can only read the first partition unless you install a utility that lets windows read Linux partitions. 

Did you happen to check the voltage of your power supply? There should be test points on the newer Pi's for checking that. On the Model 2 the red led will blink or turn off if the voltage drops too low. Can't remember if the B+ has this or not. The green led is a SD card active light and should flicker as the card is being read or written to.

If you have another memory card I would create it from scratch and see what happens. There is a good chance that will fix your problem. It's doubtful you have 2 bad pi's.

Max KG4PID
 


From: "ve3zda@... [Raspberry_Pi_4-Ham_RADIO]" <Raspberry_Pi_4-Ham_RADIO@...>
To: Raspberry_Pi_4-Ham_RADIO@...
Sent: Sunday, May 10, 2015 3:58 PM
Subject: [Raspberry_Pi_4-Ham_RADIO] New Pi won't boot up

 
Hi, I'm a newbie to Raspberry and am looking for or seeking information on how to figure out why it won't start up.
I purchased the starter kit for the Raspberry Pi B+ and a Raspberry Pi 2

I plugged the kit parts into the pi, and a usb wireless keyboard/mouse.
I'm also using the HDMI cable in order to use the TV as the monitor.
Once ready I then turned on the power switch.
The red led came on steady and the green one to the left of it lit for a second or two then went out.
The monitor lit up indicating that it is 1080p and a Raspberry across the top and the background has the 4 standard colors in 4 equal parts of the screen but that's it.
I expected the other leds near the red to flicker but that did not happen.
I tried several times and got the same result each time.

I then took the micro SD card out and checked to see if there is any data on it and there is, just over 9 MB.  If there is supposed to be more than that how would I go about trying to view/read it to ensure that everything that is needed to get started is in fact on the card?  I'm wondering if I can't see it all because it may be bindery or something and not readily visible.  I'm using a windows machine to check the card.

Is there something else I could try to get it to boot up?



Re: New Pi won't boot up

Mark Dymek <markdymek@...>
 

sounds like a power issue. did the kit you bought come with a 2.5amp power supply? if it did your supply might be bad. the fact that your getting minimal startup is not a software thing its hardware. before saying the pi itself is bad try a different supply. windows might not be able to read the filesystem of the card if its ext formatted. you “turned on the power switch” most supplies I’ve seen just have the micro usb plug that you connect to the pi. sounds like either you have a bad supply or you got some kind of weird thing. make sure your getting 2.5 amps. 


On May 10, 2015, at 4:58 PM, ve3zda@... [Raspberry_Pi_4-Ham_RADIO] <Raspberry_Pi_4-Ham_RADIO@...> wrote:


Hi, I'm a newbie to Raspberry and am looking for or seeking information on how to figure out why it won't start up.

I purchased the starter kit for the Raspberry Pi B+ and a Raspberry Pi 2


I plugged the kit parts into the pi, and a usb wireless keyboard/mouse.

I'm also using the HDMI cable in order to use the TV as the monitor.

Once ready I then turned on the power switch.

The red led came on steady and the green one to the left of it lit for a second or two then went out.

The monitor lit up indicating that it is 1080p and a Raspberry across the top and the background has the 4 standard colors in 4 equal parts of the screen but that's it.

I expected the other leds near the red to flicker but that did not happen.

I tried several times and got the same result each time.


I then took the micro SD card out and checked to see if there is any data on it and there is, just over 9 MB.  If there is supposed to be more than that how would I go about trying to view/read it to ensure that everything that is needed to get started is in fact on the card?  I'm wondering if I can't see it all because it may be bindery or something and not readily visible.  I'm using a windows machine to check the card.


Is there something else I could try to get it to boot up?




Re: New Pi won't boot up

special@...
 

Did the kit come with the latest NOOBS on the sd card?
If not or its a card from an earlier Pi then it wont work. You will need to down load and create an SD with the latest NOOBs on it.
I had the same problem as you describe when I took a known good SD from an existing pi and tried it in the 2.


Dale


Re: New Pi won't boot up

Anthony Stortz <anthony.stortz@...>
 

I'm not sure if the starter kit comes with an image flashed to the memory card or not. Did you flash/load an operating system image to the memory card?

If you just opened the box and hooked everything up, I'd suggest going to the following link which is a tutorial on how to get it up and running.

https://www.raspberrypi.org/help/quick-start-guide/


On Sun, May 10, 2015 at 3:58 PM, ve3zda@... [Raspberry_Pi_4-Ham_RADIO] <Raspberry_Pi_4-Ham_RADIO@...> wrote:
 

Hi, I'm a newbie to Raspberry and am looking for or seeking information on how to figure out why it won't start up.

I purchased the starter kit for the Raspberry Pi B+ and a Raspberry Pi 2


I plugged the kit parts into the pi, and a usb wireless keyboard/mouse.

I'm also using the HDMI cable in order to use the TV as the monitor.

Once ready I then turned on the power switch.

The red led came on steady and the green one to the left of it lit for a second or two then went out.

The monitor lit up indicating that it is 1080p and a Raspberry across the top and the background has the 4 standard colors in 4 equal parts of the screen but that's it.

I expected the other leds near the red to flicker but that did not happen.

I tried several times and got the same result each time.


I then took the micro SD card out and checked to see if there is any data on it and there is, just over 9 MB.  If there is supposed to be more than that how would I go about trying to view/read it to ensure that everything that is needed to get started is in fact on the card?  I'm wondering if I can't see it all because it may be bindery or something and not readily visible.  I'm using a windows machine to check the card.


Is there something else I could try to get it to boot up?




--
Anthony J. Stortz Jr.
CIPM, PME
Email: anthony.stortz@...
Phone: 832.413.2224


Re: New Pi won't boot up

brian <brian@...>
 

Hi
   Your Windows machine will only see the boot partition which is small, the green light flashes shortly after power is connected then mostly flashes while booting.

Try using a different SD card or image, you can use Win32diskimager to flash a new image.

Brian



Sent from Samsung Mobile


-------- Original message --------
From: "ve3zda@... [Raspberry_Pi_4-Ham_RADIO]"
Date:10/05/2015 21:58 (GMT+00:00)
To: Raspberry_Pi_4-Ham_RADIO@...
Subject: [Raspberry_Pi_4-Ham_RADIO] New Pi won't boot up

 

Hi, I'm a newbie to Raspberry and am looking for or seeking information on how to figure out why it won't start up.

I purchased the starter kit for the Raspberry Pi B+ and a Raspberry Pi 2


I plugged the kit parts into the pi, and a usb wireless keyboard/mouse.

I'm also using the HDMI cable in order to use the TV as the monitor.

Once ready I then turned on the power switch.

The red led came on steady and the green one to the left of it lit for a second or two then went out.

The monitor lit up indicating that it is 1080p and a Raspberry across the top and the background has the 4 standard colors in 4 equal parts of the screen but that's it.

I expected the other leds near the red to flicker but that did not happen.

I tried several times and got the same result each time.


I then took the micro SD card out and checked to see if there is any data on it and there is, just over 9 MB.  If there is supposed to be more than that how would I go about trying to view/read it to ensure that everything that is needed to get started is in fact on the card?  I'm wondering if I can't see it all because it may be bindery or something and not readily visible.  I'm using a windows machine to check the card.


Is there something else I could try to get it to boot up?


New Pi won't boot up

Don Moore
 

Hi, I'm a newbie to Raspberry and am looking for or seeking information on how to figure out why it won't start up.

I purchased the starter kit for the Raspberry Pi B+ and a Raspberry Pi 2


I plugged the kit parts into the pi, and a usb wireless keyboard/mouse.

I'm also using the HDMI cable in order to use the TV as the monitor.

Once ready I then turned on the power switch.

The red led came on steady and the green one to the left of it lit for a second or two then went out.

The monitor lit up indicating that it is 1080p and a Raspberry across the top and the background has the 4 standard colors in 4 equal parts of the screen but that's it.

I expected the other leds near the red to flicker but that did not happen.

I tried several times and got the same result each time.


I then took the micro SD card out and checked to see if there is any data on it and there is, just over 9 MB.  If there is supposed to be more than that how would I go about trying to view/read it to ensure that everything that is needed to get started is in fact on the card?  I'm wondering if I can't see it all because it may be bindery or something and not readily visible.  I'm using a windows machine to check the card.


Is there something else I could try to get it to boot up?


Re: multimeters with a USB interface linux?

Alan Melia
 


Hi Dick Ok It was worth checking, as these things get more processing power it becomes possible....I am probably talking of 10 year old product, where we saw that problem.
 
Alan
G3NYK

----- Original Message -----
Sent: Sunday, May 10, 2015 9:03 PM
Subject: Re: [Raspberry_Pi_4-Ham_RADIO] Re: multimeters with a USB interface linux?

Hi Alan
The article at linuxtoys.org suggests that it is ASCII data.  I seem to remember that my Chinese made cheap DMM with RS-232 also responded as ASCII strings when I looked at it as a 1200bd serial port (under windows) with my USB to RS-232 adapter.  A quick check on the RPi2 also had results using a terminal emulator and /dev//ttyUSB0.  Not gone further than that.
A good start might be to 'sniff' the serial data using original Windows software and see what the protocols are but that needs an older window machine if the software won't run on Win7
Dick G4BBH


Re: multimeters with a USB interface linux?

Richard Ferryman
 

Hi Alan
The article at linuxtoys.org suggests that it is ASCII data.  I seem to remember that my Chinese made cheap DMM with RS-232 also responded as ASCII strings when I looked at it as a 1200bd serial port (under windows) with my USB to RS-232 adapter.  A quick check on the RPi2 also had results using a terminal emulator and /dev//ttyUSB0.  Not gone further than that.
A good start might be to 'sniff' the serial data using original Windows software and see what the protocols are but that needs an older window machine if the software won't run on Win7
Dick G4BBH


Re: multimeters with a USB interface linux?

Alan Melia
 


Hi Dick I am not sure about this but the h/h DMMs that I saw with RS-232 interfaces did not transfer ASCII characters to the PC but a code" based on which segments of the 7-segment dispays were "lit". You will need the supplied s/w to interpret this so you may be stuck with what facilities this provides. It is probably no impossible to reverse engineer the code, but I dont think you were intending that.
 
Alan
G3NYK

----- Original Message -----
Sent: Sunday, May 10, 2015 8:17 PM
Subject: [Raspberry_Pi_4-Ham_RADIO] Re: multimeters with a USB interface linux?

There is some realated info at Radio Shack DMM with RS-232

 

THis may be a starter.
Dick

9601 - 9620 of 14061