Home of the Squeezebox™ & Transporter® network music players.
Page 2 of 2 FirstFirst 12
Results 11 to 19 of 19
  1. #11
    Senior Member paul-'s Avatar
    Join Date
    Jan 2013
    Posts
    611
    That is a pretty old config we should probably update it.

    I would use that file, but delete everything after the wifi stuff. So the contents of your newconfig.cfg would be

    Code:
    #########################
    # Edit the variables below to setup a wifi based system without LAN access
    # Change Wifi to "on". Valid options for Encryption are "WEP", "WPA" or "OPEN" 
    WIFI="off"
    SSID="wireless"
    PASSWORD="password"
    ENCRYPTION="WPA"
    # End Wifi setup
    ##########################

  2. #12
    Senior Member
    Join Date
    Feb 2009
    Location
    London, UK
    Posts
    522
    Quote Originally Posted by cpd73 View Post
    Hmm... Not working for me. Just to confirm I have done the following:

    1. Flashed PCP 3.11 to SDCard
    2. Mounted the 'PCP' volume in Ubuntu
    3. Deleted all dtb files from 'PCP'
    4. Copied bcm2708-rpi-0-w.dtb, bootcode.bin, fixup.dat, fixup_cd.dat, fixup_x.dat, start.elf, start_cd.elf start_x.elf from 2017-03-02-raspbian-jessie-lite.img
    5. Downloaded newconfig.cfg from PCP google.site
    6. Edited newconfig.cfg to turn wifi on, set SSID and password, encryption to WPA
    7. Put newconfig.cfg onto 'PCP' volume
    8. Put SD Card in Pi
    9. Boot Pi - green light illuminates, and stays on
    10. Checked on my router, and no new IPs registered :-(
    11. newconfig.cfg still remains on SDCard - should PCP not remove this on startup?


    Should the above work? Have I missed a step?
    Hi cpd73,

    This is exactly what I did. The only thing I have noticed though is that it takes a little bit for the RPiZero W to get an IP address assigned.

    EDIT: I have also left the newconfig.cfg on the card. I am not being funny but did you make sure you put the right parameters in the newconfig.cfg? If you get a chance I would recommend you to connect the RPi to a screen/TV to see if it boots up properly.
    Last edited by albertone74; 2017-03-12 at 15:39.

  3. #13
    Senior Member
    Join Date
    Feb 2009
    Location
    London, UK
    Posts
    522
    Quote Originally Posted by Sylvania View Post
    Hi

    Explanation :-) "removed the blacklist=brcmfmac from cmdline.txt"

    I read somewhere that the driver needed to be blacklisted in the cmdline.txt.. that's it :-)

    just copy bcm2708-rpi-0-w.dtb, bootcode.bin and all dat/elf files
    Thanks again for sharing your results!

  4. #14
    Junior Member
    Join Date
    Mar 2017
    Posts
    4
    Quote Originally Posted by albertone74 View Post
    Hi cpd73,

    This is exactly what I did. The only thing I have noticed though is that it takes a little bit for the RPiZero W to get an IP address assigned.

    EDIT: I have also left the newconfig.cfg on the card. I am not being funny but did you make sure you put the right parameters in the newconfig.cfg? If you get a chance I would recommend you to connect the RPi to a screen/TV to see if it boots up properly.
    I've tried the steps again, this time just having the required fields in newconfig.cfg. Now the Pi flashes for a bit at start-up (for 10 seconds?) - and then the light stays on. newconfig.cfg is now being removed - but still no IP address. Would try with a screen but I don't have a mini-hdmi cable.

    Is the activity light supposed to remain green? Or does this mean the Pi has crashed? Perhaps I should try a new SDCard - but fsck shows no errors.

    EDIT: OK, not sure what changed - but its now connecting! Thanks for all your help.
    Last edited by cpd73; 2017-03-12 at 16:47.

  5. #15
    Junior Member
    Join Date
    Mar 2017
    Posts
    1
    Hi I'm a new user of picoreplayer and pizero-w.

    I follow the instructions and copied files from raspbian to picoreplayer.
    I also create a newconfig.cfg file to auto configure wifi but I always receive this message during boot :

    Attempting auto connection with AZERTY
    error for wireless request "Set ESSUD" (8B1A) :
    too few arguments.


    I edit the file with VI on another picoreplayer with ethernet.

    The file is joined within the post.

    thx
    Attached Files Attached Files

  6. #16
    Junior Member
    Join Date
    Mar 2017
    Posts
    3
    After copying all the files, the WLAN is working, but the pHAT DAC (as HIFIBERRY DAC) doesnt work any more. Someone any idea

  7. #17
    Senior Member paul-'s Avatar
    Join Date
    Jan 2013
    Posts
    611
    pCP 3.11 does not officially support the ZeroW. Feel free to hack.

    The zero uses the same chip, firmware and drivers as the rpi3B. So all of the compatibility issues with i2s still apply.

  8. #18
    Junior Member
    Join Date
    Mar 2017
    Posts
    5
    Hi

    I did a clean install today.. did exactly as last time , but didn't check the cmdline.txt .
    No ip this time. Checked the cmdline.txt and it has blacklist=brcmfmac at the end. Remove it and reboot.
    Picoreplayer gets it ip :-)

    Best regards

  9. #19
    Junior Member
    Join Date
    Mar 2017
    Posts
    5
    Quote Originally Posted by Wetty View Post
    After copying all the files, the WLAN is working, but the pHAT DAC (as HIFIBERRY DAC) doesnt work any more. Someone any idea
    I'm using a pHAT DAC ( pcm5102a ) with my Pi ZeroW , Picoreplayer setup to generic "PCM51XX" , and working :-)

    best regards

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •