Follow Slashdot blog updates by subscribing to our blog RSS feed

 



Forgot your password?
typodupeerror
×
Upgrades Technology Build Hardware Linux

New Raspberry Pi Model B+ 202

mikejuk writes The Raspberry Pi foundation has just announced the Raspberry Pi B+. The basic specs haven't changed much — same BC2835 and 512MB of RAM and the $35 price tag. There are now four USB ports, which means you don't need a hub to work with a mouse, keyboard and WiFi dongle. The GPIO has been expanded to 40 pins, but don't worry: you can plug your old boards and cables into the lefthand part of the connector, and it's backward compatible. As well as some additional general purpose lines, there are two designated for use with I2C EEPROM. When the Pi boots it will look for custom EEPROMs on these lines and optionally use them to load Linux drivers or setup expansion boards. Expansion boards can now include identity chips that when the board is connected configures the Pi to make use of them — no more manual customization. The change to a micro SD socket is nice, unless you happen to have lots of spare full size SD cards around. It is also claimed that the power requirements have dropped by half, to one watt, which brings the model B into the same power consumption area as the model A. Comp video is now available on the audio jack, and the audio quality has been improved. One big step for Raspberry Pi is that it now has four holes for mounting in standard enclosures.
This discussion has been archived. No new comments can be posted.

New Raspberry Pi Model B+

