Products > Test Equipment
open source GPIB adapter
deepfryed:
--- Quote from: dazz1 on November 11, 2023, 08:31:12 pm ---I am now stuck on what to do next. I understand this is a copy command, but I can't figure out what my destination should be. I was expecting another avrdude command at this point.
--- Code: --- cp TestAndMeasurement.bin /run/media/baettig/GPIBUSBBOOT/FLASH.BIN
--- End code ---
# verify with md5sum, umount, unplug
--- End quote ---
Did you see the note re. Linux on the README ?
--- Quote ---On Linux, there is a bug with the LUFA mass storage that means it is required to use
--- Code: ---dd if=TestAndMeasurement.bin of=/mnt/FLASH.BIN bs=512 conv=notrunc oflag=direct,sync
--- End code ---
--- End quote ---
dazz1:
--- Quote from: deepfryed on November 11, 2023, 09:24:48 pm ---
Did you see the note re. Linux on the README ?
--- End quote ---
Yes, I did not see the note.
--- Quote from: deepfryed on November 11, 2023, 09:24:48 pm ---
--- Code: ---dd if=TestAndMeasurement.bin of=/mnt/FLASH.BIN bs=512 conv=notrunc oflag=direct,sync
--- End code ---
--- End quote ---
The dd command is one I only use as the option of last resort.
I think the root of my problem is a dumb assumption. I assumed that the initial firmware would be all loaded via the programmer.
I now see that the process requires the programming of the the boot loader via the ISP connector, followed by copying the firmware via the usb connector.
OK so I have connected Win10 (dual-boot PC) to the usb-gpib usb-C connector. I see:
--- Code: ---GPIBUSBBOOT(D:)
EEPROM.BIN 1KB
FLASH.BIN 24KB
--- End code ---
So that looks like it is working.
Then I tried copying TestandMeasurement.bin via the usb connector and got the error message in the attached image.
FLASH.BIN is taking up all the space.
For me, it makes no sense to re-program via the USB port.
To enable the boot loader to load new firmware, I need to remove the enclosure and short two pins on the ISP connector. Then download the firmware via the usb connector using the data destroyer dd command or Win10 copy.
If I re-program the firmware via the ISP connector, I need to remove the enclosure and plug in my usbasp programmer using the benign avrdude program.
To use the usb connector really requires an externally accessible push switch to short the ISP pins without removing the enclosure. I did look at this option when designing my PCB but did not include one. I think I will add that option on the pcb (fit for but not with).
I have make progress. I have confirmed:
the ISP works,
the usb-C works,
the MCU works.
but I have not yet been able to load the usb-gpib firmware. I am still doing something wronng.
deepfryed:
In theory, you could use the arduino style bootloader and just program directly from USB without shorting any pins. I'm not sure why the flash bootloader was chosen :-//
dazz1:
--- Quote from: deepfryed on November 12, 2023, 01:04:05 am ---In theory, you could use the arduino style bootloader and just program directly from USB without shorting any pins. I'm not sure why the flash bootloader was chosen :-//
--- End quote ---
Right now I am just trying to get the firmware installed and running. I plan to modify the software to run the two status LEDs because two LEDs is always better than one.
dazz1:
I am thinking if I don't install (delete) FLASH.BIN, I will have enough space for the usb-gpib firmware. My understanding of the software is that the FLASH.BIN code is only called if the 2 pins on the ISP connector are shorted.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version