Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
projects:chipkit32 [2016/02/17 12:20] – [chipKIT32 boot loader] darronprojects:chipkit32 [2021/10/28 02:39] (current) – [Build] darron
Line 14: Line 14:
 the freeware chipKIT [[:tools:xc32|MPIDE]] compiler instead. the freeware chipKIT [[:tools:xc32|MPIDE]] compiler instead.
  
-This fork also introduces support for the MX270 processor and for chipKIT Pi's +This fork also introduces support for the MX270 processor and also the removal 
-attached directly to the RPi, the removal of the requirement to press +of the requirement to press BOOTLOAD-EN to upload firmware, just a reset will 
-BOOTLOAD-EN to upload firmware, just a reset will do (3 seconds time-out).+do.
 === Build === === Build ===
  
Line 51: Line 51:
 If the USB firmware is loaded onto the chipKIT Pi then it no longer needs to be attached to the RPi to operate, however, it cannot stand upright (top picture). If the USB firmware is loaded onto the chipKIT Pi then it no longer needs to be attached to the RPi to operate, however, it cannot stand upright (top picture).
  
-If the chipKIT Pi is attached to the RPi and it'USB port is connected to a powered hub then it may power the complete unit (2nd top picture). In this configuration the RPi can be made into a USB device with some programming. Please note that the RPi is powered via the GPIO header in this configuration. Do not connect the RPi micro-usb power simultaneously.+If the chipKIT Pi is attached to the RPi and its USB port is connected to a powered hub then it may power the complete unit (2nd top picture). In this configuration the RPi can be made into a USB device with some programming. Please note that the RPi is powered via the GPIO header in this configuration. Do not connect the RPi micro-usb power simultaneously.
  
 The breadboard firmwares are the only ones which don't require a crystal. The target device is the MX250 with the internal oscillator at 40MHz. The pin configuration is the same as the chipKIT Pi. The 9600 version operates at 9600 baud for upload rather than the standard 115200 baud. The breadboard firmwares are the only ones which don't require a crystal. The target device is the MX250 with the internal oscillator at 40MHz. The pin configuration is the same as the chipKIT Pi. The 9600 version operates at 9600 baud for upload rather than the standard 115200 baud.
  
-One major difference between this firmware and the original is that for the serially attached chipKIT Pi (not USB) the BOOTLOAD-EN button is disabled in the boot loader and instead the boot loader will to wait for 3 seconds after reset for an upload. [[:projects:pickle|Pickle's]] `pctrl restore' may be used to reset the chip.+One difference between this firmware and the original is that the BOOTLOAD-EN button is disabled in the boot loader and instead the boot loader will wait a moment after reset for an upload. [[:projects:pickle|Pickle's]] `pctrl restore' may be used to reset the chip when the chipKIT Pi is attached to a RPi. 
 === ICSP === === ICSP ===
  
Line 88: Line 89:
 PGC=14 PGC=14
 PGD=15 PGD=15
-PGM=255+PGM=-1
 </code> </code>
  
Line 123: Line 124:
 We can upload an LED demo to the bootloader firmware installed above. We can upload an LED demo to the bootloader firmware installed above.
  
-First ensure that the serial [[interfaces:amba|UART]] is free to use.+First ensure that the serial [[interfaces:amba|UART]] is free (not USB boot loader).
  
 To enter upload mode, perform the following steps. To enter upload mode, perform the following steps.
  
-   - Press BOOTLOAD-EN 
    - Press RESET    - Press RESET
    - Release RESET    - Release RESET
-   - Release BOOTLOAD-EN 
  
-Steps 2 and 3 above may also be replaced with `pctrl restore'. For the breadboard edition, the BOOTLOAD-EN steps are omitted.+When attached to an RPi reset may be performed with `pctrl restore' rather than pressing the reset button.
  
 For the MX250. For the MX250.
Line 158: Line 157:
 cdc_acm 1-1.1.4:1.0: ttyACM0: USB ACM device cdc_acm 1-1.1.4:1.0: ttyACM0: USB ACM device
 </code> </code>
 +