mahjongg wrote:sound to me you should return your B+ under warranty, looks like outputting a "1" on GPIO38 causes a short somehow, that the only reasonable explanation I can think off.
I expect to return it but want to confirm that it is a hardware fault first, hence my registering and posting here. The concensus here does seem to be that there is a fault.
I have looked closely over the board with a 10x loupe and can see nothing obvious, nothing fried, no solder whiskers etc. There are no bent or crossed pins in any of the connector sockets. (It occurred to me overnight that perhaps it is a keyboard or even LAN fault, can't be bothered to set it all up now but I will try with just monitor and power later.)
Even so I don't think I can be 100% sure until my new B+ arrives, hopefully later today, and I can test that with my existing SD image. Until then it could still be PSU or even user error - I've been running linux for well over 10 years but I'm probably not unique in making the silliest of mistakes and not being able to see them for looking!
I hate to jump in with all the knowledge in this thread, but surely one of the parameters should have no effect at all? Is it an invalid syntax problem in config.txt possibly? Or does the newer firmware accept either or?
It's not a syntax issue, I have checked that so
I have tried the parameters, both individually and together, as
was only introduced in later updates and I wasn't sure whether it applied in my case or whether I should be using the older
When I received my B+ on 19th July, shortly after its release, I couldn't be sure that the various versions of raspbian I was trying were fully up to date - I suspect not - and Im still uncertain of the interaction between a 'raspbian' raspbian install and rpi-update (as opposed to a NOOBS raspbian).
I have not come across anything definitive about it but my guess was that might
have caused an error in code that didn't support it and that it is likely that might
be still supported for some time to come.