「NDOT」カテゴリーアーカイブ

old NDOT related

NDOT firmware SC&AD -C

NDOT
  1. onAVRdragon: spare C (This was porgrammed @edco@2019.07
  2. (mega164P) sig: 0x1E 0x94 0x0A;fuse read: 0xF7, 0x99, 0xFF; means:JTAGEN,SPIEN,Fullswing Xtal 16Kclk+65ms, lockbit read: 0xFF;
  3. onAVRdragon:2019-07-12-2(programmed @edco@2019-07)
  4. (mega164P) sig: 0x1E 0x94 0x0A;fuse read : 0xF7, 0x99, 0xFF; means:JTAGEN,SPIEN,Fullswing Xtal 16Kclk+65ms, lockbit read: 0xFF;
  5. onAVRdragon: SCAD-U4-C 04/30 8(programmed @2010?/04-30)
  6. (mega164P) sig read: 0x1E 0x94 0x0A;fuse read:0xF7,0xD9,0xFF;meansSPIE, Fullswing Xtal 16Kclk+65ms; lockbit read: 0xFF;
  7. Note@2010/01/06 says:mega164Pfuse:high byte: default 0x99 (may not work) ,JTAG disabled 0xD9 (This is safer)
  8. Above check and discussion explains why new SCAD mega164P did not work!!

AVR Dragon on Kiyoshi(xp)

NDOT、NSDOT、programming
  1.  Connect AVR Dragon (Parallel wiring intact, ISP 2pin 5V wired): big Red, small Green lit.  AVR Dragon is on the device manager: Jungo section.  Yet cannot open usb connection on Flip3.3.4.
  2.  AVR studio4: debugplatform:AVR Dragon, Device ATmega164P:finish;
  3. Tools->Program AVR->(Select AVR programmer)AVR Dragon, usb: ->connect
  4.  (source file should be selected):window(AVR Dragon in PP/HVSP mode with ATmega164P) will popup.
  5.  Click necessary action, checking the messages OK!.

SC&AD PCB

debian、NDOT

SC&AD input sectionのanalog groundは分離すべきだった。LTC1564のnoiseがdata sheetより５~７倍程度大きいようだ。

14/02/11 訂正：ground 関係はほぼ完璧：それでもAD noiseが公称の3.5倍程度：

usb controller upgrade basic

NDOT

2010/08/16
1. BMmonitor.ver1_0.exe: Windows(xp) exe file
2. AtUsbHid.dll: Windows(xp) dll file which should reside in the same
folder with 1.
3. BMver1_0.hex: firmware hex file

1. Put above 1 and 2 files in a directory on some WindowsXP machine.
2. Check if the exe file runs with the usb connection to the DOT device intact.
3. Go to ATmel and get FLIP,
http://www.atmel.com/dyn/products/tools_card.asp?tool_id=3886
4. Install Flip; you better follow the instructions on directory etc. as is.
5. While running BMmonito…exe, click the FirmwareUpgrade button on
the upper right corner.
6. In mycomputer.property->hardware->device manager window, you will
notice “LibUSB-Win32 Devices” pop up, which indicates the DOT usb
controller goes into DFU (device firmware upgrade) mode.
7. Run flip; follow instructions so that you load BMver1_0.hex into
the usb controller AT90USB162 of DOT.

usb firmware update

NDOT

2011/12/25
step2.1 Using BMonitor.exe you have on Windows PC, by hitting firmware
upgrade button, you put sdot usb controller into DFU mode. Exit
BMonitor while usb connection intact..
step2.2 Using ATmel FLIP, install the new firmware sdot2.hex.
step2.3 Using BMonitor, check if sdot with new firmware runs. If
hitting reconnect button results in “connected →disconnected
→connected” response, the firmware is basically all right. You may see
Windows message “usb機器が認識されません”. You may retry changing the order of
(sdot power on), (BMonitor run) and (connecting usb cable). If you
cannot get out of this condition, you are in serious trouble due to
the firmware bug. In this case, you must consult item #4 and install
the old firmware again.
step2.1 and/or step2.3 can be performed using either old BMonitor or
new BMoniot2.2. If you use BMonitor2.2 at step2.3, you should see
64bytes data in a row. 4byte composes one data, of which first byte is
the header. As was before, Windows cannot follow the data rate, but
the headers in a row should be consecutive numbers.

usb controller firmware revise

NDOT

1. C:ATMEL
2. copy old project folder and rename to new one e.g. SDOT.ver2.1
3. go down to at90usb162/demo/hid_generic/gcc; double click .aps
4. revise Makefile: target etc.
5. revise source code
6. build
中途半端、minor changeでは　folderをcopyしなおさない方がよさそう。ただしsource fileのback upを確実に。大がかりなときはprojectを変更すべき。