WIPy 2.0 arrived- can't see it on MacBook Pro running Mavericks



  • I've got a Micropython Pyboard v1.1 which works fine with my Macbook, running OSX Mavericks.

    I've just received my WiPy 2.0 & expansion board, plugged it into the Mac using the same cable that I used with the Pyboard. /ttyusbmodemxxxx does not appear in /dev.

    Is anything else needed to see this device on OSX?
    Do I need to change any jumper settings on the expansion board?
    I'm getting power to the board, the blue LED is flashing about once a second, and the orange LED is on solid.

    Thanks


  • administrators

    This post is deleted!


  • @abilio said in WIPy 2.0 arrived- can't see it on MacBook Pro running Mavericks:

    Can you try a Windows 10 machine, or a linux machine (even in virtualbox will be ok) in order to dismiss the last option?. We just need to see if the board is detected or not.

    I'll try installing the FTDI USB driver manually.

    I've mentioned in another post that I was able to update the FW using a Windows machine. So, we know that the hardware on the Wipy is working.

    BTW- Do I also need the G23-GND jumper on the Mac?
    If so, then I didn't have that installed when I plugged the WiPy in before.

    I'm sorry I cannot try it myself, but we don't have any Mavericks computer available at our offices. I'll be waiting for your feedback.
    Can you try installing Mavericks in a VM?



  • @cappy2112, that dump should contain the string AppleUSBFTDI when the driver is being loaded for the new USB device. As far as I know, the driver is contained by default in Mavericks, so this means one of three things:

    • I'm mistaken and the AppleUSBFTDI is not included in Mavericks.
    • The version included is incomplete or doesn't support the chip (see this article for the incomplete part)
    • The expansion board really is defective.

    Can you try a Windows 10 machine, or a linux machine (even in virtualbox will be ok) in order to dismiss the last option?. We just need to see if the board is detected or not.

    Other option will be disabling the stock driver (as the article describes), and installing the ones from the chip manufacturer (get them here).

    I'm sorry I cannot try it myself, but we don't have any Mavericks computer available at our offices. I'll be waiting for your feedback.



  • @abilio

    Dmesg output WITH the Wipy connected to the expansion board.

    ARNING: hibernate_page_list_setall skipped 10994 xpmapped pages
    hibernate_page_list_setall preflight pageCount 380474 est comp 37 setfile 629145600 min 1073741824
    [0xea956000, 0x2e0d1000]
    [0xb588f000, 0xe000000]
    [0x39848b8000, 0x3f2f000]
    [0x0, 0x0]
    kern_open_file_for_direct_io(0) took 1 ms
    Opened file /var/vm/sleepimage, size 1073741824, partition base 0x0, maxio 2000000 ssd 1
    hibernate image major 1, minor 0, blocksize 4096, pollers 5
    vm_compressor_record_warmup (35223 - 41003)
    vm_compressor_flush - starting
    vm_compressor_flush completed - took 22393 msecs
    hibernate_flush_memory: buffer_cache_gc freed up 7122 wired pages
    hibernate_alloc_pages act 66884, inact 43441, anon 789, throt 0, spec 54661, wire 399880, wireinit 306702
    hibernate_setup(0) took 25973 ms
    en1: BSSID changed to dc:7f:a4:0b:72:1a
    wlEvent: en1 en1 Link DOWN virtIf = 0
    AirPort: Link Down on en1. Reason 8 (Disassociated because station leaving).
    0 [Time 1478016838] [Message hibernate_page_list_setall(preflight 0) start 0xffffff8328ff6000, 0xffffff8329076000
    hibernate_teardown started
    hibernate_teardown: wired_pages 399857, free_pages 3722102, active_pages 21371, inactive_pages 18629, speculative_pages 0, cleaned_pages 0, compressor_pages 85
    hibernate_teardown_pmap_structs done: last_valid_compact_indx 221847
    hibernate_teardown: mark_as_unneeded_pages 8192, 62686, 34597
    hibernate_teardown completed - discarded 105475
    hibernate_page_list_setall time: 991 ms
    pages 435980, wire 270909, act 21371, inact 18629, cleaned 0 spec 0, zf 0, throt 0, compr 85, xpmapped 40000
    did discard act 35326 inact 24812 purgeable 10187 spec 54661 cleaned 0
    WARNING: hibernate_page_list_setall skipped 11268 xpmapped pages
    hibernate_page_list_setall found pageCount 310994
    IOHibernatePollerOpen, ml_get_interrupts_enabled 0
    IOHibernatePollerOpen(0)
    encryptStart 14020
    bitmap_size 0x7f4dc, previewSize 0x4e5700, writing 309406 pages @ 0x578bfc
    hibernate_rebuild started
    hibernate_rebuild_pmap_structs done: last_valid_compact_indx 221847
    hibernate_rebuild completed - took 110 msecs
    booter start at 1575 ms smc 0 ms, [13, 0, 0] total 2025 ms, dsply 0, 0 ms, tramp 887 ms
    hibernate_machine_init: state 2, image pages 270706, sum was 1af9f800, imageSize 0x1cd67000, image1Size 0x135d2000, conflictCount 2522, nextFree a7e
    hibernate_newruntime_map time: 0 ms, IOHibernatePollerOpen(), ml_get_interrupts_enabled 0
    IOHibernatePollerOpen(0) 16 ms
    hibernate_machine_init reading
    PMStats: Hibernate read took 558 ms
    hibernate_machine_init pagesDone 310791 sum2 5c1a6bce, time: 558 ms, disk(0x20000) 279 Mb/s, comp bytes: 52613120 time: 51 ms 980 Mb/s, crypt bytes: 158945280 time: 70 ms 2153 Mb/s
    Wake reason: EC.LidOpen (User)
    vm_compressor_fastwake_warmup (35223 - 41003) - starting
    AirPort_Brcm43xx::powerChange: System Wake - Full Wake/ Dark Wake / Maintenance wake
    Previous Sleep Cause: 5
    Previous Shutdown Cause: 5
    AppleThunderboltHAL::earlyWake - complete - took 18 milliseconds
    Thunderbolt Self-Reset Count = 0xedefbe00
    TBT W (1): 0 [x]
    IOBluetoothUSBDFU::probe
    IOBluetoothUSBDFU::probe ProductID - 0x821D FirmwareVersion - 0x0150
    **** [IOBluetoothHostControllerUSBTransport][start] -- completed -- result = TRUE -- 0x0800 ****
    **** [BroadcomBluetoothHostControllerUSBTransport][start] -- Completed -- 0x0800 ****
    [IOBluetoothHCIController][staticBluetoothHCIControllerTransportShowsUp] -- Received Bluetooth Controller register service notification -- 0x0800
    [IOBluetoothHCIController::setConfigState] calling registerService
    **** [IOBluetoothHCIController][protectedBluetoothHCIControllerTransportShowsUp] -- Connected to the transport successfully -- 0x9040 -- 0xc800 -- 0x0800 ****

    IOHIDDevice::newUserClient called on an inactive device
    IOHIDDevice::newUserClient called on an inactive device
    IOHIDDevice::newUserClient called on an inactive device
    IOHIDDevice::newUserClient called on an inactive device
    IOHIDDevice::newUserClient called on an inactive device
    **** [IOBluetoothHostControllerUSBTransport][SuspendDevice] -- Suspend -- suspendDeviceCallResult = 0x0000 (kIOReturnSuccess) -- 0x0800 ****

    MacAuthEvent en1 Auth result for: dc:7f:a4:0b:72:1a MAC AUTH succeeded
    wlEvent: en1 en1 Link UP virtIf = 0
    AirPort: Link Up on en1
    en1: BSSID changed to dc:7f:a4:0b:72:1a
    AirPort: RSN handshake complete on en1
    flow_divert_kctl_disconnect (0): disconnecting group 1
    vm_compressor_fastwake_warmup completed - took 13171 msecs
    Google Chrome He (map: 0xffffff8061ea50f0) triggered DYLD shared region unnest for map: 0xffffff8061ea50f0, region 0x7fff93c00000->0x7fff93e00000. While not abnormal for debuggers, this increases system memory footprint until the target exits.
    pci pause: SDXC
    Google Chrome He (map: 0xffffff8056fc9690) triggered DYLD shared region unnest for map: 0xffffff8056fc9690, region 0x7fff93c00000->0x7fff93e00000. While not abnormal for debuggers, this increases system memory footprint until the target exits.
    Google Chrome He (map: 0xffffff8062f34870) triggered DYLD shared region unnest for map: 0xffffff8062f34870, region 0x7fff93c00000->0x7fff93e00000. While not abnormal for debuggers, this increases system memory footprint until the target exits.
    Google Chrome He (map: 0xffffff8062f34870) triggered DYLD shared region unnest for map: 0xffffff8062f34870, region 0x7fff93c00000->0x7fff93e00000. While not abnormal for debuggers, this increases system memory footprint until the target exits.
    Limiting closed port RST response from 354 to 250 packets per second
    Google Chrome He (map: 0xffffff80512e6000) triggered DYLD shared region unnest for map: 0xffffff80512e6000, region 0x7fff93c00000->0x7fff93e00000. While not abnormal for debuggers, this increases system memory footprint until the target exits.
    Google Chrome He (map: 0xffffff80512e6000) triggered DYLD shared region unnest for map: 0xffffff80512e6000, region 0x7fff93c00000->0x7fff93e00000. While not abnormal for debuggers, this increases system memory footprint until the target exits.
    Google Chrome He (map: 0xffffff8054737e10) triggered DYLD shared region unnest for map: 0xffffff8054737e10, region 0x7fff93c00000->0x7fff93e00000. While not abnormal for debuggers, this increases system memory footprint until the target exits.



  • @abilio
    Here is the output of dmesg, with just the Expansion board connected

    m_compressor_fastwake_warmup (35223 - 41003) - starting
    AirPort_Brcm43xx::powerChange: System Wake - Full Wake/ Dark Wake / Maintenance wake
    Previous Sleep Cause: 5
    Previous Shutdown Cause: 5
    AppleThunderboltHAL::earlyWake - complete - took 18 milliseconds
    Thunderbolt Self-Reset Count = 0xedefbe00
    TBT W (1): 0 [x]
    IOBluetoothUSBDFU::probe
    IOBluetoothUSBDFU::probe ProductID - 0x821D FirmwareVersion - 0x0150
    **** [IOBluetoothHostControllerUSBTransport][start] -- completed -- result = TRUE -- 0x0800 ****
    **** [BroadcomBluetoothHostControllerUSBTransport][start] -- Completed -- 0x0800 ****
    [IOBluetoothHCIController][staticBluetoothHCIControllerTransportShowsUp] -- Received Bluetooth Controller register service notification -- 0x0800
    [IOBluetoothHCIController::setConfigState] calling registerService
    **** [IOBluetoothHCIController][protectedBluetoothHCIControllerTransportShowsUp] -- Connected to the transport successfully -- 0x9040 -- 0xc800 -- 0x0800 ****

    IOHIDDevice::newUserClient called on an inactive device
    IOHIDDevice::newUserClient called on an inactive device
    IOHIDDevice::newUserClient called on an inactive device
    IOHIDDevice::newUserClient called on an inactive device
    IOHIDDevice::newUserClient called on an inactive device
    **** [IOBluetoothHostControllerUSBTransport][SuspendDevice] -- Suspend -- suspendDeviceCallResult = 0x0000 (kIOReturnSuccess) -- 0x0800 ****

    MacAuthEvent en1 Auth result for: dc:7f:a4:0b:72:1a MAC AUTH succeeded
    wlEvent: en1 en1 Link UP virtIf = 0
    AirPort: Link Up on en1
    en1: BSSID changed to dc:7f:a4:0b:72:1a
    AirPort: RSN handshake complete on en1
    flow_divert_kctl_disconnect (0): disconnecting group 1
    vm_compressor_fastwake_warmup completed - took 13171 msecs
    Google Chrome He (map: 0xffffff8061ea50f0) triggered DYLD shared region unnest for map: 0xffffff8061ea50f0, region 0x7fff93c00000->0x7fff93e00000. While not abnormal for debuggers, this increases system memory footprint until the target exits.
    pci pause: SDXC
    Google Chrome He (map: 0xffffff8056fc9690) triggered DYLD shared region unnest for map: 0xffffff8056fc9690, region 0x7fff93c00000->0x7fff93e00000. While not abnormal for debuggers, this increases system memory footprint until the target exits.
    Google Chrome He (map: 0xffffff8062f34870) triggered DYLD shared region unnest for map: 0xffffff8062f34870, region 0x7fff93c00000->0x7fff93e00000. While not abnormal for debuggers, this increases system memory footprint until the target exits.
    Google Chrome He (map: 0xffffff8062f34870) triggered DYLD shared region unnest for map: 0xffffff8062f34870, region 0x7fff93c00000->0x7fff93e00000. While not abnormal for debuggers, this increases system memory footprint until the target exits.
    Limiting closed port RST response from 354 to 250 packets per second
    Google Chrome He (map: 0xffffff80512e6000) triggered DYLD shared region unnest for map: 0xffffff80512e6000, region 0x7fff93c00000->0x7fff93e00000. While not abnormal for debuggers, this increases system memory footprint until the target exits.
    Google Chrome He (map: 0xffffff80512e6000) triggered DYLD shared region unnest for map: 0xffffff80512e6000, region 0x7fff93c00000->0x7fff93e00000. While not abnormal for debuggers, this increases system memory footprint until the target exits.



  • Hi @cappy2112, I'll reply to all your previous posts.

    The WiPy/Lopy boards run MicroPython, but their hardware was designed from scratch. You're right, the docs statement is wrong. We inherited the micropython documentation, and we're working hard to update the docs to reflect Pycom specific things.

    On Mac, the expansion board should show up as: /dev/tty.usbserial-XXXXXXXX, even without any WiPy/LoPy connected to it. Can you try connecting the cable and run the following command right after:

    sudo dmesg
    

    Something like: AppleUSBFTDI should show up. I have no access to a Mavericks installation, but as far as I know it includes the FTDI chip out of the box.

    Do you have access to any other computer, so we can rule out is not the hardware?

    PS: on Linux, it will appear as /dev/ttyUSB#, and on Windows, as a COM port (Windows 7 needs additional drivers).



  • @abilio

    This page https://docs.pycom.io/wipy2/2wipy/tutorial/repl.html

    also refers to the WiPy device as "/dev/tty.usbmodem*"



  • @abilio

    I see no change in /dev after plugging in the WiPy 2.0 on my Macbook Pro.

    Are you sure it's tty.usbserial?

    When I plug the Micropython Pyboard into my Mac, it shows up as dev/tty.usbmodem1412

    Are not the Wipy, Lopy, etc, derived from MicroPython?

    I'm using the same cable with the WiPy, as when I connected the Micropython Pyboard.
    Also, I was able to update the FW on the Wipy today, on a Windows machine, so I know the WiPy is somewhat functional.

    This really confuses me.



  • @pwest
    You're correct- once every 4 seconds is right..

    I was confusing the WiPy with my Micropython Pyboard v 1.1



  • Yeah @pwest, I misread that part. it should be around 4 seconds per beat. Can you confirm me that /dev/tty.usbserial is not appearing. These are two independent things, so let's first iron the issue with the communication.



  • @abilio said in WIPy 2.0 arrived- can't see it on MacBook Pro:

    The LED flashing once a second is the expected behavior of a board running fine :)

    Really? The docs at https://docs.pycom.io/wipy2/2wipy/general.html state:
    By default the heartbeat LED flashes in blue color once every 4s to signal that the system is alive.
    Which is consistent with what I see with mine. Once every second sounds wrong.



  • Hi @cappy2112. Expansion boards normally appear as /dev/tty.usbserial-XXXXXXXX. Can you confirm it's presence?

    The LED flashing once a second is the expected behavior of a board running fine :)


Log in to reply
 

Looks like your connection to Pycom Forum was lost, please wait while we try to reconnect.