More fun with the ChipKit uC32 and the Dragino YUN shield

Created Mon, 06 Feb 2017 06:23:27 +0000 by ltheoret

ltheoret

Mon, 06 Feb 2017 06:23:27 +0000

Hi,

I have upgraded the firmware in one of my Dragino YUN Shields to the new version 4.1.1. The good news is the bridge still works as before. but again I cannot program my chipkits.

Here is the link that works with version up to 2.0.7. if the Dragino and the chipkit. [url]http://chipkit.net/forum/viewtopic.php?f=18&[/url]

Here is the like to the Dragino forum where I got the update. [url]https://groups.google.com/forum/#!topic/dragino-user/W-m_gsDKXSU[/url]

Any help would be appreciated.

Luc

majenko

Mon, 06 Feb 2017 13:24:30 +0000

In what way can you not program the chipkits at the moment? What method are you using, and what errors if any do you get?

ltheoret

Mon, 06 Feb 2017 21:11:54 +0000

Hi majenko,

I upgraded my Dragino YUN shield from version 2.0.7 to version 4.1.1. Then I installed python-MySQL. Then I tested by preloading the ChipKit uC32 with my MySQL test sketch. everything worked, the test data showed up on a remote database.

The I installed your pic32prog software following the instructions on this blog: [url]https://hackingmajenkoblog.wordpress.com/2016/02/24/dragino-chipkit-yun-yum[/url]

I pre-loaded the same board again with Blink from the USB with UECIDE, to avoid bridge conflicts as it would not program through the Dragino YUN shield.

Then I ran UECIDE with the upload via Dragino as target and uC32 as the board.

This is the output of UECIDE:

Compiling...
• Compiling sketch...
• Compiling core...
‣ api
• Compiling libraries...
• Linking sketch...
Compiling done.
Memory usage
• Program size: 6656 bytes
• Memory size: 996 bytes
• Compilation took 2.046 seconds
Uploading firmware...
Uploading firmware image... 
Programming target... 
killall: init: no process killed
grep: /proc//status: No such file or directory
sh: you need to specify whom to kill
sh: you need to specify whom to kill
Programmer for Microchip PIC32 microcontrollers, Version 2.0
    Copyright: (C) 2011-2015 Serge Vakulenko

Looking at the boards: first the Dragino YUN shield: The Green PWR and White SYS LED are on solid. The Blue WLAN LED is blinking non stop.

On the ChipKit uC32: The green LED5 is on solid The green LED4 is blinking fast non stop Unfortunately I do not see the 2 Red LEDs 1 and 2 the RX and TX?

on it stays hung in that state.

Luc

ltheoret

Mon, 06 Feb 2017 21:14:13 +0000

hi,

Forgot to mention the jumper from ICSP pin 5 to the RST pin is still on.

Luc

majenko

Mon, 06 Feb 2017 23:18:27 +0000

It looks like /proc may not be mounted. Not sure how you'd go about doing that on that version...

I'll have to download the update and see if I can get my Dragino going with it...

ltheoret

Tue, 07 Feb 2017 19:58:39 +0000

Hi, One word of caution when upgrading the Dragino to version 4.1.1. Attached is a dump of two Draginos, one with version 4.1.1 on the left and the other with version 2.0.7 on the right. with version 2.0.7 you get 5.6Mb of space to work with about 860kb used. with version 4.1.1 you get 1.1Mb of space to work with about the same used. The core is a lot bigger leaving less room for your packages.

Note: both Draginos have python-MySQL installed.

Luc

majenko

Tue, 07 Feb 2017 22:13:47 +0000

The first thing I always do with any OpenWRT system is to shift /overlay onto an SD or USB flash drive. Gives you gigs of space for your packages then.

https://wiki.openwrt.org/doc/howto/extroot

ltheoret

Wed, 08 Feb 2017 04:53:14 +0000

Hi majenko,

Thank you for the suggestion. My problem is, I bought a pack of 8Gb SanDisk USB sticks, but non of them are bootable. Do the USB stick have to be bootable?

With the raspberry pi non of my SanDisk SD cards work it, it only works with Kinston SD cards.

Luc

majenko

Wed, 08 Feb 2017 11:42:35 +0000

No, USB sticks don't need to be bootable for extroot. It boots off the internal flash as per normal then, instead of mounting the internal flash spare space as /overlay (which is then "overlaid" over root) it mounts the SD or USB drive instead.

Early Pis had terrible problems with SD card compatibility. Newer ones are much better. The first Pi boards that came out would only work with a small handful of cards. It was such a sorry mess that you could (and still can) buy Pi specific cards. The Pi is the only device I have ever known to suffer from such shoddy coding as that. I think it was partly because the boot.elf was completely closed source and written by Broadcom (who are completely useless when writing such things - I mean, look at the fiasco I had with their USB WiFi dongles...). I have never know a card (except one that is actually dead and doens't work at all) not work on a Dragino or Yun or any other embedded system.

ltheoret

Mon, 13 Feb 2017 04:21:30 +0000

Hi, Am I the only one using the Dragino shield with the ChipKit boards?

Luc

majenko

Mon, 13 Feb 2017 11:03:20 +0000

I think there is only you and me. I have dug my Dragino out, but not got round to doing the firmware upgrade yet... too many things happening around here right now...