Comments Filter:
  • by brunes69 ( 86786 ) <`gro.daetsriek' `ta' `todhsals'> on Monday July 14, 2014 @08:53AM (#47447803)

    The model B has a lot more thought into the board layout. Having the power, and HDMI all on the same side of the board and the optional I/O also all on one other side, makes so much more sense and will allow much cleaner looking enclosures. Although.. I still wish they had done even MORE thought and out the I/O on the OPPOSITE side of the board where they have all the GPIO pins.

    • by LWATCDR ( 28044 )

      I would still like to see a line in.

      • Agreed, stereo if possible, 48Khz sample rate even better...
        • by bobbied ( 2522392 ) on Monday July 14, 2014 @03:14PM (#47450543)

          Agreed, stereo if possible, 48Khz sample rate even better...

          Correction... 192 Khz sample rate would be *excellent*....

        • Re: (Score:3, Interesting)

          Yes, a respectable line-in would be really nice. For now I have been using the Wolfson Audio Card but it costs as much as the Raspberry Pi itself, and you have to patch the OS to get it to work (but the quality is great). I've tried some of the USB audio devices but found the quality to be not good enough, probably because they are really designed for microphones and even with gain at minimal settings there is too much distortion for line-in. 48kHz is good enough IMO, the Pi doesn't really have enough CP
    • Comment removed based on user account deletion
    • by AmiMoJo ( 196126 ) *

      The layout is mostly dictated by the pinout of the CPU. If you have a look at the schematics and board layout files you can see that in order to keep the number of layers down and density down they pretty much just routed everything outwards from that one part.

  • by feargal ( 99776 ) on Monday July 14, 2014 @09:06AM (#47447877) Homepage

    Like the move to micro-SD, always ended up using full-size SD adapters that just protruded needlessly from the side. I had one device damaged thanks to the SD adapter being knocked, damaging the board, and I know this has happened to many others.

    • Can get 'short' micro-SD to SD adapters that barely protrude. I use them with the R-Pi, Chromebook, MacBook, and several other devices which do not need a full-length SD.

      FYI the micro-SD goes in the side so is not removable while the adapter is plugged in.

    • Yep, i had to super glue a SD-to-microSD adapter into the SD socket. After that i bought the half-length SD to micro SD adapters to avoid that issue. http://www.adafruit.com/produc... [adafruit.com]
  • by FudRucker ( 866063 ) on Monday July 14, 2014 @09:12AM (#47447893)
    http://makezine.com/projects/m... [makezine.com]

    did i read about this here a few weeks ago?
  • by UnknownSoldier ( 67820 ) on Monday July 14, 2014 @09:34AM (#47448007)

    Last I checked there was no RTC (Real Time Clock). Don't see any mention of timer chips?

    • Last I checked there was no RTC (Real Time Clock).

      So use NTP. By default debian launches with the -g opt.

      If you're looking for hardware to operate a satellite site, spend a little more money. Get something with an RTC.

      • Last I checked there was no RTC (Real Time Clock).

        So use NTP. By default debian launches with the -g opt.

        Only really of value when you have a network connection, which for embedded problems can be an issue.

    • by AmiMoJo ( 196126 ) *

      You are supposed to supply your own, or you can use NTP. The idea is to make you learn about computers, not hand you a feature complete system to start with.

  • Glad to see it finally has mounting holes! With a board mounted on top of the Pi, it was a pain to find an enclosure that would work for my projects.

  • by Charliemopps ( 1157495 ) on Monday July 14, 2014 @09:58AM (#47448157)

    Slashdot questions here: Has anyone on slashdot made an effects processor yet?

    I've been toying with the idea of making a RPi based Effects processor. I primarily play guitar but am not going to differentiate between it and any other sound application. I've looked around and found 2 projects, one was "Guitar extended" http://guitarextended.wordpres... [wordpress.com] Which, I'm afraid, is a bit too "We're going to change guitar forever!" for me. I don't want to make yet another crazy sounding thing that no-one wants to listen to, that requires an insane peddle board to control. After I get some decent DSP reverb, gates etc... going, then I'll worry about foot controllers. The fact of the matter is, in most applications I don't need to mess with effects on the fly. I'd even argue that's a bad idea in general.

    My main problem with retail effects is the size. Getting a decent processor usually means it's a double rack space unit. But if you open them up they could have easily fit into a half rack space. I'm guessing this is an appeal to the same part of the brain that likes SUVs. I build my own combo amps, so I'd like to throw in a half rack effects module and maybe something else. But all I've found is the Roland Vf1 which isn't that great, isn't in production anymore and sells for $200+ used. Also, hey I built the amp... why not the processor as well?

    I've not really dove into it yet, I dont like to start these projects myself. It's way easier to let someone else make all of the mistakes and solve the problems for me :-) Also, it seems the RPi has audio latency issues like just about every non-firewire based computer out there. You can fix it, but it's a nightmare of driver and hardware tweaking. I've got a guide: http://wiki.linuxaudio.org/wik... [linuxaudio.org] But that sounds like the typical thing you have to do. That level of complexity is terrifying when you're trying to do a live situation. If you haven't ever played in front of people... God hates live performances... anything that can go wrong, will. I've had retail, $1000+ processors fail live and leave me to just pull the damn plug in the end and go raw.

    I've seen some Arduino projects that use a DSP chip and the arduino swaps out code from the chip to change effects... but that sounds insanely error prone to me. I could pull it off, but I would never really trust it.

    So if anyone has any experience in this area, or links to articles they've found on the topic, I'd love to see them.

    • I am considering buying some embedded board for the guitar effect purpose. While I am familiar with Linux audio recording, I am new to these embedded boards. What kind of latencies does this have ? I want to try to build a multiband distortion, kind of like the Source Audio Multiwave, except more voiced like a TS9, and friendlier to single coils. I hate the nasty sound of too much blocking distortion, typically caused by allowing too much low frequency into the initial distortion stage. I used to confi
      • The latencys is entirely based on the chip. Most are designed for live applications so it's not really an issue. The thing with DSP chips is they don't really need to be all that powerful because they were designed for the specific application you're using them for. If I were you I'd look at the Arduino DSP shields that are out now. I can't really speak for them because I've not used them.

        Here's an older one:
        http://www.amandaghassaei.com/... [amandaghassaei.com]
        Sounds awful though...

        This ones a bit better, but still not that gr

  • Does anyone know if the additional I/O lines include any hardware PWM pins? TFA doesn't say. The old RPi-B has only one PWM pin, which is insufficient for keeping two robot wheels in sync, running an X and Y axis on a CNC machine, etc. Even one more PWM would be great. A total of four would be better.

  • Did they fix the USB problems ?
    • by Dave Whiteside ( 2055370 ) on Monday July 14, 2014 @10:48AM (#47448577)

      yes as long as your input power adapter is decent
      the B+ can provide upto 1200 mA
      see
      http://www.raspberrypi.org/for... [raspberrypi.org]

    • by Anonymous Coward on Monday July 14, 2014 @12:33PM (#47449397)

      Did they fix the USB problems ?

      The B+ redesign fixed the power problems, but not the core data loss.

      The core problems of USB can't be fixed in B+, because the new board still uses the same old Broadcom BCM2835 SoC with its minimalist (only partial) USB controller. That's the reason for USB events being dropped when the ARM is busy and can't service the USB interrupts fast enough.

      That SoC was never intended to support full USB operation on a general purpose computer, only light applications like plugging a flash drive into a set top box. Its use in Roku 2 is typical.

      As a consequence of the SoC, the core USB problems won't disappear until a new SoC is chosen for a next generation Raspberry Pi.

  • It sounds like they added more GPIO to make it more competitive with the BeagleBone Black but it still has an outdated CPU with fading support.
  • The addition of 2 extra USB ports is useless, unless they have changed the polyfuse set up to allow more power to be delivered to the ports. As things currently stand with the original model B, attaching anything more than a low-power keyboard to the Pi requires a powered hub -- the Pi itself can't deliver the required juice. It would be great if this restriction were lifted.

  • Great for GPIO, power supply, and USB. My only real concern is that the ethernet port is on USB. If you're like me and prefer the stability of ethernet, be advised that using ethernet will not only be slower but it will tax the CPU since USB relies on CPU power to operate. Not that this would be much different from using USB WiFi adapters, but it's something to keep in mind about the Pi.

  • Comment removed based on user account deletion
  • Ill-named? (Score:3, Funny)

    by Anonymous Coward on Monday July 14, 2014 @11:23AM (#47448863)

    FYI: in Hungary, B+ is the abbreviation of "f*ck you". So you've made our day.

  • Lets be honest: The Raspberry Pi is designed by amateurs and has numerous problems. Most noticeable was the hugely unreliable USB and the atrociously faked audio-out. But things like that nobody could tell whether the GPIOs are actually 5V tolerant due to missing critical portions of the data-sheet and the decision for a closed-documentation chip in the first place are at best on high amateur-level. It seems they finally fixed at least a part of their screwups.

    In addition, I found the Raspberry Pi "communit

Get hold of portable property. -- Charles Dickens, "Great Expectations"

Working...